Hi @Soh-Sea-Kiat, by reconnection you mean calling ReJoin? Cheers

I'd love to see the Defold client evolving to eventually support all major LUA platforms, such as the ones you suggested, and löve2d.

The problem currently is the platform-specifics of WebSocket implementations, basically. Defold has its own WebSocket client that works for them, CoronaSDK also has one made by the community - which AFAIK it doesn't work with binary data.

@Apollo144 do you know if Gideros have a WebSocket client?

Cheers

Hi @Project-Magenta, are you sure the server is running on port 3000?

Hey @coffie-raymond-atiampo, are you going to build a native Android application?

Currently, there's no official client for Android (Java), it shouldn't be that hard to implement one, though. You can check the other clients as reference if you'd like to build it yourself:

• JavaScript client
• LUA/Defold client
• Unity3D client

One member of the community (@swittk) implemented an ObjectiveC client some time ago: https://discuss.colyseus.io/topic/82/colyseus-objective-c-client/2

Cheers!

Hi @karneaud, welcome!

Sure, you can listen to "locked" and "unlocked" events from inside the room handler. Example:

class MyRoom extends Room {

  onInit () {
    this.on("locked", () => console.log("room has been locked!"))
    this.on("unlocked", () => console.log("room has been unlocked!"))
  }

}

Cheers!

@merhawie said in Buffer not defined error:

Buffer is not defined

Hi @merhawie, that's right, I think you need to add "buffer" as a dependency on package.json. I've just added this to the RN caveats.

import { Buffer } from "buffer";
import { AsyncStorage } from 'react-native';

window.localStorage = AsyncStorage;
global.Buffer = Buffer;

Hi @hardik_sl, it's up to you how to represent turns in the state. A common approach is to set the sessionId of the current player in a variable, like currentTurn:

onInit () {
  this.state = { 
    players: {/* add players here when they join */},
    currentTurn: "" // sessionId of the current player
  }
}

onJoin(client, options) {
  this.state.players[client.sessionId] = {/* player data */}
}

onMessage (client, data) {
  if (client.sessionId === this.state.currentTurn) {
    // perform your action

  } else {
    console.log("only the current active player can send messages this time")
  }
}

Hey @merhawie,

Are you calling client.join() after the onOpen signal, as described here? https://github.com/gamestdio/colyseus.js#react-native-compatibility

Sorry @merhawie, that was actually my bad.

I've managed to fix this on version 0.9.11 of the client. During some refactoring on the client, I've moved the Storage to a different file and forgot that the storage should not have been assigned upon module loading.

It works fine now!

@zgz682000 I understand. Most tutorials and material out there about scalability will tell you about stateless applications. The thing is that games are stateful, IMO.

What Colyseus does at the moment for scalability is using Redis to map connections to messages going back and forth to the correct room instance. Regarding losing data, you usually would persist relevant data during the lifecycle of the room instances. They're meant to be ephemeral, spawned and destroyed all the time, like a short-lived session.

Hope this helps! Cheers!