Skip to content

Feature Request: Option to disable mandatory whitelist/player-check when loading match JSON #372

@papa8855

Description

@papa8855

Hi MatchZy Team,

I am using MatchZy (v0.8.15) for my CS2 server, and I’ve encountered a significant limitation regarding the loadmatch functionality.

The Issue: Currently, when a match is loaded via matchzy_loadmatch or loadmatch_url, the plugin forces a whitelist check based on the players section in the JSON. If a player’s SteamID is not explicitly listed, they are immediately kicked with the message (NOT ALLOWED!).

Even if I set matchzy_whitelist_enabled_default false or matchzy_kick_invalid_players 0, the plugin seems to override these settings as soon as a match JSON is active. This makes it impossible to host "open matches" where we want to use the match automation (ready system, knife round, etc.) without manually collecting and inputting every single player's SteamID beforehand.

The Request: Could you please implement a toggle (e.g., matchzy_allow_open_matches or a specific Cvar within the JSON) that:

Removes the requirement for the players key to exist in the JSON.

Disables the automatic kicking of players not in the list when a match is loaded.

Allows any player to join any team without a specified SteamID.

Why this is needed: Many community servers host casual scrims or 10-man mixes where players change frequently. Manually updating the JSON for every substitution is extremely tedious and disrupts the flow of the game. We need the system to allow anyone to join and play once the match configuration is loaded, regardless of whether their SteamID is pre-registered in the file.

It would be great if the plugin could treat the players section as optional rather than mandatory for the whitelist.

Best regards, [papa8855 / CS2 Server Admin]

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions