Controller Flight Mod is a control-mod record for the MelonLoader route and the captured DLL and configuration paths. It does not establish a controller feature set, a performance result, or a compatibility outcome. Those claims remain To be confirmed until they are checked in a specific setup.
What this control-mod record establishes
This record establishes only a MelonLoader route and two named file locations for the controller-flight setup. It does not turn the mod name into a claim about supported hardware or control behavior. Keep any result outside those recorded locations To be confirmed.
The page is intended for a staged check rather than a broad installation conclusion. Make one change at a time and record the condition being checked. That keeps a later rollback limited to the change you introduced.
Use the recorded MelonLoader route
Use the recorded MelonLoader route before handling the controller-flight files. Keep that route distinct from any other loader arrangement already present in a game folder. Whether another arrangement can coexist remains To be confirmed.
Record the game folder and the staged change before launching a check. This makes it possible to compare the result with the state that existed before the check. It does not confirm that the route works for every installation.
Record the exact DLL and config paths
The recorded DLL location is Approximately Up/Mods/ApproximatelyUp_GamepadMod.dll. Record that location as the file path under review before you launch a test. Do not substitute a different location as an equivalent route.
The recorded configuration path is UserData/ApproximatelyUp_GamepadMod.json. Preserve a copy of the pre-test configuration state before changing a setting. The settings available at that path and their effect on controls remain To be confirmed.
Run a low-risk flight check
Begin with one reversible configuration change and one narrow flight condition. Observe only the control change you chose to check in that condition. Record the result without inferring a wider flight outcome.
If the result is unclear, stop the staged check and restore the pre-test state you recorded. Repeat only after isolating a single next change. This is a rollback procedure for your own staged changes, not a clean-removal guarantee.
Controller and performance claims to confirm
Controller compatibility, control response, and performance claims remain To be confirmed. Do not treat one observed device or one flight check as evidence for broader support. No fixed polling value, latency value, or support percentage is established here.
Button mappings remain To be confirmed unless you have checked the exact configuration in your own setup. Do not publish a fixed mapping as though it applies beyond that check. Keep unverified control behavior outside this page's conclusion.