Forums » Code » Working on Shooter ;-)

Hey Guys,
i work on a new shooter game with impactjs.

Here some screenshots and i hope in a few weeks the link to the game ;-)

http://img855.imageshack.us/img855/3530/game1a.png
http://img811.imageshack.us/img811/847/game2et.png

Regards,
FlowPX2

Sorry,...
false forum... this must in the game and not in the code forum.

Looks good :)

(I don't know if Dominic has added a 'move topic' feature yet :/)

Thanks,
at first i create the tilesets for the game and later i create a few maps.

This game is a multiplayer shooter game... later with other guns, anti-personnel mine and other stuff ^^

did you say multiplayer? i'm looking forward to that !

Yes multiplayer...
at first with the help from impactConnect... simple multiplayer...
no physics Engine... later with a Box2D engine on the server side.

impactConnect use a WebSocket server coded in NodeJS.
NodeJS ist a Javascript runtime for a server... it work's on windows, linux and mac.

Node.JS works vastly better on Linux than it does on Windows, btw. I also wouldn't really describe it as a 'runtime' for a server; I haven't done that much in Node.JS but the stuff I was doing ended up being the full server in itself, especially since socket.io doesn't work properly (at least not for Websockets) over nginx.

I don't know how nodejs works on windows ;-)
I use a Macs or linux servers.... but microsoft helped the nodejs project for a better windows implementation. node 0.6.6 is native for windows available.

It works, but badly compared to on Mac/Linux, because the thread polling method used in Node.JS for the best performance doesn't exist in Windows' kernel.

Then the easiest way is to use a linux server for the multiplayer ;-)
And the client run in all Browsers and use WebSocket to connect... there are no problems ;-)

Websockets are not supported on all clients, and support for different versions of the Websockets specification (of which there are about three major iterations circulating) was withdrawn in at least one major browser over security matters.

If you're using socket.io to handle it, it's silently dealing with it in the background for you, falling back to conventional long polling or even Flash sockets depending on browser support...