31–40 of 46 posts
Earlier quoted context omitted.
are there any public servers that we could connect to?
(BLK author here) Whoops - the public server I had running must have died. I'll get it running again tonight. If anyone wants their server listed just let me know! I have some directions on the site for how to get it in the listing on the page.
Earlier quoted context omitted.
Agreed. Someone please make an AOE2 clone for the browser. It's the perfect environment for multiplayer RTS.
I think the big barrier for building a multiplayer RTS in the browser would be the lack of UDP sockets. You could certainly do something with websockets but it may involve making substantial compromises. With TVs you have the added issue that people probably don't want to replace their whole TV every couple of years just to upgrade the graphics or whatever.
Generally, in each tick player (or AI) input is received and then transmitted to the server or all other players. In the next tick, that input is then processed by each player's individual simulation of the game world.
A tick-based system does a decent job of handling latency by distracting the player the delay between input and processing through audio confirmation of the order or through a response/transition animation. It would not work for games requiring low-latency, i.e., FPS shooters.
Earlier quoted context omitted.
(BLK author here) Whoops - the public server I had running must have died. I'll get it running again tonight. If anyone wants their server listed just let me know! I have some directions on the site for how to get it in the listing on the page.
I filled in the form twice, just for info... ?
Earlier quoted context omitted.
Agreed. Someone please make an AOE2 clone for the browser. It's the perfect environment for multiplayer RTS.
I think the big barrier for building a multiplayer RTS in the browser would be the lack of UDP sockets. You could certainly do something with websockets but it may involve making substantial compromises. With TVs you have the added issue that people probably don't want to replace their whole TV every couple of years just to upgrade the graphics or whatever.
Earlier quoted context omitted.
I think the big barrier for building a multiplayer RTS in the browser would be the lack of UDP sockets. You could certainly do something with websockets but it may involve making substantial compromises. With TVs you have the added issue that people probably don't want to replace their whole TV every couple of years just to upgrade the graphics or whatever.
Hopefully WebRTC data channels will enable UDP-like comms from the browser.
A friend of mine made something similar, plus multiplayer support (and minus gravity): http://benvanik.github.com/blk-game/
A friend of mine made something similar, plus multiplayer support (and minus gravity): http://benvanik.github.com/blk-game/
A friend of mine made something similar, plus multiplayer support (and minus gravity): http://benvanik.github.com/blk-game/
To my knowledge Firefox has had support for IndexedDB for a long time without a vendor-prefix. Why does the page claim that it doesn't? Is there a bug in the implementation? A missing feature?
A friend of mine made something similar, plus multiplayer support (and minus gravity): http://benvanik.github.com/blk-game/
To my knowledge Firefox has had support for IndexedDB for a long time without a vendor-prefix. Why does the page claim that it doesn't? Is there a bug in the implementation? A missing feature?