Version 1.4.0 - Early mod loading + auto-updating configs

Mods now load before the game's first scene, so everything they change applies from the moment you launch: no more "reload the level and then it works". Mod configs also update automatically when a mod adds new settings.

Upgrading

• From v1.3.0: just install this APK over the top (SideQuest drag-and-drop or adb install -r). No uninstall needed, and your saves and mods are kept.
• From an older version, or if the install is rejected: back up your game data in SideQuest, uninstall, install this APK, then restore the backup (same steps as the README's Step 3).
• No mods need to be rebuilt.

Fixed

• Mods missed the first scene. Since v1.3.0, mods loaded on the first frame of every launch, after the opening scene (TitanForest) had already set itself up without them. Anything a mod changes at scene start only took effect after a level reload, for example:

  • TitanSpawner's titan settings
  • BeastTitan's flare
  • BetterMP and CustomMaps' scene setup
  • leaderboard and reward fixes

  Mods now load right after the game's scripting runtime starts, before any scene. The one exception is the very first launch after a fresh install: mods load right after you approve the storage prompt, as before.

• New config settings never appeared. When a newer version of a mod (or the mod manager itself) added a setting, your existing config file hid it until you deleted the file. Configs now merge on launch:

  • new settings show up with their defaults
  • descriptions update
  • every value you changed is kept

  Mods get this once they're rebuilt against this version's modapi.h.

Added

• EarlyModLoad setting (Mods → Configure Mods → Mod Manager, default on). Turn it off to go back to v1.3's load-on-first-frame behaviour if a mod misbehaves; it takes effect next launch.
• signing/debug.keystore in the repo. This is the public key every patched APK is signed with, so future releases (and APKs you build yourself) install over each other without an uninstall. The README's "Patch the APK" step covers signing with it and swapping in a new libmodloader.so.

For mod authors

• lib_main() now usually runs before any scene exists. Keep it to setup: install hooks, register, read config. Don't call Unity or game methods there; do that from a hook. Every mod checked for this release already does.
• aoqmm_ensure_config() now merges new entries into existing configs (rules in MODDING_GUIDE §3). merge_config_defaults() is available in modconfig.c and exported from libmodloader.so.
• Code that has to catch the first scene on the fresh-install launch: see MODDING_GUIDE §1, "Don't rely on catching the first scene".

Full details are in CHANGELOG.md.

APK: AoQ-0.5.0-Patched.apk
SHA-256: 0e9382bc379798f1855a524a9f1892f194dcdc83ff1338ad984fe04c72eb408a
Signing certificate SHA-256: 1e08a903aef9c3a721510b64ec764d01d3d094eb954161b62544ea8f187b5953 (same as v1.3.0)