Thanks! :)

@gamedeveop hi, you can try to use parse platform (open source project on node.js) for storing user data

Finally, got i worked. The problem was in the child schema type. I have two schemas A and B. B contains A. I used the wrong type anotation : [Type(0, "A", typeof(A))] public A a = new A(); Should be [Type(0, "ref", typeof(A))] public A a = new A();

Hey! I'm having a difficulty to implement Child Schema Type on client-side (unity) , it always gives me error like 'schema mismatch ... ' could you show me an example, please. For example, if the folowing is the server-side schema : class IAmAChild extends Schema { @type("number") x: number; @type("number") y: number; } class ChildSchemaTypes extends Schema { @type(IAmAChild) child: IAmAChild; @type(IAmAChild) secondChild: IAmAChild; } How the client-side schema must be implemented? Thanks

@b-thanapat You should try more words to expain your scenario in order to make it easier for your friendly neighborhood programmer to help out. That said. I store the roomid in a cloudstore under security rules so that only the relevant users can access it and use that to join if the room is created. But if everyone leaves the room will be disposed and you cannot rejoin that instance. In case what your are looking for is not the actual room but the room state, I serialize it ad store it as a file blob in the cloud, accessible only by the server. Then when the room is created I download and initialize the store using that state.

I ended up solving it by trying to join and listening to the ErrorCode.MATCHMAKE_INVALID_ROOM_ID. creating the room as private and listening to any error trying to join again after a backoff time It works but feels lowlevel and protocol-ish. J/

May be I'll explain more. So the problem is the following: when connect to the LoginServer + the json , it works perfectly. The req.body contains the json I send. I'm using Insomnia here. But when using client.Auth.Login , It give me back "email or password incorrect". So I took a look at req.body and it's always empty.

Hi @niaina, welcome! 👋 Currently we don't have examples of the built-in LobbyRoom usage written in C# - but there is a room listing example inside the "Shooting Gallery" tech demo using the GetAvailableRooms() method here: https://docs.colyseus.io/demo/shooting-gallery/

Hi @b-thanapat, welcome! 👋 I've just managed to get NestJS (7.6.15) + Colyseus (0.14.x) working together by doing this: import { NestFactory } from '@nestjs/core'; import { AppModule } from './app.module'; import { Room, Server } from "colyseus"; import { MyRoom } from "./MyRoom"; async function bootstrap() { const app = await NestFactory.create(AppModule); const gameServer = new Server(); gameServer.define("my_room", MyRoom); // attach Colyseus into the existing http server from NestJS gameServer.attach({ server: app.getHttpServer() }); await app.listen(2567); } bootstrap(); Hope this helps, cheers!

Hi @AllNamesRTaken, welcome! 👋 You should be able to do the following: const snapshot = this.state.toJSON(); // ...store snapshot JSON into the database // ...let's restore the snapshot this.state.assign(snapshot); Let me know if that works for you!

@endel , thanks for reaching out. I'm looking forward the new proxy. is it public on github ?

Hi @gagarin-su, thanks for letting me know, the documentation hasn't been updated since the new Defold WebSocket extension has been introduced, the loop() call is not necessary anymore! (I've removed that section from the docs!)

@endel . it's done and work for me. thanks for your support. You're so nice.

this what I searching for several weeks, thanks man that really halping me to jakarta selatanbest regards

I see! Glad you found out. There is a TypeScript configuration to prevent this from happening called forceConsistentCasingInFileNames: // tsconfig.json { "compilerOptions": { // (...) "forceConsistentCasingInFileNames": true, } } ``

Thank you for your fast and positive response, @endel. I suggest the following additional changes to make the documentation fully consistent within in itself: send(type, message) I think this should be: send(identifier, message) Send message a type of message to the client. I think this should be: Send message with identifier and payload message to the client. The type can be either a string or a number. I think this should be: The identifier can be either a string or a number. // sending message with string type I think this should be: // sending message with string identifier Because it should be consistent with: // sending message with number identifier The green "Tip - See how to handle these messages on client-side." was removed. I'm not sure whether this was intentional. I think it should come back.