Hi @kai_nguyenhuu, sorry for the delay to answer you here.

So what about "P123456" :-? is this string ?

Yes, this should do on 0.13. It is a string, not a digit/number.

I've spent some time today to fix the issue you mentioned in the first place ("Uncaught RuntimeError: memory access out of bounds"). It turns out the problem was using the C# dynamic keyword. This keyword is not supported on Unity WebGL builds.

You can download the latest version (0.14.0-alpha.2) here https://github.com/colyseus/colyseus-unity3d/releases

If you're sending Schema messages, you should listen for them in the client-side like this @lucks (the documentation is not doing a good job on the C# section)

room.OnMessage((MyMessage message) =>
{
	Debug.Log("Received Schema message:");
	Debug.Log(message.message);
});

(See demo unity3d source code here: https://github.com/colyseus/colyseus-unity3d/blob/30c9b7d8e8259a7516fafcbd26179a0ab6a91ec9/Assets/ColyseusClient.cs#L157-L161)

You may also declare interfaces that contains Message to get them generated to C# through schema-codegen (instead of using Schema for strictly typing messages)

Example:

interface ReadyToStartMessage {
  data: string;
}

// ...

this.broadcast("readyToStart", { data: "hello!" })

Client-side (C#, after running schema-codegen)

room.OnMessage<ReadyToStartMessage>("readyToStart", (message) => {
  // message.data
});

Hope this helps. I'm taking notes to update the C# documentation as it doesn't seem to be very helpful atm

Hi @kotwys, welcome 👋

The version 0.14 is not yet implemented in Haxe, if you're interested in migrating to 0.14 because of the "none" serializer, I'd suggest using the workaround instead - which is to use a dummy schema as your room state:

class State extends Schema {
  @type("string") dummy: string;
}

// ...
onCreate() {
  this.setState(new State())
}

I'll let you know here once the new schema decoder is available in Haxe, it's probably going to happen next month!

Cheers

Oh, I see! Thanks for pointing out the development flag, lol!
Maybe it would be better if you continue with 0.13 for now, and avoid using numbers as keys for MapSchema. I'll let you know when this problem on WebGL is fixed! Thanks for trying out! 🙏

Hi @kai_nguyenhuu,

I just checked and indeed WebGL builds are not working yet on version colyseus-unity3d 0.14 (alpha). In the example project from the repo, it crashes immediatelly after joining a room:

(I need to check why this error is happening on WebGL!)

Not sure how you managed to get past this error - are you sure you're using the 0.14 alpha version in the client-side?

71mb for ArrayBufferData in empty schema

This is related to Unity WebGL / emscriptten (has nothing to do with your empty schema). Indeed Unity WebGL builds are a disaster I can't do anything about. I've heard Unity Tiny is supposed to be much better in this regard - I haven't tried it personally, though.

Hi @kai_nguyenhuu,

Using digits as keys on MapSchema used to be a problem until version 0.13.

I'd recommend using the new 0.14 alpha that's coming up: https://deploy-preview-45--colyseus-docs.netlify.app/migrating/0.14/

Let me know if you find any issues using it!

Hi @mhosan, welcome 👋

We've been having this discussion recently on Discord, there are no immediate plans on having a Game Maker client unfortunately.

Hi @VanillaDevelop, welcome! 👋

The Unity client tries to validate all the schema structures locally, based on the "handshake" that comes from the server. What's not very well documented is that, right now, every @type() annotation is going to attach the structures into a "global" context - putting all your room's schemas into the same "global" context, therefore the client will receive schemas from multiple rooms and throw the "mismatch" error in case some of them cannot be found.

I suggest you create your own @type() to avoid this problem in Unity, as suggested here: https://discuss.colyseus.io/topic/390/schema-handshake-problem-between-server-and-unity-client/2

I need to provide more documentation about this on the next release that's coming up (0.14)

Let me know if that works for you

Hi @kukuts, thanks for your availability for testing the alpha version.
If you're using the JavaScript client (colyseus.js), you can try out the beta versions at:

• colyseus@0.14.0-alpha.5 (server)
• colyseus.js@0.14.0-alpha.4 (client)

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/

Hi @kukuts, I'm working hard on @colyseus/schema#75 since last month, I'm expecting an "alpha" release someday next week, it would be great if you can jump in to help us test this new version. There are some small differences from latest stable version to the new one which I'm going to document to help everyone migrate. 🙏