Hi @TheRedHead, welcome!

That's really up to you. Here's the major difference from using a message or the state:

• The data in the state will remain there when new players join, or a player disconnects & reconnects back to the game.
• The state is broadcasted automatically at every "patch interval" (default is 50ms - see docs)
• Messages are sent immediately, and only once. There's no built-in way to re-send a particular message when a player disconnects & reconnects for example.

Hope this helps,
Cheers!

Hi @jiabuda, I'm glad you're enjoying it and using it for your second game!

You're right about the Context. By default the @type() annotation is going to use a "global context". By having all structures inside the global context, they're all going to be synched during handshake.

I'm restructuring most of @colyseus/schema lately, and I'm going to add a utility to help with this, as follows:

import { type, Context, DefinitionType } from "@colyseus/schema";

function createContext() {
    const context = new Context();
    return function (definition: DefinitionType) {
        return type(definition, context);
    }
}

You can use this function to generate a special @type() that is going to bind to a specific context, so you can use a different one for each of your games. Example:

// "game1.ts"
export const type = createContext();

// other file
import { type } from "./game1";

class State extends Schema {
  @type("string") // ... your definitions as usual
}

This utility is going to be available as Context.create() on a next version!

Hope this helps. Cheers!

Hi @nguyen991, it seems the internal-ip is not being able to retrieve the IP address for your server. Here's the reference to the source-code where this null is coming from: https://github.com/colyseus/colyseus/blob/530f13745e655c526f5b5aef9fa5cc05de5396d6/src/discovery/index.ts#L13

@scarybanana (member on Discord) is having the same issue inside Kubernetes. I can't tell exactly why this is happening, I'd appreciate if you can help to inspect this issue

Cheers

Hi @nik0kin, the command dispatcher supports returning new commands. Wouldn't it be suitable for your use case?

Example:

execute() {
  // perform your actions...

  return [new AnotherCommand().setPayload({ ... })];
}

Hi @kukuts, thanks for reporting, is this issue you're having similar to this? https://github.com/colyseus/schema/issues/71

If the key of the map you're deleting/creating is the same, I'm afraid you'd need to do some workaround in the meantime, I'm planning to fix most of @colyseus/schema annoyances here, which should be released in a few weeks https://github.com/colyseus/schema/issues/75

Cheers

hi @virtumonde, you could use instance.toJSON() and store that. you'd need to have your own way to restore/instantiate those objects by yourself when retrieving them from the database if you need to

@cooul can you post the stack trace and your system details (OS, Node version) as a comment on this thread? https://github.com/colyseus/colyseus/issues/318#issuecomment-608084651

Thanks!

Hi @virtumonde, the @colyseus/schema supports inheritance, if the Gate extends Tile it should work as expected!

Hope this helps, cheers!

Hi @cooul, please check this thread on GitHub https://github.com/colyseus/colyseus/issues/318#issuecomment-608084651

Hi @Fitninja, you can override the roomId during onCreate(), you'd have to make sure the id you provide is unique, though.

onCreate() {
  this.roomId = "/* your own id generation here */"
}

Cheers