I've just seen your dashboard and it's look pretty good

I'll have a look on your code later to see if some feature are redundant.
However, the purpose of the tools seems to be quite different.

Your dashboard looks awesome to monitor and manage rooms and server on backend side. My client is more like a Postman client. It helps to debug server without having a fully workable game client.

@endel thank you very much

Thanks for the detailed answer!

AFAIK these platforms you mentioned will provide servers and resources to host your game. As Colyseus is just a networking framework, it also doesn't provide any kind of game logic out of the box. You'd need to implement everything by yourself.

Right, both platforms are also social networks, and I don't need that. (Though BYOND doesn't host the servers.) A networking framework is exactly what I'm looking for.

This works great if your game state is not too big.

How big is too big?
I've seen the splitting and filtering views feature. It seems like a must-have for a networking framework, not only for performance, but also for cheating prevention purposes.

Currently, we haven't seen a use case for this. Most games need to have multiple sessions, and matchmaking comes along with it.

My (hypothetical) use case is a ss13-like: every server uses their own fork of the game code with minor tweaks, and the servers can have up to a hundred players and are barely ever full.

Not at the moment. I believe client-side prediction is not easily pluggable in a way that the framework abstract everything for you.

Wait, do you run the game code on the client at all?

Client-side prediction can depend on the game, but all games could benefit from changing the local state immediately. And many games aren't performance-bound on the client by the size of the local game state and can handle recalculating several game states every time the server sends something unexpected. Right?

@holywyvern I've added a new issue about this here: https://github.com/gamestdio/colyseus.js/issues/25

Hi @endel ! Thank so much!

this is suitable, thank you very much!

@rscata alright! One thing that is not intuitive in this version is that you can only see the error messages and stack traces if you turn on DEBUG=colyseus:errors

DEBUG=colyseus:errors npm start

@endel said in Room Error.:

es2016

works, thanks.

@endel It works, thanks!

No problem! The problem however still presist if you use the server from the Unity package if im not mistaken. You might want to update this one aswell?

Hi @Carlos-Montesino,

Sorry, the c3addon zip file I've uploaded was corrupted. I've just fixed it here: https://www.construct.net/br/make-games/addons/111/colyseus-multiplayer

Cheers!

Hey @colyseus, (you should pick another username btw, )

AFAIK, Cocos Creator doesn't play nice with NPM modules. So, you'd need to download and use the distribution file directly: https://github.com/gamestdio/colyseus.js/blob/master/dist/colyseus.js

Hope this helps! Cheers!

Hi,

thanks for the release, this is awesome!

I have an issue though, I'm getting error (RESOLED, see below) : colyseus.js: server error: Class constructor Room cannot be invoked without 'new'

Client-side:

client = new Colyseus.Client('ws://localhost:9090'); room = client.join('basic');

Server-side:

#index.js const colyseus = require("colyseus"); const http = require("http"); const express = require("express"); const app = express(); const gameServer = new colyseus.Server({ server: http.createServer(app) }); class BasicRoom extends colyseus.Room { requestJoin (options, isNew) { console.log('Quizzroom requestJoin: ', options, isNew); return true; } onJoin (client) { console.log(`BasicRoom - client ${client.sessionId} joined.`); } } gameServer.register("basic", BasicRoom); gameServer.listen(9090);

The documentation doesn't provide example in javascript, only typescript.
Is there something I'm missing?

UPDATE:
I was running the server with nodemon server.js --exec babel-node and I should use nodemon server.js.
Everything is fine now.

Hi @shortid,

The Timeline is an experimental feature only present for lag compensation on the server-side. I personally haven't seen anybody using it yet. You can add it as a dependency in your client-side and take the snapshots whenever the state updates if you'd like to.

There's a big difference between lag compensation and client prediction techniques, though. I think you're looking for client-prediction. Unfortunately, the framework doesn't provide an easy way of doing either.

@Алексей-Андронов the clock only works if you set up the simulation interval.

I guess that's not intuitive, I'll fix this on version 0.9.0 too.

Ok, thank you. Oh yeah, I did actually figure it this way, but in this case, I'm worried about performance, as it would need to do 7x (10x, if I would also include the scale) more callback calls as if it would just return the array. So the string solution does work ok (.split('|')/.join('|')), but it sends/receives more bits of data.
Mean, for now, there is no way to hack around, so I would be able to get an array in "one batch"?

Thank you @endel for the quick reply, this is exactly what I was looking for. I should've found it in the documentation.