Questions & Help

• J

  How to generate unique 6 digit game code?
  • jellitan

  6
  0
  Votes
  6
  Posts
  689
  Views

  

  Thanks a lot for the insights @visgotti I was tinkering about this, and I think it's possible to use custom-generated roomId's by mutating it during onInit(), I haven't tested though: Example: import * as generateId from "nanoid/generate"; class MyRoomHandler extends Room { onInit () { // this may introduce colliding `roomId`, use at your own risk this.roomId = generateId("1234567890ABCDEFGHIJKLMNOPQRSTUVWXYZ", 6); } } Make sure to include nanoid as a dependency.
• 

  Can't run basic examples.
  • IanBellomy

  2
  0
  Votes
  2
  Posts
  352
  Views

  V

  @ianbellomy maybe it didn't bundle colyseus.js for whatever reason.. you can just grab it here https://github.com/gamestdio/colyseus.js/blob/master/dist/colyseus.js put it in a lib folder or anywhere and make sure you import it in the html
• I

  About data when using Presence API
  • itoonom

  4
  0
  Votes
  4
  Posts
  479
  Views

  I

  @endel Thank you very much. Your help gives me more confidence to keep going on. The scaling topic is all new to me, so every single explanation/example counts!
• D

  This topic is deleted!
  • davidhoare

  1
  0
  Votes
  1
  Posts
  1
  Views

  No one has replied

• T

  How to use @nosync in nodejs
  • Tyrus Shan

  5
  0
  Votes
  5
  Posts
  1275
  Views

  

  @quangthaiptit is the property initially set before you call nosync?
• C

  URL for new Client()
  • Coruscare

  1
  0
  Votes
  1
  Posts
  240
  Views

  No one has replied

• A

  Web Game Server
  • Alpha

  3
  0
  Votes
  3
  Posts
  424
  Views

  A

  I want it to be multiplayer like Cats as I mentioned. but tnx for the reply.
• I

  Guide for RedisPresence config
  • itoonom

  1
  0
  Votes
  1
  Posts
  318
  Views

  No one has replied

• L

  State management question
  • learning

  1
  0
  Votes
  1
  Posts
  259
  Views

  No one has replied

• 

  Can someone point me to a working Colyseus example that I can download?
  • WillWam

  3
  0
  Votes
  3
  Posts
  479
  Views

  

  Thanks for that. The Docs didn't use npm run bundle-colyseus-client so perhaps it was implied.
• V

  Have multiple rooms live and be managed inside a room?
  room multiroom area connector • • visgotti

  1
  0
  Votes
  1
  Posts
  344
  Views

  No one has replied

• 

  Bug on Unity Colyseus after reconnect client
  • Soh Sea Kiat

  6
  0
  Votes
  6
  Posts
  1109
  Views

  O

  Hi , i up the post because i have the same issue , after a rejoin ( successfully ) i can't send any data between server and client, thanks
• N

  Problem listening rooms on Unity After Connect
  • NivekJump

  2
  0
  Votes
  2
  Posts
  281
  Views

  No one has replied

• 

  TypeScript features in JavaScript
  • njohnst

  3
  0
  Votes
  3
  Posts
  486
  Views

  

  That solved my problem. Thanks @endel ! Nicholas
• 

  Creating a room from another room?
  • gioragutt

  2
  1
  Votes
  2
  Posts
  448
  Views

  

  Found sort of a solution - use RegisteredHandler's create event to subscribe to the room's event. The changes can be found here. I wanna make an important note here: Creating an async main method in index.ts and awaiting gameServer.register was crucial.
• 

  clock.setInterval deltaTime
  • RobinFalko

  3
  0
  Votes
  3
  Posts
  483
  Views

  

  Hi endel, thanks for your reply. You're right but the delta time is computed for the tick of room.setSimulationInterval, not clock.setInterval if I understood that correctly. e.g. //clock.start() is called indirectly and ticking starts: this.setSimulationInterval(deltaTime => { [...] //let's say deltaTime is about 15 }); this.clock.setInterval(function() { [...] //the deltaTime of this closure should be about 2000 //but instead this.clock.deltaTime is about 15 since it's computed at the tick of setSimulationInterval }, 2000); So each setInterval should have its own deltaTime since it has its own refresh rate.
• 

  Metadata is not readable on Unity3D client
  • gioragutt

  1
  0
  Votes
  1
  Posts
  304
  Views

  No one has replied

• 

  Configuring Room and Timeline
  • njohnst

  2
  0
  Votes
  2
  Posts
  428
  Views

  

  I found the options / parameters :) In case anyone else makes the same mistake, you can pass options/parameters into a Room when you call Server#register(name, handler[, options]) - see http://colyseus.io/docs/api-server/ I'm still wondering about the first part of my question regarding Timeline - is that part completely left up to me to implement (with the exception of snapshots being taken in Room#setState)? Thank you, Nick
• A

  Colyseus.js Websocket is not defined
  colyseus.js • • Abymes

  2
  2
  Votes
  2
  Posts
  897
  Views

  I

  I know this topic is 3 months old, but I have found a workaround so if anyone searches for this they will have an answer. The reason your unit test is not working is that WebSocket is not globally installed when you run it in say Jest for example. A quick work around would be to define it globally. // npm install ws const globalAny: any = global; // This way we don't get an error in TypeScript saying WebSocket is not a defined property on global globalAny.WebSocket = require('ws'); Also, it appears as though the colyseus.js client makes use of the window.local storage object. A quick polyfill you could do would look something like this globalAny.window = { localStorage: { getItem: () => {}, setItem: () => {} }, };
• S

  Lag compansation example using @gamestdio/timeline in client
  • shortid

  3
  0
  Votes
  3
  Posts
  747
  Views

  

  @endel @shortid There is also a case for using interpolation on the client-side, not just prediction. In the case of the Source engine (e.g. Counter Strike), there are buffered patches on the client side. Ex. Client receives state update N, it buffers the update and instead interpolates between N-1 and N (this mitigates packet loss issues from UDP - the engine has settings to allow buffering of multiple updates in more unstable network conditions) https://developer.valvesoftware.com/wiki/Source_Multiplayer_Networking Edit: Then client side prediction is layered on top of this to make user-controlled objects feel more responsive. Edit2: Even though Colyseus uses TCP on the client side, it still could be beneficial to use interpolation on the client side (with only one buffered update, as multiple buffered updates won't really accomplish anything on TCP) as otherwise the enemies would get stuck in one place on the screen for waiting for the next update. There's also a case for using dead reckoning / extrapolation, but it has issues as well.