You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Just encountered a bug where a user tried connecting via session id in connect by address and it led to the server crashing and wiped inventories of most players. My inventory, money and compendium were all reset. I'm unsure if the crash and the connect by address were linked but they happened at the same time which made me suspicious of an issue occurring with that.
To Reproduce
Steps to reproduce the behavior:
Take session id from pause menu in top left corner
Connect to session id from address connect option
Expected behavior
Player was unable to find server on server list so we decided to give it a shot via direct connect which should've connected the player but led to a crash instead.
Screenshots
Over 1000 lines of Array bounds exceeded at the tail end of the log before it crashed
Server (please complete the following information):
Describe the bug
Just encountered a bug where a user tried connecting via session id in connect by address and it led to the server crashing and wiped inventories of most players. My inventory, money and compendium were all reset. I'm unsure if the crash and the connect by address were linked but they happened at the same time which made me suspicious of an issue occurring with that.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Player was unable to find server on server list so we decided to give it a shot via direct connect which should've connected the player but led to a crash instead.
Screenshots
Over 1000 lines of Array bounds exceeded at the tail end of the log before it crashed
Server (please complete the following information):
Client (please complete the following information):
Additional context
I'm going to dive deeper into the log file to see if I can find anything leading to the issue source
The text was updated successfully, but these errors were encountered: