administrators

@quangthaiptit is the property initially set before you call nosync?

Hi, @itoonom, welcome!

The data stored via the presence API is not disposed automatically. It's up to you when to remove them.

Hi, @itoonom, welcome!

If you're using Visual Studio Code, you can Right click + Go to definition (F12) on the RedisPresence, and redis.ClientOpts, which you'll see all accepted config values for RedisPresence constructor, which are:

export interface ClientOpts {
    host?: string;
    port?: number;
    path?: string;
    url?: string;
    parser?: string;
    string_numbers?: boolean;
    return_buffers?: boolean;
    detect_buffers?: boolean;
    socket_keepalive?: boolean;
    no_ready_check?: boolean;
    enable_offline_queue?: boolean;
    retry_max_delay?: number;
    connect_timeout?: number;
    max_attempts?: number;
    retry_unfulfilled_commands?: boolean;
    auth_pass?: string;
    password?: string;
    db?: string | number;
    family?: string;
    rename_commands?: { [command: string]: string } | null;
    tls?: any;
    prefix?: string;
    retry_strategy?: RetryStrategy;
}

You should pass a plain JavaScript object BTW, no need to call new ClientOpts. Example:

new colyseus.RedisPresence({
    // your Redis configs here
});

Hi @njohnst,

Here's a post about using nosync in pure JavaScript: https://discuss.colyseus.io/topic/102/how-to-use-nosync-in-nodejs

The EntityMap is just a type for {[ entityId: string ]: T}, you can replicate the same thing in JavaScript using:

this.entities = {};
this.entities[entityId] = yourEntity;

Hope this helps, cheers!

Hi @RobinFalko,

The clock instance already have a deltaTime property which updates at every tick. See clock's public properties here: http://colyseus.io/docs/api-timing-events/#public-properties

Hope this helps! Cheers!

(Replied on GitHub: https://github.com/gamestdio/colyseus.js/issues/42)

Hey @karneaud, when using :anything, starting with :, it will generate a wildcard regular expression, that's why both listeners are being triggered.

You have two alternatives on this situation, which are:

Listening to direct properties

room.listen('pullPosition/position', (change) => {
    console.log('position attribute has changed', change.value);
});
room.listen('pullPosition/hold', (change) => {
    console.log('hold attribute has changed', change.value);
});

Remember that if position is a vector, you'd need to listen to its deep variables such as x and y, by using listen('pullPosition/position/x') and listen('pullPosition/position/y'). You can also use the wildcard method for this, using the same example below.

Listening to every attribute, and check which one has changed in the change.path

room.listen('pullPosition/:attribute', (change) => {
    console.log(change.path.attribute, 'has changed to', change.value);
});

Hi @varunhegde93, welcome!

Wouldn't it be easier to write the AI agents directly in the server, using JavaScript/TypeScript? I don't see the need to have an external service for the AI.

Or, maybe you could make the agents directly in the UI client itself, having multiple connections to the same room/server.

Cheers!

Hi @hardik_sl,

You may modify the requestJoin method to allow creating the room regardless of the param create is being passed as true or not. I've made this example to demonstrate that clients may have control to create or join into rooms. By omitting the requestJoin method, it will always return true.

Hi @zpr, welcome!

I think the problem you're facing is exactly what @Nebri just asked about in the Gitter channel.

You're probably facing the famous this problem in JavaScript. When referencing the function directly on setSimulationInterval you will lose the this reference.

You can call it like this instead:

this.setSimulationInterval(() => this.tick())

or

this.setSimulationInterval(this.tick.bind(this))

Hi @amit-gshe, welcome!

Have you tried this.emit('dispose')? It should work as you expect!