OMG It’s AMP 3!
Hey everyone! We have an important announcement regarding AMP!
You might have seen the rumours, or you might have seen some of us talking about it - but AMP 3 is very much in development. And it is awesome.
No, it’s not available yet. We don’t know when it will be. Do not ask.
If you want to be among the first to try the private AMP 3 beta in the future, you must already own a copy of AMP Advanced Edition before July 1st! Now is the time to upgrade!
Ownership is not a guarantee that you will be invited immediately, but is a requirement. Invitations will go out in stages. There is no sign up or registration until we’re ready to release.
Mockery and punishment will be swift and brutal for anyone who asks a question already answered below.
Where AMP 2 was a direct succession of AMP 1, AMP 3 is a completely new codebase with a completely different design. Aside from the fact that it uses the same template source data, almost none of the implementations share anything in common.
AMP 3 fixes almost every major design issue, problem and frustration with AMP 2:
- Game servers can keep running and functioning while AMP is shut down for maintenance or for updates.
- Full localisation, AMP 3 will be available in English, French, German and Dutch at launch. You can switch languages on-the-fly too if you need to share something with us.
- Accessibility is massively improved, with a special high-contrast mode and full keyboard navigation.
- Permissions are fully centralized, you don’t need to hunt around in different parts of the interface.
- Far richer file manager with better selection, drag+drop, faster transfers, the works.
- Snapshot based backups that behave like a time machine, taking your entire server back to a point in time easily.
- Richer application list, you can type in “7d2d” and it knows exactly what you’re on about.
- A far better design for multiple servers, no more fragile hierarchical controller<->target setup.
- A full console history that goes back as far as you want. AMP can be stopped, started, new sessions, no matter what - everything is logged and you can go back as far as you like.
- The backend doesn’t rely on filesystem access to the individual instances, so separating where the game servers run from the control panel is going to be possible (and allows the control panel to easily run in a container which wasn’t practical before)
- No single point of failure. All of the key layers are redundant and support high-availability.
- It looks friggin’ sweet!
- Instances don’t rely on another running process to manage them, so there’s nothing to start/stop when configuring instances. The only thing that starts/stops/updates is the game itself. There is an intermediary agent layer but it doesn’t control anything so it doesn’t (normally) run when the game doesn’t.
Questions my magic orb predicted
Will I be able to use my AMP 2 licence?
Yes. AMP 2 licences will function in AMP 3 and behave in a similar way.
Will existing AMP 2 templates work?
Yes. AMP 3 will be able to use all existing AMP 2 templates so you’ll have the full application library straight away.
Will I be able to import my existing AMP 2 instances into 3?
Yes! It’ll be able to read in your existing instance data so you can keep your game configuration etc. What you won’t be able to import is things like your roles, users, etc because they work differently in AMP 3. But you will be able to keep your game instances and then re-assign users/roles/etc afterwards.
Is it going to…? How will X work?
It’s too early in development at this moment to answer questions about how any given peice of functionality will work. So hang tight on those questions for now.
When/how can I try it?
AMP 3 is going to be in a very tight invitation-only beta once we’re ready to show it off.
To qualify for an invitation when it’s ready, You must have already owned a copy of AMP Advanced or Enterprise edition since the 1st of July 2026 or earlier. The initial beta will only be available to experienced, long term AMP users.
When exactly this happens depends on when we can get enough working that it’s actually practical to use. We are not announcing any kind of dates at this time.
Why are you now working on AMP 3 after the AMP 2 Feature Freeze?
AMP 3 is such a big design change and departure from the concepts that AMP 2 uses that it’s actually going to take quite a long time to reach feature parity with AMP 2. So there will be a period of time where both projects are available and in-use in tandem.
The goal is to make sure that AMP 2 is gotten into the best possible state, as well as adding any features that will be necessary to facilitate the migration to AMP 3 - and then do the transition as gently as possible.
Show me the screenshots!
FINE! Here you go!
