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
Since modversions are ordered by number the modversions are all out of order. For example, in a list ordered from oldest to newest modversions, 4.2.19 comes before 4.2.2 (because 1 is smaller than 2, but 19 isn't smaller than 2). It should be the other way around, that's why I think modversions should be ordered by date and not by number.
Look, 1.2.12 is the latest version, though it's in the middle of the list. This makes it easy to make a dumb mistake when picking the correct modversion.
The text was updated successfully, but these errors were encountered:
@spannerman79 Yeah I have that issue too. Really really annoying. Seems like an easy fix if all builds were dated and sorted by that and not by number.
Only issue is the weird way that some mod devs number their build versions. Not to mention sometimes a modder (or two) just re-uploads the same version number when clearly there has been changes made. CustomNPC is one such mod 😦
It would be "nice" if mod devs followed some sort of correct versioning system. Hell even at the end (if they use Travis/Jenkis/etc) they can stick their build numbers on the end themselves if they wish.
Since modversions are ordered by number the modversions are all out of order. For example, in a list ordered from oldest to newest modversions, 4.2.19 comes before 4.2.2 (because 1 is smaller than 2, but 19 isn't smaller than 2). It should be the other way around, that's why I think modversions should be ordered by date and not by number.
Look, 1.2.12 is the latest version, though it's in the middle of the list. This makes it easy to make a dumb mistake when picking the correct modversion.
The text was updated successfully, but these errors were encountered: