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
- CBA_A3
- ace
- https://steamcommunity.com/sharedfiles/filedetails/?id=1373175187
- 3cb Weapons ACE compat, VPHUD, dzn Vehicle on Fire, ACE Interaction Menu Expansion, some NIArms compat mods
Description:
CBA 3.10 release on Steam happened ~15 minutes before our scheduled mission start. The server is running essentially 24/7 and needs to be manually kicked into grabbing mod updates from the SWS.
After loading in, those who got their clients updated got slapped by PBO Checking for having "CBA 3.1" which was claimed to be older than CBA 3.9; I checked CfgPatches in the config viewer pretty much immediately and it was showing version = "3.10.0.190314"; for all CBA classes that had a version defined.
Steps to reproduce:
Have CBA 3.10 loaded
Join a server running CBA 3.9 and PBO Checking
Observe the chat message dropping the zero in the version number and saying the newer version is older
Where did the issue occur?
Dedicated
Additional information:
For us, this time, it was only a display issue. But if the system ever has to compare x.1.x to x.10.x, it might end up calling them identical.
Arma 3 Version:
1.90.145381
(stable / rc / dev)CBA Version:
3.10.0.190314 (client) / 3.9.1.181229 (server)
ACE3 Version:
3.12.5
Mods:
Description:
CBA 3.10 release on Steam happened ~15 minutes before our scheduled mission start. The server is running essentially 24/7 and needs to be manually kicked into grabbing mod updates from the SWS.
After loading in, those who got their clients updated got slapped by PBO Checking for having "CBA 3.1" which was claimed to be older than CBA 3.9; I checked CfgPatches in the config viewer pretty much immediately and it was showing
version = "3.10.0.190314";
for all CBA classes that had a version defined.Steps to reproduce:
Where did the issue occur?
Additional information:
x.1.x
tox.10.x
, it might end up calling them identical.RPT log file:
The text was updated successfully, but these errors were encountered: