Skip to content

Fuji 0.6.0

Choose a tag to compare

@github-actions github-actions released this 28 Mar 21:11

Hey y'all, it's time for another Fuji release! Again, the steady stream of new features continues as we approach 1.0.0 (if a bit slower than before). Let's review everything added since 0.5.0:

Highlights

💾 Multiple Saves

Fuji now supports multiple save files. Swap them out anytime you want from Overworld -> Pause menu -> Saves.

Huge thanks to @echoslabs for contributing code for this feature!

🌐 Overworld Extensions

The overworld has been freshened up for this release, including some new QOL:

  • See your progress on maps at a glance without having to select the card
  • Sort your maps by the mod which they come from

🛡 Better, Safer Error Handling

The error handling from last release has received a buff; it will now try to look for errors in more places and handle them as gracefully as possible. Say goodbye to the Notepad Window of Despair! (At least, for the most part. Hopefully.)

Other notable improvements

  • We've added an option in Fuji Settings to log more information to the console. This option, if enabled, logs info that may be useful for people developing mods.
  • Mods are sorted alphabetically when loading for more consistency.
  • You can now put mods in your user directory for loading - useful for anyone who has multiple installations and wants mods to apply globally. (thanks to @coolreader18)!
  • Added a new LoadingZone actor for map creators.

Bug fixes

  • Fixed an issue with code mods in zipped files not loading properly.
  • Other improvements to code mod loading (thanks to @psyGamer)!
  • Fixed a TAS desync related to climb checks (thanks to @psyGamer)!
  • Fixed positioning bugs with SolidMeshes.
  • Fixed some issues related to mod settings not saving.
  • Fixed issue related to loading mods with missing dependencies
  • Fixed issue related to mod dialog loading

Breaking Changes

Sorry to everyone whose mod was interacting with the Save instance directly, your code is likely to be broken in 0.6.0 due to behind-the-scenes code overhauls.