administrators

Hey @elieobeid7, welcome! That's not possible, unfortunately. It would be great to support Godot in the future, there's one thread about this here: https://github.com/colyseus/colyseus/issues/217

Hey @KG204, yes! State mutations look exactly the same as they used to on previous versions! Cheers!

Hey @cmdt-ed, it's not ideal but you can use that. The Presence API doesn't currently support sismember - which is better for checking that, I'd appreciate if you can send me a pull-request adding it! https://redis.io/commands/sismember

There's only two Presence implementations now, both can implement this method:

• LocalPresence: for single-threaded environments link
• RedisPresence: for multi-threaded environments link

Cheers

Looks like the client-side is still on version 0.9, and the server is 0.10. I haven't tried this Haxe setup yet though!

Really nice work @serjek! if you're interested in supporting it, would be nice to move it to the organization, then I give you rights to it :)

hey @cmdt-ed, you can override the roomId during onInit():

// server-side
onInit(options) {
  this.roomId = options.roomId;
}

// client-side
var room = client.join("chat", { roomId: "hello" })

Keep in mind that making sure these values are unique is in your hands this way.

that's pretty cool @serjek! great job!

@serjek nice, when you install both colyseus and colyseus.js through npm install, you'll find all .d.ts files inside the node_modules/colyseus/lib and node_modules/colyseus.js/lib directories.

Not sure if I understand why not to use the colyseus-hx project for the client-side. I think there's no need to make externs for the JavaScript client here. If server (Node.js) and client (React.js) are two different applications, the server doesn't need to have the client module as a dependency (colyseus-hx). The client-side would, though, and it's compatible with the browser. The problem would be react-native indeed.

Are you currently wanting to make a react-native app with Colyseus + Haxe?

@mackycheese The error points you to see this URL: https://docs.colyseus.io/migrating/0.10/#new-default-serializer

Basically, the new default is to use a class extending the Schema for your state as of version 0.10. You can continue using the previous serializer if you'd like to, as stated in the migration guide.

Using React, you can do this in the client-side:

// client-side
this.room.onStateChange.add((newState) => {
    this.setState(newState);
})

Colyseus is not supposed to be used along with socket.io. Why would you need socket.io AND colyseus?

@serjek awesome, let me know when you got something working, wanna jump on this as well! :)

about tink_http, I think that's not really useful because Colyseus has been tested only along with Node.js' http module and the express framework.