Skip to content

[REVIEW #1913 FIRST] Determine auto-join by server's bot quota mode convar#1935

Closed
nullsystem wants to merge 3 commits intoNeotokyoRebuild:masterfrom
nullsystem:GH-1298_AutoJoin_BotQuotaDiff
Closed

[REVIEW #1913 FIRST] Determine auto-join by server's bot quota mode convar#1935
nullsystem wants to merge 3 commits intoNeotokyoRebuild:masterfrom
nullsystem:GH-1298_AutoJoin_BotQuotaDiff

Conversation

@nullsystem
Copy link
Copy Markdown
Collaborator

@nullsystem nullsystem commented Apr 8, 2026

REVIEW #1913 FIRST

Description

By default, server's kicks out bot due to fill behavior and so doesn't need to check bot count. However if the server's using normal or match, then the server returns relevant tags and the client will include bot count in auto-join player count decision.

Toolchain

  • Linux GCC Distro Native Arch/GCC 15

On entering a server, a ping-reply is now sent to the server to
get the most up to date players count upon entering. Auto-join
is determined if the server's full when trying to enter, and if
so enters an auto-join state where it'll refresh for 15s checking
count then entering when there's a free slot available. The
auto-join popup bar stays on any states.

* fixes NeotokyoRebuild#1298
Now with passworded server auto-join, it'll prompt first and
save the password rather than only prompting on joining in.
By default, server's kicks out bot due to fill behavior and so
doesn't need to check bot count. However if the server's using
normal or match, then the server returns relevant tags and the
client will include bot count in auto-join player count decision.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant