Skip to content

Deprecate console commands in DesiredGameState and allow match managers to bypass state setting - #177

Merged
NicEastvillage merged 3 commits into
masterfrom
cmds
Aug 15, 2026
Merged

Deprecate console commands in DesiredGameState and allow match managers to bypass state setting#177
NicEastvillage merged 3 commits into
masterfrom
cmds

Conversation

@NicEastvillage

Copy link
Copy Markdown
Contributor

Uses changes in RLBot/flatbuffers-schema#63

Resolves #176


case InterfaceMessage.DesiredGameState:
if (!_stateSettingIsEnabled)
if (!_stateSettingIsEnabled && _agentId != "")

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Always allowing console commands is one thing, but always allowing state setting when it's supposed to be off is something else imo. I thought the point of splitting off console commands was to allow them to be used by match managers even when state setting is disabled, without letting them do state setting?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Imo match managers are allowed to do anything. It's their match.

The splitting was just to clean up the API.

@VirxEC

VirxEC commented Aug 12, 2026

Copy link
Copy Markdown
Collaborator

other than that, LGTM

@NicEastvillage
NicEastvillage merged commit 8b6c5c4 into master Aug 15, 2026
3 checks passed
@NicEastvillage
NicEastvillage deleted the cmds branch August 15, 2026 07:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

Allow console commands for match manager even when state setting if off

2 participants