Announcement

From Averra to Sunfallow

The game formerly developed as Averra is now called Sunfallow – A Living World. What changed, what stayed, and how old saves find their way over.

The main menu: the SUNFALLOW wordmark with the subtitle A LIVING WORLD above a menu with Continue, New World, Load World, Join Server, Account, Character, Settings and Quit, in front of a village.
Main menu of version 0.9.1.Gameplay captureCaptured in version 0.9.1, 30 October 2026

The game that was developed under the name Averra is now called Sunfallow – A Living World. The official website is sunfallow.net. Version 0.9.1 is the rename and nothing else: gameplay, world generation, seeds and the save format did not change.

What changed

  • The name in the window title, menus, texts, the app and the documentation. The app is now Sunfallow.app with the bundle identifier net.sunfallow.game.
  • The logo. A new SUNFALLOW wordmark in pixel letters with a rising sun and a furrowed field with green sprouts, with the subtitle A LIVING WORLD. It is drawn by the project’s own art tools, like all other art.
  • The app icon. A pixel-art oak in front of a large sun disc.
  • The data folder. Saves and settings live in ~/Library/Application Support/Sunfallow/ now instead of .../Averra/.

How old saves come over

On the first start, the game copies the saves and the settings from the old folder into the new one. Every file is checked against its SHA-256 checksum, nothing in the new folder is overwritten, and the old folder is never changed or deleted. If the copy is interrupted, the next start picks up where it stopped. Damaged files are copied as they are and reported, and the game’s own loader keeps using the backup file of a world.

The migration has its own test suite with 48 checks, covering a fresh install, a full migration, a second run that changes nothing, name clashes and unreadable files. On the developer’s own data it copied five worlds and the settings file, and every file had the same checksum before and after.

What stayed on purpose

Some old names are still there because they hold data: the former name in the migration code and in old changelog entries, the AV- prefix of user IDs, and the names of the local development databases and containers. Renaming a database means migrating it, and there was no good reason to risk that for a name.

What this is not

This is a rename, not a release. There is still no public build, no download and no public server. The changelog lists the version, and the development page says what has and has not been checked.

All articles