Hi

I'm making a Real-time multiplayer game, which also includes physics, I'm working with node.js, socket.io on the backend and Phaser on the client Side.

Till now I was running the logic on the client side and sending the velocity and position through sockets to all the clients, but obviously it doesn't works well(And we haven't even started to talk about cheating).

So, what I need is to run the logic and physics of the game in the server side, sending just the inputs on the client, and receiving the position from the server.

Well, for now it's simple, as any other multiplayer game.

The problem is that I'm going crazy, I have seen many tutorials but I don't even know where to start, because my programming skills are limited and the tutorials didn't help me, what I would need is a framework or tutorial which allows me easily to run several worlds(The game has different rooms), in whose physics have to be calculated as fast as possible.

So I ask, has someone done or found any tutorial which does that?

sounds like what you need is a game engine that supports multiplayer and serve side physics. poll for input or queue input packets then process, then broadcast results.

That's another option I'm wasking for, one easy to use, I will need to use a DB in the future too, to make an entire web around the game, but I don't know if, for example Construct 2, has enough potential to do that because it's without programming, but I would love to.

What i need is a easy engine which serves that, as easy as possible, or some example/template of what I'm looking for, in box2d physics, for example.

Note that distributed systems programming is some of the most challenging parts of software development.

As Phil Karlton has reportedly said, "There are only two hard things in computer science: cache invalidation, and naming things" Distributed systems programming includes LOTS of both, so it should be indeed among the most challenging ones ;-) .

P.S. My apologies for off-topic, but I couldn't help myself...

"There's only two hard things in computer science: Cache invalidation, naming things, and off-by-one errors!"

I love this one too ;-) (BTW, Leon Bambrick from secretGeek says he's the one who added 'off-by-one' bit: https://twitter.com/codinghorror/status/506010907021828096 ), but as off-by-one errors are not specific to distributed computing, I've decided to skip it this time :-)