Skip to content

When creating custom matches, the first environment being played is wrong #3

@carelfransen

Description

@carelfransen

When creating custom matches with match.configs.custom.xml, you can determine the order of environments in the match like this (for example):

<number_of_maps>4</number_of_maps>
<map>stadium</map>
<map>speed</map>
<map>island</map>
<map>rally</map>

However, for some reason, the match will always start with another environment than the first listed (often the second). I believe this mostly happens when the played maps are not yet loaded on the server (but are loaded on starting the match), but I haven't pinned down exactly when what happens yet.

Another thing that might be linked to this, is when starting a match on not-yet loaded maps, FAST will say:
<login> (admin) started <match title> match ! (1 maps)
Regardless of how many maps will be played or how many are in the matchsettings file, FAST will always say the match will be played on (1 maps). After the maps are loaded, there are no problems, it's just a visual bug, but maybe it's somehow connected to the problem above.

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