Bomberman massively multiplayer in HTML5

Post by jff » Wed, Feb 27, 2013, 6:17 PM UTC

ruok0101 wrote: post #90

Shish2k wrote: post #70

Earlier quoted context omitted.

Web Apps set us back 20 years in pretty much every respect except ease of deployment (1992 - people are impressed that Wolfenstein 3D gets 60FPS on a 100MHz Pentium; 2012 - people are impressed that Wolfenstein 3D (in Javascript!!!!111omg) gets 15FPS without sound on an 8-core 3GHz box). With the exponential rate of development I doubt it'll take a full 20 years to catch up, but it'll still be a while before we've co…

I think this overlooks all the pluses of this new "medium". How did you get your copy of wolfenstein in 1992? Travel to the radioshack, get a stack of disks, feed them one by one into your trs80? Within seconds this morning I was playing this game - with a 1000 other people simultaneously. Amazing in my book.

Post by dubcanada » Wed, Feb 27, 2013, 6:36 PM UTC

T-hawk wrote: post #56

de90 wrote: post #47

Earlier quoted context omitted.

The way you prevent cheating in a game like this is that the game itself runs on the server. The client side is merely showing a representation of the server state. If people want to edit the scripts to show an invalid state who cares. Granted latency becomes a huge challenge, but in a perfect world (no latency) having the scripts on the clients side and having people edit them isn't a big deal

Easily said, but the challenge is making absolutely triple damn sure that the game running on the server is bulletproof against malicious input by the client. It took years for early games like Diablo and Everquest to get it right in ignoring a client sending position updates to move a character faster than nominally allowed by the game logic. And that's the tip of the iceberg. You also have the problem of hidden inf…

Post by harlanlewis » Wed, Feb 27, 2013, 6:41 PM UTC

Shish2k wrote: post #70

jader201 wrote: post #29

I upvoted this because it is awesome, and it is, well... Bomberman. But I'm genuinely curious: at what point will we stop being fascinated by what can be done in HTML5, and actually start focusing more on what is actually being done -- regardless of the technology used. Or to put it another way: when will HTML5 games stop feeling like HTML5 games? For example, if this were on a console, I think it would still be cool…

Web Apps set us back 20 years in pretty much every respect except ease of deployment (1992 - people are impressed that Wolfenstein 3D gets 60FPS on a 100MHz Pentium; 2012 - people are impressed that Wolfenstein 3D (in Javascript!!!!111omg) gets 15FPS without sound on an 8-core 3GHz box). With the exponential rate of development I doubt it'll take a full 20 years to catch up, but it'll still be a while before we've co…

Post by joshuacc » Wed, Feb 27, 2013, 6:54 PM UTC

jiggy2011 wrote: post #79

sixothree wrote: post #77

Earlier quoted context omitted.

Do you still have to deal with all of the DOM stuff in html5/javascript?

Yes and no. It's all still there of course. I imagine though if you want to build a game you don't use DOM elements for sprites etc. You just create a giant element that you draw to as you would draw to a frame buffer in DirectX etc. You could use DOM elements for the UI though I guess.

Post by saraid216 » Wed, Feb 27, 2013, 6:58 PM UTC

jader201 wrote: post #29

I upvoted this because it is awesome, and it is, well... Bomberman. But I'm genuinely curious: at what point will we stop being fascinated by what can be done in HTML5, and actually start focusing more on what is actually being done -- regardless of the technology used. Or to put it another way: when will HTML5 games stop feeling like HTML5 games? For example, if this were on a console, I think it would still be cool…