We know a lot of our users are relatively new to Linux, so we made sure that in the new GetAMP installer for AMP 3 - the first time you hit CTRL+C while trying to copy the URL to finish setup, it doesn't kill the script - the copy happens instead. Even if you do accidentally kill it, the URL is left in the terminal afterwards :)
We're just 10 days and 10 hours away from the premiere and the first stage of the AMP 3 Beta! We've updated the announcement with information on eligibility and what you can expect from the beta: https://t.co/WSX6KBd0iD
Headline details for those who want to try out the beta to be eligible for the Batch 0 keys:
You need to have owned AMP Advanced or Enterprise before the 1st of July this year (inclusive of that date)
Your Discord account needs to be linked so your exclusive role can be assigned.
Your email preferences in your account needs to have "Product Notifications" turned on so we can actually send you the invitation.
Batch 0 will be a pool of 250 keys - but if the live premiere exceeds 1000 views during the premiere itself, we're going to double that to 500 keys. So make sure you're there for it and register your interest in the event just above so you get notified!
We've spent the last week testing and doing validation on a variety of systems and setups, checking things like automatic updates, rollback handling, compatibility and general behaviour. We gained access to Mythos to do a (very expensive!) security sweep of the entire stack. Windows users in particular benefit from this because we've got some most excellent functionality come out of that to provide isolation in the absence of containers.
Getting AMP 3 built and into the state where it's ready to show off has been an absolutely labour of love over these last few years - but it's going to be worth it. As for Batch 1 onwards, the speed of that basically depends on what kind of issues come up during the beta. If everything goes as planned we'll be expanding the number of beta slots fairly quickly.
See you all November 6th! <3
The phrase "contact your administrator" occurs exactly once ever in AMP 3, where you have an invitation whose roles originally assigned to it no longer exist and the administrator needs to re-issue the invite.
One of the rules in AMP 3s development is that *every* failure condition must have some kind of human readable explanation - no generic "Something went wrong" situations. It's a lot of work authoring messages for every condition but it means that dealing with issues when they do come up will be a lot easier with only a single message per cause.
We've recently updated our AI disclosure for AMP 3 development to include the use of Mythos for security testing.
You don't need us to tell you it has been a bloodbath this week with LLMs discovering or producing PoCs for all kinds of exploits, and AMP of course is installed on a large number of fairly powerful systems which makes it a really attractive target. So we're using the same kind of tooling to make sure not just AMP but the game servers running inside it don't become a vector.
We're committed to aggressive proactive testing before builds reach users to help keep you guys safe, rather than reacting to things after they happen.
On container-less systems, AMP 3 still isolates each game server process within its own user. So even if one was compromised, it wouldn't be able to affect anything else on the system. This applies on both Windows and Linux hosts.
We don't use PHP for any products we ship or systems we use. If you're using any legacy panels that still rely on PHP then AMP 3 is about to offer you an excellent upgrade path soon :)
Anything that can create standard Docker contains on your system has the equivalent of root access to your entire system and everything in it. This is part of why AMP uses either rootless Docker or Podman (which is always rootless)
If you're still using a panel that creates normal containers, AMP 3 has the ability to import from a variety of other server panels so you can level up your security.
P.s. It's also a good reason to make sure you're not using something vibe-coded that has de-facto root access to your system whose developer doesn't understand how it works ;)
One of the things we will never do is shoehorn unwanted AI features into our software just for the sake of it or push it onto users who don't want it.
If we ever do find a use for AI that actually adds value in some way to our software, it will be disabled by default, explicitly opt-in, and you will never be pestered or annoyed into turning it on.
If a feature can be implemented *without* using AI to do it, that will remain the preferred approach.
Apologies all, there was a minor issue with the new referrals system that meant some referrals weren't being counted. Anyone you referred can credit you retroactively by going to their account at https://t.co/Npxulfc5vj and giving it your link again so you get credit for it.
We've made a change to how CubeCoders accounts work that you may wish to review. We've introduced a new set of flags to let you control when you want to hear from us via email.
The defaults are as shown here - so transactional emails, security notifications and rewards/bonuses issued to your account. Sales and Offers and Product Notifications are disabled by default. If you'd like to change when you hear from us, you can change this at https://t.co/7Xd2s10C12
Psst: Turn that last one on if you want to be amongst the first hear about AMP 3!
One of the best overall design changes in AMP 3 is removing redundancies and duplications. Need to open a support ticket? You do that in *one* place regardless of whether it's with the system itself or a specific app. Permissions? All in one place, you don't need to go in to each apps own settings. Analytics? Same again - one big shared system that lets you filter by the app rather than requiring that you go to each one individually. Similarly there is *one* SFTP for each machine rather than needing one for each individual app. It addresses one of the biggest sets of issues with AMP 2 that made features harder to find than necessary.