Table of Contents
Settings for dedicated server features may be adjusted in the ..\ArmA2\userconfig\ACE\ACE_serverconfig.hpp file.
Also see Running an ACE Server
Lock out players with missing PBO's
To check if certain pbo's are missing on client and prevent client from playing if they are missing.
check_pbos = 1;
Check All ACE PBOs
To verify that all pbos shipped with ACE are running on client.
check_all_ace_pbos = 1;
Checklist
If check_all_ace_pbos is enabled, the following pbos are added to the checklist. If not, only these pbos are checked.
checklist[] = {"ace_addon1","ace_addon2"};
Exclude PBOs
If all ace_pbos_check is enabled, exclude the following files from check.
exclude_pbos[] = {};
Allowing different versions of ACE to connect
Not recommended for "production" servers.
- Find the file ACE_serverconfig.hpp in the subfolder userconfig of your ArmA2 game folder ( e.g. c:\Program Files\Bohemia Interactive\ArmA2 ).
- Optionally make a backup copy for just-in-case situations.
- Open that file with a text editor, notepad works fine.
- Locate the section on VERSIONING_LEVEL
- Uncomment or add a non-commented line setting the amount of checking you desire.
- -1 - Exact match. Default setting.
- 0 - Disable all checking.
- 1 - Check 1st level. 1.0.v, 1.1.v are allowed, 0.u.v.w.x.y rejected.
- 2 - Check 2nd level. 1.1.1.w, 1.1.2.w are allowed. 1.2.v.w.x.y rejected.
- 3 - Check 3rd level. 1.1.1.1.x, 1.1.1.2.x are allowed. 1.1.2.w.x.y rejected.
- 4 - Check 4th level. 1.1.1.1.1.y, 1.1.1.1.2.y are allowed. 1.1.1.2.x.y rejected.
- The final result should look like this....
// Uncomment and set to the level of version checking you prefer. -1 means all pieces. 0 means disabled. 1 means only major. 2 means major and minor... etc. // #define VERSIONING_LEVEL -1 #define VERSIONING_LEVEL 3
- Save that file
- Close the profile file and restart the server.