AMP Beta 1.7 ‘Hawking Starman’ Release Notes

![AMP 1.7][1]

AMP 1.7 represents significant progress to some of the major milestones in AMPs roadmap. The 1.7 codebase will be focusing on permissions and management further as well as some of the features destined for the 1.8 milestones.

Important notes for users upgrading from AMP 1.6.x:

* Using fast file transfers requires that Webserver.EnableFetchPostEndpoints is set to True in AMPConfig.conf (you will need to add this line if it does not exist) as it is disabled by default in previous AMP versions. You can then enable Fast File Transfers in the configuration.
* Websockets are disabled by default on previous AMP installations, you may enable them by setting Webserver.EnableWebSockets=True in AMPConfig.conf
* If you are using ADS, you must also update all of your instances. There is no backwards/forwards compatibility between 1.7 and older versions when using ADS.
* You will almost certainly need to do a force refresh (CTRL+F5) or empty your browser cache when browsing AMP after updating.

General

* Across the board various AMP components are being converted to use async logic more where possible. This generally improves the responsiveness of AMP and improves maintainability of the code base.
* The ConsoleOutputRecieved event is now handled by AppServerBase (ModuleShared) rather than by individual modules.

AMPCore

* Link-local (169.254.*.*) IP addresses no longer show up in IP address lists.
* Added support for Websockets. Right now this is only used for the console but will be rolled out to other parts of AMP over time. This doesn’t work inside ADS when managing an instance but fallback is automatic.
* New ‘account’ page. The drop down menu in the top left for logging out has been removed. Clicking your user icon now shows you your profile where you can change your details.
* Changed appearance of modal dialogs to be easier to see and look better.
* Fixed “You do not have permission to use this method (WebMethods. GetAMPUserInfo) at this time.” errors when logging into an instance that uses ADS for authentication.
* Don’t consume activations when using ADS even if a key is supplied.
* Work in progress for 2FA (Google Authenticator) support. This is approximately 90% done.
* Rate limiting now applies to websocket upgrade requests and fast file transfers.
* Fixed an off-by-one error that caused January not to show up in the scheduler and triggers scheduled in December not to run (triggers will need re-adding).

Instance Manager CLI

* Now auto-restarts ADS during the first-time setup to smooth out installation.
* Fixed ampinstmgr ‘stalling’ for a long time when running any command due to it building an excessively long port mapping list.
* Added option to UpgradeAll to only upgrade instances that are on the Mainline release stream.
* Added a –skip-user-test flag to skip the test for a user mismatch.
* Added a warning that you’ll break everything if you try and rebind ADS.
* Now shows parameter types for commands when using Help.
* (Core) Fixed behaviour of sparse ranges so ports get handed out correctly.

File Manager Plugin

* Added support for fast file transfers. This bypasses the API for uploading/downloading files. **Note that when using this with ADS you must use ADSs file manager when uploading/downloading files. You won’t be able to do so while managing a specific instance via ADS** at this time.
* Fixed notifications being left behind if an archive operation fails.

Local File Backup Plugin

* No longer incorrectly shows a ‘Backup failed’ error when taking a backup that actually starts.

Minecraft Module

* Now specifies a larger heap size by default when using Buildtools.
* Fixed crash if file permissions cannot be resolved on Windows systems.

srcdsModule / SteamCMD Plugin

* Fixed an issue that could cause the module to crash if a user spammed the ‘Update’ button.
* Temporarily removed the map cycle tab as it’s not functional. It will likely return at a later date.

ADS Module

* Fixed instances randomly disconnecting while being managed.
* When managing remote instances, failed API calls will be automatically retried 10x before giving up.
* Improved IPv6 support. It’s now possible to correctly manage instances that are bound to IPv6 addresses.

[1]: https://c10.patreonusercontent.com/3/eyJ3IjoxMjQwfQ==/patreon-media/p/post/23459190/bf9daa7d84b04d1c9c77c988110f56c5/1?token-time=1546473600&token-hash=ssXx2FtorrEZ-S6k_6EsmXsTvZP3PekqjCKZidNgMY0=