ClusterAtlas

@index: Added p5.js!

Glad you've found DigitalOcean! Anyways if you got a spare credit card w/ few dollars (required, but not charged) feel free to try out Azure, AWS & Google Cloud, too https://www.microsoft.com/itprocloudessentials/en-US - $25 / mo on Microsoft Azure, 1 year. enough for small vps. https://cloud.google.com/free/ - free vps w/ other stuff, 1 year. https://aws.amazon.com/free/ - free vps w/ other stuff, 1 year. - sign up using any credit card (visa/mastercard/whatever; prepaid cards not accepted) - just run an ubuntu linux virtual machine instance - use put

@index: q.js, q-io.js, bluebird.js, asap.js, async.js, i18next, ejson, msgpack, underscore, lodash, highland, uuid-random, random.js, chance.js, faker.js, google maps, leaflet, openlayers, vexjs, express, koa, hapi, gulp, grunt

I ain't @Arcanorum but I think you're in the right direction! Yes it would be node.js & socket.io, and yes a home server would already do the trick. Some points to consider: - Static IP for the server-side, so you can use / bind that IP & port in the client-side code. Hence when the players open / run the game in their mobile, the server will be reachable instantly. - A great / battle-tested RNG (Random Number Generator) so the game really operates on a very randomized environment - many can be found in npm - It would help to draft it on the paper first on ho

@index: Added CreateJS suite: EaselJS, TweenJS, SoundJS & PreloaderJS.

@cloud4gamedevs: got some great feedback at Totally doing this, cheers!

@index: added stage.js, cocos2d-x, playcanvas engine, atomic game engine, goo.js, crafty.js, whitestorm.js, planck.js; added description to all linked engines / frameworks.

Linked this thread and the site @ https://github.com/clusteratlas/index Awesome collection man

@index: Added three.js, ammo.js, cannon.js, p2.js, physics.js, stats.js, keypress.js, hammer.js, moment.js, moment-timezone.js

https://github.com/clusteratlas/index - Basics, libraries, assets, etc. https://github.com/clusteratlas/awesome-cloud4gamedevs - Everything cloud-related, simplified for game devs. - Diagram drafts: Yup there's a lot of housekeeping & finishing to be done, hell at least the table of contents for the 2nd one already got drafted. I'm dedicating my whole next week to finish 'em. Cheers and thanks!

I actually agree XD pardon my vagueness What I actually meant was to piece them working things (ie eventemitter3 & socket io) together into a client-side & server-side classes that both have their own common predefined events so they can work well with each othaa EDIT: I just re-read the main post, not sure if OP's creating a multiplayer one - hence he can just use eventemitter3 alone already OP, w/ eventemitter3 it's already enough to emit & handle events wherever and however the hell you want https://www.npmjs.com/package/eventemitter3 https://nodejs.org/api/

Welcome to the forums brotha! Check the link below in my signature, I regularly update it!

http://reddit.com/r/iogames

Create your own! Craft your own object / class that does the both: - Emits the event locally (ie: when user picks up item, eventemitter3 can raise an event!) - Emits the event remotely (ie: when user picks up item, an eventhandler attached to the above eventemitter3 event SENDS / informs the server that ya picked dat item)

One of the cutest games ever XD LOL