Skip to content

Conversation

@Rainyan
Copy link
Collaborator

@Rainyan Rainyan commented Jul 10, 2025

Description

Revert MAX_PLAYERS from 101 to 33.

Undo maxplayers change from 2fdf6fb.
While the engine technically supports 100 players now, keep the maxplayers at parity.

Also update the main menu server slider to use the MAX_PLAYERS define for the upper bound.

Supersedes #1212

Toolchain

  • Windows MSVC VS2022

Linked Issues

Rainyan added 2 commits July 10, 2025 13:18
Since the x64 update 2fdf6fb, the engine's MAX_PLAYERS limit (for x64)
has increased from 33 to 101. Update the main menu's server creation
panel slider value to use this definition, instead of hardcoding 32 as
the upper bound.

We're using MAX_PLAYERS-1 because as per
https://github.com/NeotokyoRebuild/neo/blob/8f0fee0b0e4760af3851afb856815de9db2a9250/src/game/shared/shareddefs.h#L285-L287
the maximum gamerules allowed players should be <MAX_PLAYERS to make
room for the SourceTV/replay bot on the last allocated slot.
Undo maxplayers change from 2fdf6fb

While the engine technically supports 100 players now, keep the
maxplayers at parity.
@Rainyan Rainyan requested a review from a team July 10, 2025 11:19
@Rainyan Rainyan requested a review from a team July 10, 2025 11:36
@Rainyan Rainyan added the Gameplay Stuff that isn't gamemode or weapon specific, such as spectating, audio, configs. label Jul 10, 2025
@Rainyan Rainyan merged commit 23343df into NeotokyoRebuild:master Jul 10, 2025
7 checks passed
@Rainyan Rainyan deleted the bug/maxplayers-v2 branch July 10, 2025 18:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Gameplay Stuff that isn't gamemode or weapon specific, such as spectating, audio, configs.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants