Hi @metiscoda,

You can't have circular dependencies between your schema files. Your KamadiTest is requiring KawadiPlayer, which requires KamadiTest again.

I suggest refactoring your structures so you don't have circular dependencies. Cheers!

Hi Maël, welcome! 👋

Are you using @filter() or @filterChildren()?

Can you please share your source-code with us, so we can have a bigger picture of the operations on MapSchema? I'm curious to see what's going on as I've never seen this error before!

Feel free to ping me on Discord (endel#2163) or email (endel[at]lucidsight.com)

Cheers!

Hi @vishwasgagrani!

By the error message, it seems that devDependencies listed under package.json were not installed during npm install:

sh: ts-node-dev: command not found

If you use npm install --only=dev the development dependencies should be installed as well.

Let me know if that works for you!

Hi @vishwasgagrani, welcome! What is the error you're getting exactly?

Hi @Scopique, glad you're considering using it for your next project!

What you described is exactly how Colyseus has been designed to operate! :)

Taking mazmorra.io as an example - it is a "dungeon crawler" type of game. Every dungeon has the same logic behind it, the only difference is their "progress":

• Filtering dungeons by its "progress": https://github.com/endel/mazmorra/blob/b6fef8bd884261b948e4a8c816a0fac93fc543c7/server/index.ts#L58
• Joining a dungeon room by "progress": https://github.com/endel/mazmorra/blob/b6fef8bd884261b948e4a8c816a0fac93fc543c7/client/game/level/Level.js#L52-L54 - the enterRoom() method is going to call .joinOrCreate()
• Here's the implementation for the "dungeon room": https://github.com/endel/mazmorra/blob/b6fef8bd884261b948e4a8c816a0fac93fc543c7/server/rooms/DungeonRoom.ts

Full sources: https://github.com/endel/mazmorra

Hope this helps! Feel free to ask if you happen to have specific questions during development!

Cheers!

Welcome @tungnt2k,

Please provide more details. What is your room's code doing? When usually the CPU goes higher? Does it happen suddenly? Does it happen after you got many connected clients? Please elaborate.

Hi @Akadream, there's no such thing currently, and I've never actually thought about this. I imagine this would be useful to bridge the gap between "server-side" and "client-side" developers, is it?

Hi @banool, sorry for the delayed response!

Inheritance is supported on ArraySchema and MapSchema. So the approach of having an Item as base class works! (I'm using a MapSchema for this, to be able to add/remove directly by key rather than a moving index, see mazmorra.io sources)

In order to be able to differentiate the instances on the client-side - if you are using JavaScript/TypeScript, you can share the actual Schema implementation with the client, and provide its concrete implementation as a third parameter for the matchmaking method:

// this is the same RoomState as you have in the server
class RoomState extends Schema {}

const room = await client.joinOrCreate("my_room", {}, RoomState);

This way, the actual instances of Bucket, Hose, and whatnot are going to be created during decoding time.

Hope this helps, let me know if you have any questions!

Cheers,
Endel

I agree with @netd777. Deno looks very promising but to this date is not quite there yet. Perhaps in the future, if we find a compelling reason to migrate.

No worries! In fact room.state.on_change and room.state["on_change"] are just different in syntax, they are actually equal!

I can put up a PR to make this a bit clearer on the docs.

That'd be much appreciated! 🙏

Cheers!