AMP 2.6.4 ‘Phobos’
This is primarly a QoL update with user interface and behavioural refinements.
New Features
“Dirty” Backups
Available for games where AMP is able to track when users join the server, AMP can now be smarter about how backups are taken. If a scheduled backup is set to “Dirty Only” - then it will only take a new backup if the server is either currently populated, or if someone has joined the server since the last backup was taken.
This means that if you were to schedule hourly backups with this turned on, it wouldn’t create a series of identical backups because nobody has joined the game to change anything.
Interface Updates
The scheduler UI has been updated to match the rest of AMPs design to make it tidier and more obvious what you’re doing when adding/editing tasks.
Additionally, like lists - settings that have key/value pairs can now have their existing values edited in-place without having to delete and re-add values to change things.
Sub Users!
A long requested feature has finally been implemented. You may now create a user with a specific set of permissions or roles, and that user can add another sub-user that has equal or less permissions. This does require that the user is able to create and edit users, of course.
Changes
- If a backup is not taken because a policy prevents it, the error message shown in the scheduler or when creating one manually more clearly explains that it’s specifically because of the policy, and what should be changed.
- The ‘Take a sticky backup’ task has been deprecated, since the “Take a backup” task has been updated to have Sticky as a flag.
- The WebHook API endpoint has a special exemption that means that the requesting party isn’t required to specifically accept application/json and can accept / instead.
- OIDC - The username claim can now be customised. The user info is now tracked by the unique “sub” of the user in the OIDC provider. Be sure users all sign in one time after this change before switching to a different claim or their permissions could be lost (Does not apply to new OIDC setups).
- Added a new schedulable task for server info publishing, for example games that expose a Server ID to connect to - this can now be intercepted to use elsewhere, for example pushing to a Discord message .
Bug Fixes
- Fixed the file manager trying to navigate to paths that don’t exist if you click too fast on directories between refreshes (or accidentally double-click)
- Fixed not being able to use forward slashes in branch names for Git repos for app configuration stores.
- Fixed side menu not loading properly in some cases for users with reduced permission sets.
- Fixed application IP binding being reset when updating Generic instances.
- Fixed not being able to deploy templates from API users with reduced permission sets.
- Fixed not being able to set container mount bindings.
- Fixed an issue where long-running tasks that fail might show an empty reason for the failure to the user.
- Fixed a potential crash in the Minecraft module when trying to write data to its console while the server is in the pre-start state.
- Fixed users not being able to properly set up and assign permissions for sub users due to an incorrect calculation of the users current permissions which made it deny everything.
- Addressed users being able to see buttons they don’t have access to use on the Instances tab in ADS. They were unable to use the buttons, but they were visible which caused confusion.
- OIDC users were not getting assigned user specific permissions properly (permissions not assigned through a role).