FakeFishGames / Barotrauma

A 2D online multiplayer game taking place in a submarine travelling through the icy depths of Jupiter's moon Europa.
http://www.barotraumagame.com/
1.76k stars 406 forks source link

Renaming in lobby bug #11643

Open Maximegede opened 1 year ago

Maximegede commented 1 year ago

Disclaimers

What happened?

When renaming a character in lobby and you're doing it too fast. Then when you try again it doesn't change everywhere. Some places it will be the correct name, and other places it will be the wrong one.

Reproduction steps

  1. Start a multiplayer lobby with two or more players
  2. Rename to one player to a wrong name : E.G. "Wrong Name"
  3. Rename again to right one, but too fast : E.G. "Right Name". Receive response: "Wait 5 seconds until you can rename again"
  4. Try to rename to the right name again after the 5 seconds have passed : "Right Name".
  5. Receive no error message but it doesn't change to "Right Name" and character is still called "'Wrong Name".
  6. Start campaign.
  7. Have two people look at that person's character sheet and determine if the names match with name shown in party list. They don't. one place is "Right Name" the other is "Wrong Name"
  8. Exit to lobby and crash.

Bug prevalence

Happens every time I play

Version

v1.0.8.0

-

No response

Which operating system did you encounter this bug on?

Windows

Relevant error messages and crash reports

Sorry I can't remember the error message.
Maximegede commented 1 year ago

I forgot to add. You can also see 2 different traits depending who is looking.

kumilanka commented 2 months ago

Trying to replicate this with 3 clients running on local server: able to change name once, all clients update. Attempt to change name again, tells me to wait 25 sec, probably 30 second cooldown. Changing name many times results in message for cooldown. After cooldown, changing name works as normal.

Had one client crash when max players was set to 2, then changed to 3 and attempt to join client3. Trying to connect again worked as normal.

QA should investigate if we can get repro steps for this to work more reliably.