Open johnspeny opened 2 months ago
The colyseum library was updated by they and the client lib need be updated to stop the errors. They have more headers things that need be considered now.
You can try help here: https://github.com/colyseus/colyseus-cocos2d-x/issues/8
Is it possible to avoid the colyseus client and use the websocket that is in axmol. I don't really think they will provide us help anytime sooner. Connection to the server could be easy but other stuff like rooms that looks hard on just bare websocket.
Hi @johnspeny,
It already use the axmol websocket, you can see here: https://github.com/paulocoutinhox/axmol-multiplayer-colyseus/blob/main/ColyseusLib/Colyseus/Connection.hpp and https://github.com/paulocoutinhox/axmol-multiplayer-colyseus/blob/main/ColyseusLib/Colyseus/Connection.cpp
I already fixed the other things in Colyseum, but need someone that understand the protocol part to update here.
I see that don't have too much difference, because i see on other code that they update (like js client and check that don't have big changes: https://github.com/colyseus/colyseus.js)
I made the most part to update somethings, create a sample project, create a simple server, organize everything from axmol, but the only part that left is add the things that we don't have in the client from latest protocol version.
Some clientes:
Schemas:
We nee compare with other client and add the part that left
Using visual studio 22 and building for win32. The server is running alright on localhost. The client errors with std::out_of_range at memory location. I can't seem to hit any breakpoint in the MainScene to know whats exactly wrong.