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...

@mdotedot now to think of it. Perhaps static/02-state-handler.html does not work for you because you don't use haxe rc2 to compile server. Thing is that haxe prior to rc2 will still compile the js server code but it will be ES5 javascript. Code generated in this way does not work with states for example; perhaps I need to add some compilation error for this case. So you need to be sure that js got generated with ES6 features with classes and all that. Check generated index.js - it should contain classes, something like this: class server_rooms_StateHandlerRoom extends colyseus_server_Room

@usamasermad yes, you should ensure the Client connection is open before performing a ReJoin. If you're going to instantiate a new Client, make sure it has the same client.id as the one who initiated the first connection to the room (https://github.com/colyseus/colyseus-unity3d/blob/master/Assets/Plugins/Colyseus/Client.cs#L66)

Awesome @halome, it's looking good! Another option would be MatterJS: https://github.com/liabru/matter-js Good luck with your project! Don't hesitate if you need any help with Colyseus here!

Hey @rscata, I've just released a new version (colyseus@0.8.13, see release) which adds the isNew parameter on requestJoin. With this version you'd be able to achieve the same result by having this implementation: // ... maxClients = 4; requestJoin (options, isNew) { return (options.create && isNew) || this.clients.length > 0; } // ...

From my setup: root@raspberrypi:~/colyseus-hxjs-examples# haxe -version 4.0.0-rc.2 root@raspberrypi:~/colyseus-hxjs-examples# haxelib list colyseus-hxjs: [git] hxnodejs: [10.0.0] tink_core: [1.23.0] tink_lang: [0.6.2] tink_macro: [0.17.7] tink_priority: [0.1.4] tink_syntaxhub: [0.4.3] root@raspberrypi:~/colyseus-hxjs-examples# cat src/colyseus/server/schema/Schema.hx | grep MapSchemaUtil class MapSchemaUtil { Your tink_core is different than mine. Don't know if that is the only thing that is different?

@endel said in colyseus.js: server error: registeredHandler.klass is not a constructor: Or by exporting the room usin I'll try it the week end and come back to you later. Thx for the help so far.

Hi @endel thanks for you quick reply, as you said... yeah.. too many issues already LOL I'll go for the database option to persist the data between room changes, I'm working on it now, the idea is to save the player progress > leave the room > join the new room > re-authenticate the user with the data in the session and reload the progress. I though it will be too expensive in terms of server response time, but keep a room or persist too much information in the presence could end up been even more expensive than just hit the DB to get the data. Best,

Hey @merhawie, Are you calling client.join() after the onOpen signal, as described here? https://github.com/gamestdio/colyseus.js#react-native-compatibility

That's great to hear @visgotti, thanks a lot ❤️❤️❤️

@umen we have 3 servers now (each droplet of DigitanOcean 1 vCPUs 1GB / 25GB Disk), each server can keep about 500-600 users, but it's depends on logic of your server.

@endel I was looking at this in a tired state, but im pretty sure i had fully updated client and server. Ill double check what i was seeing and if i still have an error I'll open an issue on the github. Thanks for the response.

@Алексей-Андронов the clock only works if you set up the simulation interval. I guess that's not intuitive, I'll fix this on version 0.9.0 too.

@Carlos-Montesino, i've tried your endpoint (wss://carmenproject.herokuapp.com) but it is not working properly. the "please wait" text is not destroyed. it seems that it is cannot join any room.

Thanks :smile:

@endel So, I got this working by calling gameServer.matchMaker.create("game", {}); after registering (I only do this on the second process). It seems that the you are only subscribing to presence when the room is created. There is no knowledge that a registered handler is registered within presence. So, I have manually created the room on startup. This probably is not the best way, but it works for now while you can think about how we would want to solve for making the other game servers aware that a room is registered but not yet created.

A colyseus + DB with authentication would be the ideal example IMO something like the existing tic tac toe example with a simple user creation (DB) and login (authentication) would be enough and it would be all someone needs to make a complete multiplayer game experience

@marwan38 Needless to say that I'm flattered! I'm glad that my little project has been able to help you so far, as I am really not a game dev at first. Lately I've improved the whole architecture by removing a lot of code, making a cleaner and more flexible hud, using r-trees for collisions on the client and server side, and making actions more responsive. Though there are still a few minor bugs, but nothing really critical. And nice to hear the game was working great on mobile! I'm really working hard to have a similar experience on both desktop and phones. PS: I'll check your pm

@endel Yay !! thats work Thanks.

@endel thanks, we're done with it server scalability. Next step is redis.