Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Get5 match config - map_sides #101

Open
lanslide-team opened this issue Feb 23, 2024 · 1 comment
Open

[BUG] Get5 match config - map_sides #101

lanslide-team opened this issue Feb 23, 2024 · 1 comment

Comments

@lanslide-team
Copy link
Contributor

For the match config (Get5), there's a parameter called map_sides. MatchZy is requiring the length of this array to be >= the number of maps (num_maps). However, according to the get5 documentation (see below), if this parameter is less than the number of maps, it should use side_type to determine the behavior for the remaining maps. Therefore, MatchZy should permit an array size less than the number of maps, if side_type is defined.

map_sides: Determines the starting sides for each map. If this array is shorter than num_maps, side_type will determine the side-behavior of the remaining maps.
Source: https://splewis.github.io/get5/latest/match_schema/

Here's an example (partial) config:

"num_maps": 3,
"side_type": "standard"
"map_sides": {
"knife"
}

@lanslide-team
Copy link
Contributor Author

With further testing, the workaround is to exclude map_sides in the match config and ensure matchzy_knife_enabled_default is enabled.

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

No branches or pull requests

1 participant