Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Old school RPG style map in HTML5 canvas using websockets.

news.ycombinator.com

Post reply on HN
Print view View original

11–20 of 44 posts

Re: Old school RPG style map in HTML5 canvas using websockets.

#13

Post by skorgu »

JimmyRuska wrote: post #3
messel wrote: post #2

Hey that's pretty cool, is the source open? I might have some time tonight, found an error. I can fix it and pop it on github?

Just view source, it's not obfuscated. If there's interest I can post the erlang code for the server on github.

Please do.

Re: Old school RPG style map in HTML5 canvas using websockets.

#15

Post by dan11 »

JimmyRuska wrote: post #14

Here's source http://github.com/jimmyrcom/websockets-RPG-map-thing Gotta fix the flooding issues, there's still something that can make it crash too.

Yeah, that's me.

var a = 1; function d() { $('#say').val(a); say(); a++; } setInterval("d();", 100);

Not exactly hard.

Re: Old school RPG style map in HTML5 canvas using websockets.

#16

Post by JimmyRuska »

dan11 wrote: post #15
JimmyRuska wrote: post #14

Here's source http://github.com/jimmyrcom/websockets-RPG-map-thing Gotta fix the flooding issues, there's still something that can make it crash too.

Yeah, that's me. var a = 1; function d() { $('#say').val(a); say(); a++; } setInterval("d();", 100); Not exactly hard.

It does have a flood filter, your thing just spams so it gets in the post every chance. I can only make the flood count longer. That's the problem with javascript, kinda hard to prevent people from screwing around and editing it in-place.

Re: Old school RPG style map in HTML5 canvas using websockets.

#17

Post by dan11 »

JimmyRuska wrote: post #16
dan11 wrote: post #15

Earlier quoted context omitted.

Yeah, that's me. var a = 1; function d() { $('#say').val(a); say(); a++; } setInterval("d();", 100); Not exactly hard.

It does have a flood filter, your thing just spams so it gets in the post every chance. I can only make the flood count longer. That's the problem with javascript, kinda hard to prevent people from screwing around and editing it in-place.

I'm not 100% sure how WebSockets work, but I assume it's going through your server and then sent to everyone else? Could you not do a rate limit of 5 per 30 seconds, or require at least one comment in between yours? Not sure what the best approach would be best.
Post reply on HN