Client-side Playground is now available! #585
Replies: 5 comments 6 replies
-
|
Awesome to found this Client-side Playground is now available. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @BugSlayer87, it only works on version 0.15 |
Beta Was this translation helpful? Give feedback.
-
|
I was under the impression that this would also show existing rooms, or is this designed with another goal in mind? |
Beta Was this translation helpful? Give feedback.
-
|
You can use https://github.com/colyseus/colyseus-monitor to inspect existing rooms, including state. Playground (from what I understand) is more of a way to test interactions from a client <-> room |
Beta Was this translation helpful? Give feedback.
-
|
Thank @avatus , you helped me a lots. I saw state tab now in monitor. But don't know how to keep that state when user (player) join room again, ex. last position in map to render exactly. And I tried to deploy Colyseus server on GCP K8s, when I deploy again, I see the room was disposing (delete in my MongoDB) -> so user will createNewRoom by RoomName, don't know if we have ways to solve this. |
Beta Was this translation helpful? Give feedback.
-
|
Hello! I'm playing around with Colyseus and I like it so far. Is there a way to share state only partially with a client? Let's say I have Room with locations that needed to be actually reached before client would be able to see what items in there |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Hi @Yashko, thanks for your interest - right now partial state sync is only supported via the A new "data ownership" model is on the roadmap as part of improvements on the state sync structures - though no progress has been made there yet https://github.com/colyseus/colyseus/wiki/Public-Roadmap#colyseus-framework |
Beta Was this translation helpful? Give feedback.
-
|
Hi @endel , Recently, I have been using colyseus/colyseus as a game server and colyseus/playground to test messages between client-room-server. Displaying schemas is a necessary feature to allow clients (game clients) to know which properties they will use in the schema to make requests and receive corresponding responses. I want to use my code to contribute to the colyseus/playground repository. For those who might want to use a similar feature in the future. Currently, I have only created a pull request here, you can review the code and the attached image. If possible, please let me know the process for contributing to the colyseus/playground repository, including code conventions, etc. I will follow them. Thanks, |
Beta Was this translation helpful? Give feedback.
-
|
hi @endel , thanks for the playground repo, and quick feedback for the last version: I think typescript definition is missing in the latest version (0.15.16). There is no index.d.ts file under the build dir anymore. I also can't find any types package for this playground package. VS Code is suggesting to install npm i --save-dev @types/colyseus__playground but obviously that package is not exist. (Issues tab is not active in the playground repo btw, so I can't report it there.) |
Beta Was this translation helpful? Give feedback.
-
|
Hi @huseyindeniz, thank you for the detailed report. I just published version |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
playground.mp4
How to test it
The playground tool is installed by default on new projects created via
npm create colyseus-app.To manually install on an existing project, please do:
Then, import and bind it to your express app instance:
Your feedback is welcome!
Is there a feature you'd like to see, or an improvement that would make your life easier inspecting/debugging your room implementation?
Beta Was this translation helpful? Give feedback.
All reactions