AUML is an independent mod-loader workflow, not a player-content mod. Its captured record distinguishes this loader from the ordinary content records in the same collection. This page keeps the workflow limited to the installer behavior and file destination that the record actually identifies.
AUML loader identity
AUML is a loader workflow with its own recorded handling for compatible files. It should not be treated as a content mod that merely adds a visible feature. That distinction helps keep a loader change separate from a game-content change during review.
The captured material does not establish which packages AUML supports beyond files described as compatible with it. Treat each proposed package as To be confirmed until its current instructions identify it. Do not use this page to classify another loader's files as AUML files.
Review the installer game-location step
The captured installer attempts to locate the Approximately Up game folder. Review the location it presents before continuing with any change. If it does not find the folder, the recorded workflow provides a manual Browse choice for selecting it.
Write down the game folder selected for the current check. This keeps the observed installer step tied to one known game location. It does not establish that detection will behave the same way on another machine or installation.
Use the designated Mods folder only
Use the designated Mods folder only for files documented as AUML-compatible. The captured workflow names that folder as the destination for those compatible files. It does not make the folder a general destination for every mod-related file.
Do not place BepInEx or MelonLoader files there merely because they are mod files. Those loaders use their own recorded routes, and their relationship with AUML is To be confirmed. Keep each file location in a change record before testing.
Validate one change and keep a rollback record
Begin with one documented AUML-compatible change and record the selected game folder, added files, and result. Check only the behavior relevant to that one change after launching the game. A result from this check is limited to the configuration you actually observed.
Keep a copy of the pre-change state and a record of the files added for this check. If the result is unclear, stop and compare the recorded additions with that baseline before choosing a next step. This is cautious rollback guidance, not a claim about a removal outcome.
Package, removal, and coexistence limits to confirm
Supported packages are To be confirmed unless their own current documentation identifies AUML compatibility. The captured record does not establish any removal outcome for a setup. Keep package scope and removal observations separate from the loader identity described here.
Whether AUML can coexist with another loader is To be confirmed. Do not infer that relationship from a successful local check of one workflow. Any broader compatibility conclusion needs current instructions and a separately recorded test.