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
Mods (complete and add to the following information):
Arma 3:1.98 stable
CBA:3.15.1 stable
Any mod that requires another mod
Description:
When BUILD of a required mod is a string and requirement specifies only MAJOR.MINOR.PATCH (without BUILD), versioning will fail and see required BUILD as too low.
Without BUILD or number BUILD, it works fine.
Steps to reproduce:
Set BUILD of a mod to some string, eg. 3.15.1.something
Require that mod by just MAJOR.MINOR.PATCH, eg. CBA[] = {"cba_main", [3,15,1], "(true)"} (in CfgSettings)
Observe warning of "mod requires req_mod at version [...]"
Expected behavior:
Ignore comparison of that version part if it's not a comparable number. Build is not necessarily a number.
Where did the issue occur?
Load a mission or main menu mission.
Log Files:
Example: 21:31:04 WARNING: mymod requires acre_main (@ACRE) at version [2,7,3] (or higher). You have: [2,7,3,"1024-tac1"] where ACRE's build number is 1024-tac1.
Additional context:
Not a result of versioning changes in one of the recent versions, but only VERSION_AR which was around for a while. This might have always been the case and might just not be supported by design. However, build numbers can be anything, same would happen with CBA's date as build number if you'd put dashes into the date.
Screenshots:
/
The text was updated successfully, but these errors were encountered:
Mods (complete and add to the following information):
1.98
stable3.15.1
stableDescription:
When BUILD of a required mod is a string and requirement specifies only MAJOR.MINOR.PATCH (without BUILD), versioning will fail and see required BUILD as too low.
Without BUILD or number BUILD, it works fine.
Steps to reproduce:
3.15.1.something
CBA[] = {"cba_main", [3,15,1], "(true)"}
(inCfgSettings
)Expected behavior:
Ignore comparison of that version part if it's not a comparable number. Build is not necessarily a number.
Where did the issue occur?
Log Files:
Example:
21:31:04 WARNING: mymod requires acre_main (@ACRE) at version [2,7,3] (or higher). You have: [2,7,3,"1024-tac1"]
where ACRE's build number is1024-tac1
.Additional context:
Not a result of versioning changes in one of the recent versions, but only
VERSION_AR
which was around for a while. This might have always been the case and might just not be supported by design. However, build numbers can be anything, same would happen with CBA's date as build number if you'd put dashes into the date.Screenshots:
/
The text was updated successfully, but these errors were encountered: