Multiplayer Platformer Log #3 – Authoritative Server

In the first developer log we talked about cheating and how the best way to prevent it, is making the server authoritative about the state of everything. That is what this log is about. Taking the custom simple physics engine we talked about in the second log, we are ready to start. Server Loop So how do we go about moving everything to server? Client has basic game loop where it moves character around based on input.

Multiplayer Platformer Log #2 – Physics

This second log was supposed to be about making the server authoritative so we would prevent cheating. Authoritative server has to simulate physics while client does client-side prediction. The first step took a bit longer than expected and deserves its own log. The previous naive implementation of our multiplayer platformer used Phaser’s Arcade Physics. Given new requirements, which will be further explained in the next log, we can’t use Arcade Physics and need to create our custom solution.

Haxe Externs For Phaser

When I started preparations for my online multiplayer game attempt, I realized I will need to create Phaser externs for Haxe. Haxe externs are a way for Haxe to know about types of methods and properties of external objects like Phaser. Surprisingly generating them took me a week and not the expected hour or two. And they still aren’t perfect (and probably never will be). Turns out that taking Phaser’s source and parsing the JSDoc using tools like js2hx isn’t good enough.

Multiplayer Platformer Log #1 – Naive Implementation

Motivation After finishing the project for my parents I was talking about last time, I finally had some time to get back to game development. After spending something over a month playing with unity engine, I decided to switch my focus back to something that got me to programming in the first place. Multiplayer online games. Back in high school, I implemented very naive multiplayer bomberman game as my school-leaving project.