rosshadden / engine Goto Github PK

I did this in MMO or old-engine or something, but the aspect ratio thing here is pretty awesome.

Provide some color or formatting tools to the log.

I'd like to make it less of a debugging tool and more of a game component, eventually.

Add support for network events in Events API.

Make a module that loads resources, and returns promises.

External map editor program, preferably running as another Node.js service.

Add ability to end the game.

Work on making an Audio API.

rather than having one repository for the client engine and one for the server, I should make it all self-contained.

All of the client code will go in engine/client or something.

I just want to make sure I merge everything from how it is now so as to maintain history.

I think a simple cute and raw snake-game should be enough. Without sprites, sounds and else. I made something to port:

https://gist.github.com/yckart/5320382

It's time to link Socket.IO with the Node routes.

I did it once (here); shouldn't be too hard now that I've figure it out. But believe you me, it sure wasn't easy the first time... Why is there NO documentation on it? .

Refactor the client-side network module to allow for socket namespacing.

Right now, connect(), on() and emit() are all on the same level, but on() and emit() should not be available until after connect() is called.

This will allow for easy socket namespaces, implemented like this:

var one = network.connect('/one'),
    two = network.connect('http://localhost/two');

one.on('blah', function(){}).emit('blah');
two.on('blah', function(){}).emit('blah');

Allow resources.get() to accept type/name.

IE:

resources.get('sound/bark');
resources.get('image/dog');

I did this in MMO or old-engine or something, but the aspect ratio thing here is pretty awesome.

Allow for 'top, bottom' and the like as a parameter, which would be parsed as 'top' and 'bottom'.

Add some sort of angular collision.

Will probably have to rely on a history of entity positions.

Break out players into their own module, or at least share them between all modules of the engine.

Needs to be accessible from everywhere.

Move (or duplicate) collision to server.

Make an events system that can handle event bindings and emissions.

Add multiplayer API.

After messing around with Jade to try and fix my code after the update to 0.25.0, I realized the power in the new features. The pages can definitely benefit from them if used correctly.

Add ability to restart game.

I did this in MMO or old-engine or something, but the aspect ratio thing here is pretty awesome.

Break out events into their own module.