AMP 18.104.22.168 is primarily a bugfix release to address issues caused by some underlying changes made as part of 22.214.171.124.
AMP 126.96.36.199 most notably fixes a major issue with the scheduler that prevents it working in the month of December, as well as a number of improvements to ADS, the scheduler and parts of the API.
Release 188.8.131.52 is a relatively large release with a number of bug fixes, and a focus on the Minecraft module, APIGEN tooling, and ADSs Server<->Server logic.
Discuss this release on the forums.
You must update the AMP instance manager for this release.
This minor release mostly consists of module/plugin specific bug fixes with relatively few changes to AMPCORE.
Tethys 184.108.40.206 introduces a number of fixes for VPS users, and has significant compatibility improvements with older versions of Linux, allowing AMP to run on Debian 7 and CentOS 6 without requiring a risky glibc upgrade.
AMP 220.127.116.11 contains a number of high-priority bugfixes to address common issues.
Tethys 18.104.22.168 includes a number of quality-of-life improvements and a number of bug fixes, as well as some new functionality.
This release includes some minor incremental changes and fixes to AMP itself, and features a new application module!
An update to the instance manager is largely optional, but is needed if you want to create ARMA3 instances.
Release 22.214.171.124 is a minor update to address some minor issues in the main Tethys release.
This update does not require an update to the instance manager.
This is a minor bugfix and refresh for MCMA2 based on some of the newer logic found in MCMA3/AMP with a focus on reducing resource usage.
- The scheduler logic from AMP has been backported to MCMA2, now only requiring a timer tick once per minute instead of very frequently, using less CPU time and fewer threads.
- The logic to find Java installations has been backported from AMPs Minecraft module.
- All referenced libraries have been upgraded to their latest version.
- The CPU/Memory usage is no longer polled, but rather only checked on-demand.
- Internal users (Admin and emc_server) are now stored in the UserInfo.txt file instead of in the config file. The values in the config file (and command line flags) can still be used to update values for Admin and emc_server. MD5 hashes can now only be used during first creation and cannot be used for subsequent updates of the user data, a valid Salt/Hash pair must be provided. Values specified in the config files are wiped after being applied. (Reverted)
- The 'SYSTEM' user has been removed. (Reverted)