There is a method "removeAllListeners()" that removes ALL listeners from a client. I would suggest a method of removing a specific onMessage listener by name.
A useful pattern for in socket.io is to emit some message and then await a Promise for its broadcast back. This allows you to chain the response as part of a parent function. However, its safest to then do a socket.off() for that message type once you've gotten it back. I'd like this same ability when using Colyseus, thanks.
Hello. I have recently deployed a GameFi application (https://hashandslash.io/) that is a singleplayer, turn-based roguelike game. As it's GameFi, the game needs to be server authoritative despite being singleplayer.
Originally I wrote the game server in socket.io from scratch, and I'm looking for a solution that will scale automatically before I take it to Mainnet. So I have some questions about Colyseus:
I currently update the client by sending a single protobuf message containing the results of each turn. Does Colyseus support protobufs for gamestate updates?
It looks like Colyseus is designed for realtime games specifically. I only need to send a gamestate update whenever a player submits a valid turn. Is there an option for turn-based gamestate updates?
While the game is singleplayer, I also give other players the option to observe a game by joining its socket.io room. Is this something I can recreate in Colyseus? Would I be able to give players a global list of active games across whatever horizontal scaling you're using?
I need to be able to encrypt/decrypt certain server-side messages which are stored in a DLT. Does Colyseus support any kind of key rotation/management system for individual games? (This one isn't too big of a deal as long as I can use the aws sdk).
Lastly, there's various DLT-related stuff the server needs to do, including storing and accessing private keys. Is there any limitation wrt outbound traffic (specifically to the Interplanetary File System) on Colyseus, and does Colyseus have a guarantee as to account privacy (no individual employee has access to a client's server info)?
Thanks.
