🔒 Locked

Libraries for online web game multiplayer?

Started by Caleb Adam Jan 19, 2018 at 4:05 PM 6 replies 5k views

Original Post

Jan 19, 2018 at 4:05 PM

I want to make a html5 canvas / javascript game, similar to agar.io. I know a little node.js, and I think I understand the way online multiplayer works, but now that I do understand I realize it's gonna be a ton of work if I want to do it from the ground up with something like socket.io. My question is: are there libraries that can help with the multiplayer aspects of my game (sending game packets, etc.), and if so, is the performance for that library fast enough to run my game? (has a latency at least as low as agar.io)

Caleb Adam

Jan 19, 2018 at 4:15 PM

I did find Lance, but the list of games built on it is suspiciously small. I'll look into it, but please post your recommendations!

flodihn

Jan 21, 2018 at 11:53 PM

I have heard some people use Photon Engine: https://www.photonengine.com/en/OnPremise.
Maybe it is what you are looking for.

I also know the UnityPark SDK, I suspect that only works if you are using Unity3D.

http://developer.muchdifferent.com/unitypark/

BeerNutts

Jan 24, 2018 at 9:09 PM

phaser.io with socket.io described here:

http://www.html5gamedevs.com/topic/13472-four-player-pong-example-with-socketio/

caymanbruce

Mar 25, 2018 at 8:48 AM

I write my game server from scratch. I don't think socket.io can handle the workload of any serious multiplayer web game, try to use ws or uws library.

Caleb Adam

Mar 25, 2018 at 3:39 PM

Thanks, by now I’ve decided to learn Unity and release my game for WebGL. (I’m assuming the networking on that is reasonably fast and reliable, Unity is a very widely used game engine) That way I can release for any other play form if I want later. It’s encouraging to hear that someone actually has built their game from scratch with web sockets though!

hplus0603

Mar 25, 2018 at 7:27 PM

I don't think socket.io can handle the workload of any serious multiplayer web game, try to use ws or uws library.

I don't think there's a significant difference in what server-side socket library you're using. The main problem is that all websockets use TCP, and that you will need to funnel player counts across multiple threads (hard with Node.js) and multiple servers (hard in general.)

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.