@endel said in room.OnMessage not registered for Schema message: MyMessage:
room.OnMessage((MyMessage message) =>
Debug.Log("Received Schema message:");
Works perfect, thanks, yes I was reading the documentation, but not well at all.
Found the issue.
SSL was not the problem .Unity client is replacing the existing path in url when joining a room.
Fixed it by adding existing path in CreateConnection method of Client.cs class
UriBuilder uriBuilder = new UriBuilder(Endpoint.Uri)
Path = Endpoint.Path + path, //earlier it was just path
Query = string.Join("&", list.ToArray())
It seem like not only colyseus server is affected:
I created a bug for colyseus to handle this particular error in graceful way and keep clients connected:
I just asked if you can use Spanish. I attach this text if not:
Thanks for the welcome !, and the question was to try to connect from gamemaker. Currently I made a very very basic server in Node but I would like to take advantage of something already made like Colyseus, which is a very good development, congratulations!
Hi @kukuts, thanks for your availability for testing the alpha version.
For short, you can install them using:
npm install colyseus@alpha --save
npm install colyseus.js@alpha --save
Hopefully, ALL MapSchema issues should be gone now. There are some small API changes though, mostly regarding iterating through MapSchema values and/or its keys, and getting its length. Here's the upgrading guide so far: https://deploy-preview-45--colyseus-docs.netlify.app/migrating/0.14/
And another problem, when A game and B game share the same schema, that would be a problem.
gameA use PlayeInfo Schema in ARoomSchema and gameB use PlayerInfo too in BRoomSchema. That would be a situation, the PlayerInfo could only implement one specific context but not two.