Questions & Help

• 

  Dynamic refreshing of room list for lobby
  • creationspirit

  2
  0
  Votes
  2
  Posts
  364
  Views

  

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

  Questions about rooms
  • emarkk

  3
  0
  Votes
  3
  Posts
  489
  Views

  

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

  Typescript Interfaces for TS client
  • genox

  3
  0
  Votes
  3
  Posts
  496
  Views

  G

  Will give it a try, thanks!
• C

  colyseus.js and Cocos Creator
  • colyseus

  3
  0
  Votes
  3
  Posts
  1247
  Views

  J

  https://gitee.com/limo/simple_server build with colyseus .js 0.9.33 version.
• 

  React-native & Colyseus.js : Issue with room.join
  • Meabo

  3
  0
  Votes
  3
  Posts
  408
  Views

  

  Hello @endel thanks for your answer, So I deleted node_modules and package-lock.json, reinstalled colyseus.js at its latest version but the error's still there. But I got something interesting: It works with @colyseus/schema 0.4.23 instead of 0.4.29. so I downgraded Schema until I find a solution :)
• A

  Fail-over and load balancing colyseus Testing
  • ahtashamabbasse

  1
  0
  Votes
  1
  Posts
  324
  Views

  No one has replied

• 

  How to get rooms count and clients count that connect to server
  • takaaptech

  7
  0
  Votes
  7
  Posts
  1576
  Views

  A

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

  @filter not working as expected
  • emarkk

  4
  0
  Votes
  4
  Posts
  366
  Views

  

  @nosync is for FossilDelta only, it has no effect using the Schema serializer
• 

  Is it possible to use colyseus without a client
  • elieobeid7

  3
  0
  Votes
  3
  Posts
  396
  Views

  

  Ok thank you so much, have an awesome day.
• 

  Is this possible to get `onAuth` reject reason to client?
  • serjek

  1
  0
  Votes
  1
  Posts
  252
  Views

  No one has replied

• K

  With the 0.10 schema release, has changing the state in the server changed?
  • KG204

  2
  0
  Votes
  2
  Posts
  387
  Views

  

  Hey @KG204, yes! State mutations look exactly the same as they used to on previous versions! Cheers!
• C

  How to influence roomId for new room?
  • cmdt.ed

  6
  0
  Votes
  6
  Posts
  553
  Views

  C

  OK, I'll look into doing that. I don't have much experience with redis, promises, async and even javascript but I'll see what I can do. Thanks.
• 

  Server State Class How To Reference Room
  • mackycheese

  2
  0
  Votes
  2
  Posts
  323
  Views

  

  First off, you shouldn't do this. It's meant to be a state, which holds data. Not a lot more than that. That said, if you really want to, you can add a @nonenumerable or @nosync attribute to the room variable. to make it not serialized.
• K

  Colyseus.js "Cannot read property '_schema' of undefined".
  • KiloGram

  3
  0
  Votes
  3
  Posts
  411
  Views

  K

  Thank you so much! That actually worked!
• 

  Client throws when setState is called in server room
  • mackycheese

  3
  0
  Votes
  3
  Posts
  451
  Views

  

  @endel I see. Thanks! I switched to the old serializer and it works fine now. Out of curiosity, why would you switch serializers?
• H

  colyseus.js: server error: no available handler for client
  • henrydavidzhu

  2
  0
  Votes
  2
  Posts
  320
  Views

  

  Colyseus is not supposed to be used along with socket.io. Why would you need socket.io AND colyseus?
• H

  Colyseus.js error after migrating from 0.09 to 0.10
  • henrydavidzhu

  2
  0
  Votes
  2
  Posts
  318
  Views

  

  hey @henrydavidzhu, you can always find the latest colyseus.js file here: https://github.com/colyseus/colyseus.js/tree/master/dist colyseus.js: server error: no available handler for "1mnyb24wwjtwkdbld" This error means you're trying to join a room handler named "1mnyb24wwjtwkdbld" that doesn't exist. You must register the room handler in the server. gameServer.register("1mnyb24wwjtwkdbld", YourRoomHandler) class YourRoomHandler extends Room { // ... } I highly recommend you read the documentation: https://docs.colyseus.io/server/api/ https://docs.colyseus.io/server/room/
• 

  onLeave timeout
  • rscata

  5
  0
  Votes
  5
  Posts
  1151
  Views

  A

  @DinhNguyen and @rscata I think you both are looking for rejoin the game. Below snippet will solve your problem. For more details: Rejoin Link. async onLeave (client, consented: boolean) { // flag client as inactive for other users this.state.players[client.sessionId].connected = false; try { if (consented) { throw new Error("consented leave"); } // allow disconnected client to rejoin into this room until 20 seconds await this.allowReconnection(client, 20); // client returned! let's re-activate it. this.state.players[client.sessionId].connected = true; } catch (e) { // 20 seconds expired. let's remove the client. delete this.state.players[client.sessionId]; } }
• 

  POST method not allowed in express app after passing it to Colyseus constructor
  • kappacoder

  4
  0
  Votes
  4
  Posts
  699
  Views

  

  Oh god, that actually solved it! Thank you very much! I thought I was going crazy :D
• 

  Listeners triggered even though listening to different state properties
  • karneaud

  3
  0
  Votes
  3
  Posts
  620
  Views

  C

  Sorry to reply to an old post but this was the one that finally helped me understand how to use listen so I thought it might be helpful to clarify for other users who are as dense as I am. The documentation for listen at https://docs.colyseus.io/client-state-synchronization/ is painfully terse and confusing especially in how it uses the colon (:). From my understanding, if you have something like the following as your state: {foo: bar: {baz: 'somevalue'} } then you can listen for baz via room.listen('foo/bar/baz', ...) or via something like room.listen('foo/:wildcard_1/:wildcard-2', ...) That is you can either use the exact path or use wildcards but the text after the colon has no special meaning. I kept thinking that the :id and :attribute wildcards in the docs had a special meaning. Hope that helps others who got confused like me. Thanks again.