You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the wrong name is recorded in the database for the first map. The first map should be the one on which BAN/PICK was performed. As a visual example, before loading the match configuration I set the maps to ar_pool_day / ar_baggage / ar_sheets (see screenshot).
However, the first map — which should correspond to the map chosen during BAN/PICK — is recorded incorrectly; instead, the name returned by Server.MapName is used.
To fix the bug with determining the first map’s name, the method of obtaining the map name during match initialization must be changed. Currently, in the InitMatch method (in the file DatabaseStats.cs) the following line is used: string mapName = Server.MapName;
I propose to replace it with obtaining the map name from the selected map pool stored in the MatchConfig object, i.e.: string mapName = matchConfig.Maplist[mapNumber];
Below is a fragment of the corrected InitMatch method:
This change ensures that the map name recorded in the database corresponds to the map chosen during the BAN/PICK process rather than the name returned by Server.MapName.
The text was updated successfully, but these errors were encountered:
I’ve been working on a few improvements and bug fixes for MatchZy. If you don’t mind, could you please invite me as a collaborator so I can create pull requests directly? This would help streamline the contribution process.
Currently, the wrong name is recorded in the database for the first map. The first map should be the one on which BAN/PICK was performed. As a visual example, before loading the match configuration I set the maps to ar_pool_day / ar_baggage / ar_sheets (see screenshot).
However, the first map — which should correspond to the map chosen during BAN/PICK — is recorded incorrectly; instead, the name returned by Server.MapName is used.
To fix the bug with determining the first map’s name, the method of obtaining the map name during match initialization must be changed. Currently, in the InitMatch method (in the file DatabaseStats.cs) the following line is used:
string mapName = Server.MapName;
I propose to replace it with obtaining the map name from the selected map pool stored in the
MatchConfig
object, i.e.:string mapName = matchConfig.Maplist[mapNumber];
Below is a fragment of the corrected
InitMatch
method:Also, in the file Utility.cs (starting around line 769) a correction must be made in the call to
InitMatch
so that theMatchConfig
object is passed:This change ensures that the map name recorded in the database corresponds to the map chosen during the BAN/PICK process rather than the name returned by
Server.MapName
.The text was updated successfully, but these errors were encountered: