The Lock System is still a good challenge. After two code-refactors I have put it on hold for now. Last week I've worked on an actual TurnBased system game (TicTacToe) [running html5 and windows publication next to eachother] (published for HTML5, Windows and Android; should work on the others) During development I started to rethink my approach of a single extension versus multiple extensions. I believe that a Stencyl user wants to create a specific type of game and install / enable the extension that is used for that type of game. This make the palette a lot cleaner. (Unfortunately Stencyl Extension Developers don't have the means to create sub-palettes or tabs) TODO for TurnBased System : set timeout value; when a player needs to react before certain time (auto-logout) TODO for general : make roomtype specific extensions (raw, turn, physics, lock/logic) that have still the general purpose blocks (init, join, create, leave room, etc..) TODO for games: Make another turnbased game (Poker?) Also, I need to figure out the Lock/Logic room type eventually...

I'd check out the examples first. Have you decided which platform you want to use for client development? Client libs and example projects are linked from here: https://docs.colyseus.io/client/client/

I was able to fix it! Babylon.js was loading a lot faster than colyseus, so using the scene.registerAfterRender(function() {} was calling room.send before the client had even connected. I now use the pointer lock canvas.click function to start the position updates! demo at https://boilerplate-fps-works.herokuapp.com/ WASD moving, mouse look

@endel Thanks for your answer . I use this solution for set data to setMetadata and This code work well: Client side (local): room = client.join('create_or_join', { create: true, name:'hi2020', gametype:1 }); Server side (TS file): onInit (options) { this.setMetadata({ name: options.name, gametype: options.gametype, });}

FYI, latest API supports this now. Simply pass the room handle or roomId. https://docs.colyseus.io/client/client/#join-roomnameorid-string-options-any

Hi @KiloGram, ArraySchema does not support multi-dimensional arrays. The general suggestion is to use a 1D array and treat is as 2D when iterating on it. Please check this reference: https://softwareengineering.stackexchange.com/questions/212808/treating-a-1d-data-structure-as-2d-grid Cheers

https://github.com/colyseus/colyseus-examples does create and join js here in this example help?

Thanks a lot! Works great!

This module is very famous for having multiple transport layers for logs: https://github.com/winstonjs/winston Maybe you can use it during your room lifecycle. I've never used it though, so I can't give more detailed information

Thanks! I can try that later! EDIT: Works like a charm! Thanks!

endel your my hero and i love you. just in case ;) in case any one else makes this mistake i was trying to mutate the client object and assign a accessToken to it so the error occurred. i hope better errors will be shown and i didn't know that the client object cant get mutated. i'm planning to develop lots of mobile turned based games and i'll join this fantastic framework asap

@endel I messaged him, waiting for reply. Hope he'll help

Hi @endel, you are fast!! I had it like u suggested at first. MapRoom has MapState with World (static platforms, ground etc) PlayerState EnemyState NpcState BlockState (all dynamic bodies that aren't players npcs or enemies) The player in TownRoom doesn't need to know about the state from MapRoom so I thought to create a room for each map to make the game as lightweight as possible. But thinking now maybe there is a way I can get the data from onAuth and then initiate MapState or TownState based on that without sharing for example NpcState to all the players online.

@genox I face the same challenge/problem as you. I see there wasn't much response in this topic, did you maybe come up with something along the way?

You could use something like setInterval to get the room list on a loop. There is no way to watch for it to be emitted though.

apparently it was due to the websocket disconnecting. it happens every time a "normal" request is sent (like performing an http get request or loading an ad). for now I am just forcing the websocket to reconnect, but maybe a simpler way exists.

Will give it a try, thanks!