Advance notice of module replacement
In Mid-October 2025 - we are going to begin the process of removing certain legacy modules from AMP. These are standalone modules that have since been superseded by generic module configurations where the module offers no appreciable features or advantages that the Generic config doesn’t offer.
If you a relatively new AMP user (since mid-2024 onwards), then - other than in the case of FiveM and RedM - chances are you won’t be affected by this as the option to create instances based on these modules has been hidden for some time once they were flagged as deprecated.
In the case of FiveM and RedM, the modules are being deprecated now given they are being replaced by Generic module templates.
This change does not affect AMPs ability to run the games listed below, it’s purely about how AMP runs them.
AMP will warn you if you are affected. If you receive no warning from AMP itself, no action needs to be taken.
Affected instances will have a “Replace Instance” warning in their tile after the next AMP update:
Instances based on these modules will eventually stop working unless replaced with newer equivalents. And there may not be any warning when this happens as it will simply depend on how long those legacy modules survive the changes made to AMPs core over time.
The modules that will be affected are:
- ARK (Legacy)
- ARMA3 (Legacy)
- Factorio (Legacy)
- Terraria (Legacy)
- TheForest (Legacy)
- RedM/FiveM (Legacy)
- SevenDays (Legacy)
- SpaceEngineers (Legacy)
- SRCDS (Source/Valve games)
What will I need to do if I am affected?
You will need to create a brand new instance for the game in question, and then copy its data and any settings over manually.
Why are these being outright removed?
Removing these modules from AMPs main build reduces the testing and validation footprint, improves build times, and generally reduces the workload involved when we change parts of AMPs core as there will be fewer modules to maintain and update to match those changes.
This is also part of a push to improve the usefulness of the Generic module and reduce the number of specialised modules where there’s no special need or justification for it which helps keep development focused.
What if I have been using Greelan’s FiveM / RedM / txAdmin templates?
In this case, you can switch your instances so that going forward they use the templates that are being added at the same time to the main CubeCoders configuration repository. From now on, only the templates in the main repository will be maintained.
In a terminal/command prompt, as the user running AMP:
ampinstmgr stop ADS
ampinstmgr reconfigure INSTANCENAME +GenericModule.Meta.OriginalSource CubeCoders-AMPTemplates-main
ampinstmgr start ADS
Substitute INSTANCENAME for the name of your instance (not the friendly name).
Then update the instance from the main instances page in AMP (click on the down arrow on the instance tile).