I am in very beginning stages on this of learning. I admit this is untested, but it should work. Furthermore, I fed a bunch of data from the assembly code on IDA and functions to AI. I spent the last 2-3 days total of 3 to 4 hours. Feeding it data and pretty sure this should work, this game is now made with unity framework. The other thing is I have no jailbroken device to test this, but this should work.
PS: just trying to contribute
yes these are real offsets 😃
Minion Rush Superman Mod: Fly Over the Course
*Minion Rush: Running Game* version 12.3.0 (iOS, [App Store](https://apps.apple.com/us/app/minion-rush-running-game/id596402997)),
Why Patch at the Function Start [Hidden Content]?
The goal is to replicate the old mod, which set `S0 = 30.0` and returned immediately to apply a strong upward velocity every frame. In the new function (`sub_3B407E8`), the gravity factor (stored at `[X19,#0x1C]`) normally becomes negative to pull the Minion downward. Patching at the function’s start ensures we:
- Override all complex gravity calculations (e.g., clamps at `-1.0` or time scaling) to set `[X19,#0x1C] = 30.0` for consistent upward movement.
- Mimic the old mod’s simplicity, avoiding interference from branches or null checks.
- Maintain stability by jumping to the function’s epilogue [Hidden Content] which restores the stack and registers, preventing crashes.
- Achieve the Superman effect: the Minion flies upward continuously, likely triggered by a jump, soaring over obstacles and the course.
## Original Assembly and Offsets
The original instructions at the start of `[Hidden Content] 12 bytes) set up the stack and save registers:
```arm
[Hidden Content]
Patched Assembly and Offsets
We replace these with instructions to set the gravity factor to 30.0 and jump to the epilogue for safe cleanup:
[Hidden Content]
[Hidden Content]