[koningrobot]

I'm working on a realtime strategy game in the browser using "full-duplex" AJAX. I started working on it about a year ago but I had to take a considerable timeout after burning out at my former boring job. It's slowly getting somewhere, though.

So why in the browser? Because that makes it instantly hackable! No more bad pathfinding or shitty interfaces to put up with!

[tectonic]

Have a demo?

[koningrobot]

Unfortunately, no. I've been getting the plumbing together; a layer that abstracts the ajax and session stuff so that all I'm left with on the server side is a file descriptor (one per session) to read from and write to.

I have some JavaScript code that allows you to select "units" (I made some ugly debugging sprites in Gimp) and move around with them, and scroll around and stuff like that. But I have yet to bridge it with the mostly to-be-implemented server-side logic. The client-side part is just for "dead reckoning" and generally making things flow between game state updates from the server. So both sides will share some logic, and I'm still thinking about how to centralize this.

It might take me as much as half a year to get unit movement working across the network; once that is in place, the rest should be relatively easy.

Luckily it's all hobby. ;)