@wenish looks really awesome, thanks for sharing!
Did you do the artwork yourself? :o (On the Login / Sign Up screen)
I'll definitely consider using it at one point.
hi @ahtashamabbasse, not sure if this was already replied on Discord, I'll post here anyway!
you can listen to your hand structure using something like this:
room.Listen("hands/:index/:attribute", this.OnHandChange);
// ...
void OnHandChange(DataChange change)
{
Debug.Log(change.path["index"]);
Debug.Log(change.path["attribute"]);
Debug.Log("has changed to");
Debug.Log(change.value);
}
The callback will be called for each attribute you have on each item in your array. Here's the logs I've got from this:
There's a big discussion about this here: https://github.com/colyseus/colyseus/issues/59
To summarize: in the current state of the framework, you'd be better off sending data manually to each client (thorugh room's send method), and not use the state for the world.
Hopefully this will be improved eventually when colyseus/schema gets stable!
@deadwind88 I think I can help with this.
You need to create an onMessage handler on your client side. Refer to this https://docs.colyseus.io/client-room/#onmessage
so lets say your server code is working fine, in the client, you'd need to extract that message.
ex: onMessage(…) {
if (message.action === "request_dule") {…}
}
Thank you! Apologies if I thought it was colyseus related.
Its probably that but I wont be able to test for a while (computer crashed and fails to start, less than a year old, still under warranty)
And that's why unit tests should always be used. Could have caught the error. I come from a compiled background so still getting used to debugging JS
Aah interesting I'm also wondering about this thing but don't know about forever package. Hope so it will solve my problem too while deploying the game I'm working on multiplayer puzzle game in JS. And noticed that whenever server is crashed need to spin it again.
You will not be able to easily restart game loops and etc after the server restarts. The best you can do is persist the relevant state to the DB and load it when the room is created again.
Hi @DenisNP, welcome. This is not available at the current state of the framework.
The only encoding option the framework provides today is a binary-diff using fossil-delta. The diff transferred to all clients consists in diff of the msgpack-encoded version of the previous state with the current one.
A custom state encoding would be necessary to allow this behaviour.
I do not have a solution strictly speaking to counter the problem in a "clean" way, only a way to circumvent the problem by adding a condition that would remove an element of the dictionary if it already exists
Hi @Oviol, this sounds really good, sorry the delay to reply here. Would you mind creating a pull-request in the colyseus-unity3d project with this update?
Cheers!
Hi @donghung, have you tried replacing the file mentioned by the author? (https://github.com/deniszykov/msgpack-unity3d/issues/21#issuecomment-451642818)
I don't have Unity3D installed right now. Let me know if it works for you!
Awesome, feel free to share what you are doing here on the forums or the Discord chat! Not many people are using the Haxe client yet! Good luck with your project!
