Page MenuHomeFeedback Tracker

patch 1.22 problem
Closed, ResolvedPublic

Description

After the release of the patch, the queue of players stopped working, they either get into the download immediately or they get an error

[Login]: Adding player emtri2 (30782876) to login queue at position 0
Player Unknown (30782876) kicked from server: 96 (An unknown error has occurred.)
[Login]: Remove 30782876 from login queue (index 0)

Details

Severity
Major
Resolution
Open
Reproducibility
Always
Operating System
Windows 10
Category
General

Event Timeline

For some reason, if you put the value
loginQueueConcurrentPlayers=5;
more than 5, the server cannot start due to the fact that at startup the server fps will fall below one in the first seconds

Geez changed the task status from New to Awaiting internal Testing.Sep 7 2023, 11:37 AM
Nolhek added a subscriber: Nolhek.Sep 7 2023, 5:01 PM

Maybe related to T175043?, that being from client perspective and this one from server perpective? @Norealname, do you know what error code shows to the player. Is it error 0x00040031?

Norealname added a comment.EditedSep 7 2023, 5:59 PM

Maybe related to T175043?, that being from client perspective and this one from server perpective? @Norealname, do you know what error code shows to the player. Is it error 0x00040031?

This is another 0x00040060
No player can queue, so I think it's a server side issue

@Geez
verifySignatures = 0;
breaks the queue, tested on a completely vanilla server

Geez changed the task status from Awaiting internal Testing to Confirmed Internally.Sep 13 2023, 10:03 AM
Geez added a comment.Sep 13 2023, 10:14 AM

For some reason, if you put the value
loginQueueConcurrentPlayers=5;
more than 5, the server cannot start due to the fact that at startup the server fps will fall below one in the first seconds

Hello Norealname.
There needs to be some reasonable number in this parameter. Putting more than 5 will definitely affect performance negatively.

Geez added a comment.Sep 13 2023, 10:15 AM

@Geez
verifySignatures = 0;
breaks the queue, tested on a completely vanilla server

Also we are aware of this issue and it is scheduled for a fix. However putting zero is not recommended by us generally as this allows people with outdated mods/mods not installed on the server/without mods to connect to the server. which can cause issues.

@Geez
verifySignatures = 0;
breaks the queue, tested on a completely vanilla server

Also we are aware of this issue and it is scheduled for a fix. However putting zero is not recommended by us generally as this allows people with outdated mods/mods not installed on the server/without mods to connect to the server. which can cause issues.

This also allows you not to worry that any mod will stop the server after updating.

Geez closed this task as Resolved.Nov 27 2023, 10:29 AM
Geez claimed this task.

Resolved for 1.24 update.