About breaking saves

Hello ACEO world! It’s been a long time since I’ve posted. Can’t believe its been over 2 years since first started following this project ( weekly devblogs got me through a particularly terrible few months of studying!).

I know its been pretty quiet from the Dev side of things for the last few weeks, and know its going to pick up again once the new UI is in with some smaller improvements. I thought it would be interesting to start a chat about something which could happen in future development-breaking saves for a bigger update. This is something more and more studios try and avoid doing in development, where an update means you can’t use your old saves. I’ve been thinking however, if it might be something which could be a good thing in the long run. There are I’m sure things which devs would like to change and things which could potentially improve the game as well. I think baggage could be made more intuitive for example, (even silly things like adjusting stand size). It could also be a flash point for a really exciting update. Obviously, no one wants every update to break saves, but if there was enough warning, and a legacy version was kept available (like factorio), would this be something people would mind if it made the game better in the long run?

love to hear people’s thoughts!

2 Likes

So far the devs have tried to be backwards compatible,but have not shied away from making changes if they felt it necessary. :slight_smile: if worst comes to worst a small conversion utility could be created

1 Like

I would imagine that it is always good practice to try and keep saves from breaking and keeping your updates compatible with all things in the past.

However, just stating my opinion on the matter, I wouldn’t be grumpy at all if I was told that my saves will not be compatible with a new update. To me, if an update has much such massive changes that it simply can not relate to previous saves, then at that point, I am more excited about starting a brand new airport with all of the new features & updates that my old saves could not work with. It is part of playing games in Alpha. It happened to me a couple of times on SimAirport before ACEO was released. I enjoyed the experience of starting fresh with a boat load of new content, UI change, performance upgrades, etc.

That is just my two cents.

2 Likes

TL;DR: Our goal from a pure development perspective will always be to maintain the integrity of a save saved in a certain version, as far as it is reasonably possible. This will not change in the future, and right now I cannot see any case in which we will on a single version update brick all past Airport CEO saves (but I will not guarantee it since the game in fact is in an alpha state). Fun fact: Our main test airport which we still use today was first built around June 2017 (i.e. something like Alpha 0.16).

Long version because I’m waiting for a download to complete: Our goal from a pure development perspective will always be to maintain the integrity of a save saved in a certain version, as far as it is reasonably possible. To this date we have not had a single save that has not been compatible (launchable) with the few next versions, for example running an Alpha 25 save in an Alpha 27 game is not an issue, but the further apart the save’s last played version is compared to the version it is being launched in, the more likely it is that the save will launch without issues.

And the word “launchable” is of course important here. While we will always aim to keep the save launchable, there might be some strange behavior from one version to another which in that case always will be motivated by an underlying fundamental change to a certain system. When we implemented a new system for handling placeable objects in a generic way, for example the new furniture such as the small and large gate seating, the defaulted version of an already placed gate seating was the small gate seating. Since the small gate seating had different placement variables such as object size and grid snap, all gate seating in the game become small and incorrectly offset when launching an older save into the new system. Since the other systems in the game are generic enough, there was no issue for passengers to interact with the offset items and we deemed the changes’ impact to have enough significance for the future to be worth the weird offset “issue” (which of course was easily fixed by the CEO themselves).

There’s really two sides of the coin when going about the discussion of save integrity, on the one hand we do have CEOs who enjoy starting fresh whenever there’s a new content update (as mentioned) but on the other hand we also have CEOs who’ve spent insane hours on constructing an airport and would want to see it fitted with that same new content. Primarily, they wouldn’t want their saves to become bricked by a new update so that they’d have to refrain from updating the game. So, again from that development perspective, if there ever was a certain change we would have to make that would be of such a fundamental character, the change must stand in relation to bricking a huge number of airports (which becomes an increasingly worse scenario as we launch Steam Workshop). As of right now, I can’t see any scenario where a version upgrade would ever immediately render all previous ACEO saves unlaunchable. If that were to ever happen, or would become plausible from a development perspective, we’d instead focus on writing code that could bridge the versions and keep their integrity. I’ll never guarantee that we’ll always maintain 100 percent save integrity since the game is in an alpha stage and a lot can happen, I just deem it very unlikely at this point.

However, ACEO saves will never be backwards compatible, i.e. if you play on the experimental branch and save your game there, it will most likely not launch at all on an older version.

3 Likes

Cheers for the really detailed answer! Definitely sounds like a solid plan :slight_smile: Launchable vs entirely running makes the whole thing make lots of sense. Can’t wait to see what you guys come up with next!

3 Likes

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.