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
When a specific map version doesn't have a config it looks for an other version of the map that does have a config, however it just picks the first one that matches. This can lead to a very outdated config being picked.
For example, when loading koth_bagel_rc6 it picks the config for koth_bagel_rc2 while koth_bagel_rc5 is available.
Ideally it some logic should be added to attempt and pick the closest/most recent version.
The text was updated successfully, but these errors were encountered:
I like the idea behind this but I'm not sure how to quantify "the most recent version"
For the closest match one could go ahead and use something like the levenshtein distance to get the closest match, but that could be somewhat unpredictable.
The only idea I have right now for the most recent version would be to sort the versions by name and use the "biggest" one.
This would work quite well for maps following the _a,_b,_rc naming scheme but could fail for other ones.
If there's any other ideas on how to achieve this let me know I would be willing to implement this.
Sorting by name wouldn't work for everything yes, but I think it should handle most cases properly and for the ones where the naming scheme doesn't sort properly it shouldn't make much of a difference compared to the current "random" pick.
When a specific map version doesn't have a config it looks for an other version of the map that does have a config, however it just picks the first one that matches. This can lead to a very outdated config being picked.
For example, when loading
koth_bagel_rc6
it picks the config forkoth_bagel_rc2
whilekoth_bagel_rc5
is available.Ideally it some logic should be added to attempt and pick the closest/most recent version.
The text was updated successfully, but these errors were encountered: