Play test - Login Queue - (Unity module)
This play test assumes that you only have the Login with Device ID method activated. Note that this feature will work with every login method without additional work.
Login Queue
Ensure that the configuration in your Admin Portal matches the settings described on the Setup Login Queue page. This setup is required to force the login queue to trigger on every login attempt.
Play the game in the Unity Editor and click the login button. The Login Queue menu should appear shortly after the loading screen. Once the player reaches the front of the queue, the login process will continue, and the main menu will be displayed.
Cancel Login
To test cancel login, consider using an additional account logged in. With the minimum configuration value set, the backend still permits one player to log in. The Login Queue screen will appear for that player, although it might display only briefly and potentially not long enough to interact with the cancel button.
You can use Byte Wars other login method to log in as another player in the same machine, login with password. Open the project with this launch parameter:
-AUTH_TYPE=ACCELBYTE -AUTH_LOGIN=<email> -AUTH_PASSWORD=<password>
Play the game in the Unity Editor and click the login button. The Login Queue menu should appear shortly after the loading screen is displayed.
Click the Cancel button. A loading screen should appear, and the game will return to the login menu once the cancellation is complete.
With that, your Login Queue implementation is done!
At this point, you might want to change your configuration to the actual case you want the login queue to trigger. These are the default configuration if you want to set it back to their default value:
- Max Concurrency: 100000
- Max Login Rate per Second: 5000
- Safety Margin: 5
- Cool-downs: 600
- Queue Reconnect Grace Duration: 60
- Player Reconnect Grace Duration: 300
- Polling Time: 20