Update log
Full First Class Trouble update
The complete published notes, normalized for clean reading and source attribution.
Repeated intro
Hello fellow passengers, it is nearing that time when we are commencing the big retrofit of First Class Trouble! This post will detail what is to come. It will contain both a little rundown on what this update is, why it is what it is, and explain how we will be rolling out the first update here on January 29th. which will be a technical update and the coming content updates.
Extracted changes
- Gameplay
- Workshop
- Performance
In the bottom you will find a few select patch notes, as honestly we changed so much it would be an impossible task to list them all.
If we’ve done our jobs correctly, this update will feel a little bit like boarding the ISS Alithea and finding that everything looks exactly as you remember it.
The carpets are still plush-ish. The drinks are still chilled-ish. And the trouble… well, that’s still very much first class-ish - nevermind the blood ;).
But beneath the polished exterior, almost everything has changed a board the ship and game.
Over the past months, we’ve been working on one of the largest and most technically ambitious updates in the history of First Class Trouble.
It's not a content update. It is not a flashy update, but a foundational update - the kind you only ever do if you care deeply about a game’s future.
Or, put more bluntly: the kind of update you do to make sure the ship doesn’t quietly drift into the void.
This update represents the first major step in giving First Class Trouble new life - or at the very least, ensuring it stays alive and well for years to come.
Behind the scenes, we have:
Migrated the entire backend services and match making solutions
Moved all player accounts safely to the new system
Upgraded the game engine from Unreal Engine 4.24 to Unreal Engine 5.4
So much more that we can't even remember
This has required months of engineering work, extensive testing and more late-night debugging sessions than we care to admit. At times, it felt like pulling the ship apart mid-voyage and reassembling it without letting the passengers notice.
This is a huge update - just not a loud one that you necessarily will hear- if we do it right.
And that’s very much by design.
We are upgrading to Unreal Engine 5, not because it is shinier and newer, but for us to develop more content for you and also because that many of the tools and back-end services that the game run on is no longer supported so they won't work anymore.
Not here. Yet!
This update is about stability, longevity, and future-proofing. It lays the groundwork for what comes next. New features, content, and improvements are planned, but we couldn’t responsibly build those without first making sure the foundation was solid - quite frankly if we didn't do this the game would close down very soon for everyone; and we don't want that.
Because this is such a deep technical overhaul, there may be stability issues we haven’t caught yet. That’s also why we’re rolling this out in stages rather than flipping every switch at once. If something feels off, strange, or unexpectedly broken, please let us know; especially on Discord. Your reports genuinely help more than you might think.
To safely execute the migration, First Class Trouble will be offline for maintenance on:
Thursday, January 29th 05:00 CET - 11:00 CET
During this time, the game will be unavailable
Source