Navigation

  • Recent
  • Tags
  • Users
  • Search
  • Login
Colyseus
  • Login
  • Search
  • Recent
  • Tags
  • Users

Documentation GitHub

We're migrating to GitHub Discussions. This forum does not accept new registrations since April 6, 2023.
  1. Home
  2. boygiandi
  3. Posts
  • Profile
  • More
    • Continue chat with boygiandi
    • Flag Profile
    • Following
    • Followers
    • Topics
    • Posts
    • Best
    • Groups

Posts made by boygiandi

RE: How to disconnect from Client

I still face this problem. Should I do this

delete room
room = null

After leave() room ?

posted in Questions & Help • 22 Apr 2020, 07:32
RE: Invalid WebSocket frame: invalid payload length 126

@endel Is there any way to fix it ?

posted in Questions & Help • 15 Apr 2020, 01:04
RE: Invalid WebSocket frame: invalid payload length 126

Ah.. I'm sorry. I didn't make server crash. Just make the client disconnected.

posted in Questions & Help • 14 Apr 2020, 12:40
RE: Invalid WebSocket frame: invalid payload length 126

Yes. It crash server

posted in Questions & Help • 14 Apr 2020, 12:37
RE: When running server: "TypeError: Cannot read property 'types' of undefined"

@globallyltd I have this error when I use and empty State. Then I try create a property in that state object and it works.

posted in Questions & Help • 14 Apr 2020, 11:50
RE: Invalid WebSocket frame: invalid payload length 126

React native, When I got this error I'm testing on iOS simulator. It just happen sometime.

posted in Questions & Help • 14 Apr 2020, 11:47
Invalid WebSocket frame: invalid payload length 126

Sometime I get this error. What is it and how to fix ?

  colyseus:errors RangeError: Invalid WebSocket frame: invalid payload length 126
  colyseus:errors     at Receiver.getInfo (/home/godate/node_modules/ws/lib/receiver.js:216:16)
  colyseus:errors     at Receiver.startLoop (/home/godate/node_modules/ws/lib/receiver.js:130:22)
  colyseus:errors     at Receiver._write (/home/godate/node_modules/ws/lib/receiver.js:77:10)
  colyseus:errors     at doWrite (_stream_writable.js:415:12)
  colyseus:errors     at writeOrBuffer (_stream_writable.js:399:5)
  colyseus:errors     at Receiver.Writable.write (_stream_writable.js:299:11)
  colyseus:errors     at TLSSocket.socketOnData (/home/godate/node_modules/ws/lib/websocket.js:876:35)
  colyseus:errors     at TLSSocket.emit (events.js:197:13)
  colyseus:errors     at addChunk (_stream_readable.js:288:12)
  colyseus:errors     at readableAddChunk (_stream_readable.js:269:11)
  colyseus:errors     at TLSSocket.Readable.push (_stream_readable.js:224:10)
  colyseus:errors     at TLSWrap.onStreamRead [as onread] (internal/stream_base_commons.js:145:17) +0ms```
posted in Questions & Help • 14 Apr 2020, 09:44
RE: Seat reservation expired when many servers using the same redis

Wow. It's exactly my situation. I just fixed it by using @endel suggestion.
Thank you

posted in Questions & Help • 11 Apr 2020, 09:38
RE: How to debug MatchMaker

@endel said in How to debug MatchMaker:

ming from your application. If you're using TypeScript, the compiler should be able to warn you where the issue is.
This could be happening if you have if (yourCon

No, it come from the MatchMaker request

posted in Questions & Help • 3 Apr 2020, 10:38
RE: How to debug MatchMaker

Please help me. My product is in public test and prepare for official publish. And I got this problem

posted in Questions & Help • 3 Apr 2020, 03:51
How to debug MatchMaker

Sometime, it has error with matchmaker. Like this

alt text

The problem is I don't know where the line of code that cause error. How can I debug. It just happen sometime and when I restart the service, it works again.
I tried run with DEBUG=colyseus:* node index.js but no error output. I tried to add log in your code and find out that in the CreateRoom function,
const roomsSpawnedByProcessId = yield exports.presence.hgetall(getRoomCountKey());
roomsSpawnedByProcessId is null, I used Redis.
No idea why

posted in Questions & Help • 3 Apr 2020, 01:39
RE: How to disconnect from Client

As you can see in this console log from client, I removeAllListeners then I leave room. But after that, I still get message from server. How is that possible ?
console log

posted in Questions & Help • 2 Apr 2020, 02:10
RE: How to disconnect from Client

I'm having problem like this.

  1. Server start and async call ( fetch api )
  2. When the async call is still in processing, client send command leave room.

( problem is sever wait until async call is finished then process the leave room command - I guest ? )

  1. After the async command, server send message to client -> client still receive the message even it call leave room already
  2. Server process the leave room command

How to make the leave room immediately and force stop all async call on server.
Thank you

posted in Questions & Help • 1 Apr 2020, 16:08
How to disconnect from Client

From Client, how to disconnect to server ( not only leave room but close websocket connection ).
I can't find the API to do that.

Thank you

posted in Questions & Help • 1 Apr 2020, 15:46
RE: Can I access gameServer from Room ?

@endel said in Can I access gameServer from Room ?:

e gameServer, but you can access the matchMaker via

Thank you.

posted in Questions & Help • 1 Apr 2020, 15:16
Can I access gameServer from Room ?

Is there anyway to access gameServer from inside a Room class ?

posted in Questions & Help • 1 Apr 2020, 08:43

© 2023 Endel Dreyer