Aloft's final Early Access content update lands on 26 August, and if you're the person running the server for your group, that date means something different to you than it does to everyone else. They get a new world to poke at. You get to decide whether the world you've all spent months building on comes through the other side intact, and whether you find that out on your own terms or at nine o'clock on a Wednesday evening with six people waiting. Astrolabe Interactive announced Discovery & Ancestry on 13 August, and it's a much bigger swing than the name suggests, because there's an engine change buried in it. If you need somewhere to put it, we host Aloft servers.
Here's what's confirmed, what genuinely isn't, and what I'd do this week if it were my server.
What's actually in it
Astrolabe's announcement is unusually specific, so I'm sticking to their list rather than the paraphrases going round:
- The Wind Spirit, a new companion you find and befriend, built around riding the winds to sail further out across the islands than you can today.
- Ancestral Memories, a system that connects you to your ancient predecessors and hands you skills and character upgrades for the trouble, the closest thing Aloft has had to a real character-progression tree.
- A revamped sandbox world, with reworked UI and changes to progression and route-finding that Astrolabe frames as giving you more freedom to pick your own path.
- New sub-biomes: lush jungles, snowy regions, prairie fields and dense woods.
- Dynamic cluster events. Fog banks, tornadoes, debris fields.
- The Spyglass and Table-Map both get reworked, aimed at surveying and getting your bearings.
- New building pieces and stockpiles, including a Water Well and a Dew Catcher. Astrolabe's own description of those two is "highly-requested", which is the studio conceding a point rather than making one.
Taken together that's a proper content drop, and by Astrolabe's own count it's the fifth major update since Aloft went into Early Access in January 2025. But the line I keep coming back to isn't in the feature list at all.
The Unity 6 swap is the real story
Astrolabe are moving Aloft from Unity 2021 to Unity 6 in this update, and they've said plainly it's for performance and visuals on the road to 1.0.
For someone playing the game, that's a footnote. For anyone running a dedicated server it's the single most consequential line on the page, because the Aloft dedicated server isn't a separate product with its own build pipeline: it's the game executable launched headless, with -batchmode -nographics -server in front of it. Change the engine under the game and you've changed the engine under the server too, all at once, on the same morning.
I've watched this play out before. When Conan Exiles jumped from UE4 to UE5 back in May, the mod catalogue broke overnight and admins spent a fortnight working out what still loaded. Aloft has no mods, so that particular flavour of pain isn't coming for you. What an engine jump does reliably shift is memory behaviour, startup time and the shape of whatever lands in the log when something goes wrong. Plan for your server to feel a bit unfamiliar for a week and you won't be caught out.
And the honest caveat: I have no numbers for any of that. Astrolabe haven't published a before-and-after on server memory, and I'm not going to invent one to fill the gap. Watch your own graphs after the 26th rather than trusting anybody's estimate, mine included.
About that word "final"
"Final Early Access update" is doing a lot of work in the headlines, so it's worth being precise about what Astrolabe actually committed to.
They said Discovery & Ancestry is their final content update during Early Access, and that once it lands the team turns its full attention to the 1.0 launch. That's it. That's the whole commitment.
What they didn't say, anywhere, is when 1.0 arrives: no date, no window, not even a season. So anyone telling you Aloft 1.0 is coming in a particular month is guessing, and given that "this summer" back in June resolved to a late-August date, I'd treat the confident guesses as noise rather than information. Worth separating out the other thing "final" doesn't mean: patches and fixes are not content updates, and nothing in the announcement rules those out. Expect plenty.
The save question, and why I'd back up anyway
Nobody has said Discovery & Ancestry wipes worlds. I want to be completely clear about that, because "final update, world reset incoming" is exactly the kind of thing that spreads through a Discord in an afternoon and it isn't currently supported by anything Astrolabe have published.
What is on the record is precedent. In their one-year devlog back in January, Astrolabe described the Bloom & Blight update as having come with "a necessary reset due to file data changes and a new more robust save system". So this team has shipped a major update that required a reset before, and, to their credit, said so plainly when they did. Discovery & Ancestry revamps the sandbox world and reworks progression on top of an engine migration, which is an awful lot of moving parts touching saved data on the same day.
No announced wipe, then, but real precedent for one and a whole new engine underneath. Take the backup. Cloud Backup in the panel will do it, and I'd take a manual one on the 25th rather than trusting whatever the schedule happened to catch. We wrote about what actually saves you when a world goes wrong, and the short version is that the backup you took deliberately, the day before the risky thing, is the one that turns out to work.
If you'd rather choose your own moment than have the new build land on you at whatever hour Astrolabe press the button, open a ticket before the 26th and ask us to hold your server where it is. Let the first wave find the problems, read a few hours of feedback, then go.
Running one with us
Aloft servers here live in the LOW.MS Control Panel, and there's one thing about this game you want to know before you go looking for settings, because otherwise you'll spend twenty minutes hunting for a screen that doesn't exist.
Aloft has no server config file. None: no .ini to edit, nothing to fill in, so Configuration Files sits empty for Aloft and always will. Every single thing the server does is set on the command line, in the slightly odd hash-delimited syntax Astrolabe's own PowerShell launch scripts use:
-batchmode -nographics -server load#MyWorld# servername#SkySailors# log#ERROR# isvisible#true# privateislands#false# playercount#8# serverport#27500# admin#76561198000000000#
isvisible decides whether you show up in the lobby or run code-only, privateislands does what it says on the tin, and admin takes a SteamID64. You repeat the whole parameter once per admin rather than comma-separating them, which catches people out.
Two other things bite. The first is spaces, and the advice here is less settled than most guides make out. The community wiki marks both the world name and the server name as no-spaces fields. I'd take that seriously for the world name, because that string is how the server finds your save. The server name I'm genuinely unsure about: our own default ships as "Aloft Server", space and all, and those hash delimiters around each value look like they exist precisely so a value can contain one. So if a server refuses to load and the only odd thing in the line is a space, strip it and try again. Just don't rebuild your whole naming scheme around a rule nobody has confirmed.
The second is simply that a command line is not a config file. Changing anything means a service restart, and today it means a ticket rather than a field you can edit yourself: the command line isn't exposed on Aloft services, so setting admins or flipping isvisible is something you ask us for. That's a two-minute job at our end, but it's worth knowing before you go looking for the box.
Two files are worth knowing about once the server is running, and both are Astrolabe's doing rather than ours. output.log is the server log, and it gets overwritten every time the server boots, so take a copy before you bounce the service if you're chasing something. ServerRoomCode.txt holds the join code, which the server regenerates on each start. Cloud Backup sits in the sidebar the way it does on every service we run, and it's the one I'd actually use.
Beyond that, Aloft is new enough on our side that I'd rather not promise you a specific row of buttons. If something you'd expect isn't in your sidebar, a console or a file browser or a scheduler, open a ticket and we'll either switch it on for you or just do the thing. There's no Mod Manager story either way, because Aloft doesn't support mods and has no Workshop content behind it. The server listens on port 27500/UDP by default, and for file transfers SFTP is on 8822 and FTP on 8821.
A few things I'd do before Wednesday
Take the manual backup, and then actually check it's there instead of assuming. Get the update timing sorted with us so it happens when you're awake. Write down your world name exactly as it appears, character for character, because if you ever need us to rebuild that command line then the string is the whole difference between loading your world and quietly generating an empty one alongside it. That's the mistake I'd most expect to see in tickets this week. And tell your group that the first evening after a major update is not the evening to attempt anything they'd be sad to lose.
If your server comes up strange on the 26th, or doesn't come up at all, open a ticket and paste in the last chunk of output.log if you can get at it. Support runs around the clock, so it doesn't matter what time it goes sideways.