When you're offline, all of the asset update checks fail (of course) and
thus can prevent you from logging in. While it's possible to work around
this already by toggling certain things off such as Dalamud, the
built-in Wine etc - we should still be able to play if we have all of
that downloaded.
Now there is buttons in the network fail prompts that allow you to
continue if you understand the risks. This would also make Astra more
resilient to issues like GitHub being temporarily unavailable.
This is to prevent "surprise" situations, such as:
* You have a limited internet connection, and the game updates out of
the blue.
* Your installation is invalid, and Astra decides to suddenly redownload
the entire game.
This was lost in the QML rewrite, even though it's still useful. In this
menu you can launch the official launcher, system information and the
config backup tool easily.
I never really used this feature in Astra, and now that Kawari can
perform the login process for you (and just point it towards a Sapphire
server) I don't see a reason to support it anymore.
This uses the same profile system as the regular game, and can be used
to download the current benchmark (currently hardcoded, to be fixed
later.) Or as always, install it offline from an existing zip.
This pops up because the built-in Qt web engine is considered
"unsupported" despite the FFXIV websites working fine. Even worse, when
continuing through this check it sends you back to the homepage. Now a
cookie is set so the pop-up doesn't come up at all.
Now there is more visible and consistent information such as the number
of patches and how far you're into the patching process. It's harder to
close or quit the window while patching to prevent errors, and
installing patches no longer freezes the window.
And fixes an issue where the boot component would never properly update.