Uploaded August 2026 | Updated November 2026, 2 days ago
Reassemble can assist with aversion to make a new script or opcode equivalent (This is quite helpful in stuff like pcsx2 jump codes after some mov whatever if it's included in the script or some code that strangely changes per open pcsx2 with some game again) or the need to make multiple script variants. Also works well after wildcarding aobscan thinger.
In general when you turn a script off, the instructions/opcode/code might scramble into something unfavorable and if you trigger that current function again, you may crash the game (best be sure it's not constantly reading or writing at the time, or you're somewhere in the game where it doesn't trigger at the moment, or you truly paused the application before making the script inactive).
I'm not sure why but it happens. Like you could turn the script off once and it's good. A second time it's fine but an nth time it may scramble.
0:00 setting up reassemble() readmem()
4:55 regular auto assemble stuff
5:48 Salvaging Broken Code upon Script Deactivation
Reassemble can assist with aversion to make a new script or opcode equivalent (This is quite helpful in stuff like pcsx2 jump codes after some mov whatever if it's included in the script or some code that strangely changes per open pcsx2 with some game again) or the need to make multiple script variants. Also works well after wildcarding aobscan thinger.
In general when you turn a script off, the instructions/opcode/code might scramble into something unfavorable and if you trigger that current function again, you may crash the game (best be sure it's not constantly reading or writing at the time, or you're somewhere in the game where it doesn't trigger at the moment, or you truly paused the application before making the script inactive).
I'm not sure why but it happens. Like you could turn the script off once and it's good. A second time it's fine but an nth time it may scramble.
0:00 setting up reassemble() readmem()
4:55 regular auto assemble stuff
5:48 Salvaging Broken Code upon Script Deactivation






![Snowboard Kids 2 Recompiled: Ways To Update Scripts That Have Jmp App Name...+somehexvalue Part 1
This might apply for things other than jump,
like mov r13d [App Name...+somehexvalue]
if encountered in some script.
Anyhows, 2 Attempts for updating a script that includes some jmp:
1) Manually fixing/updating to align with the right game version CHECK
2) Reassemble for the jump updating (Definitely something I would recommend when using emulators. Option 1 usually is forced to be consistently done again per game run session again when its an emu. And that is quite unfortunate.).
0:13 Starting Option 1. Manual Fix and Checking The Script with jump
6:24 Other Things Im doing before I begin Option 2
9:44 Beginning Option 2 | Reassemble Attempt 1 (Layout Preparation)
12:00 Doing the Reassemble Method for a jmp instruction in the script
16:58 Reason Reassemble can fail (even though it should not)
18:17 Attempt 2, to do for next video, next time
Next Time (https://www.youtube.com/watch?v UJnzaD50PM) Reassemble Jmp
After Next Time (https://www.youtube.com/watch?v=r2p8efdZ6FQ) Avoid jmp fully Snowboard Kids 2 Recompiled: Ways To Update Scripts That Have Jmp App Name...+somehexvalue Part 1](https://i.ytimg.com/vi/j7vFXqgsNJk/mqdefault.jpg)



