Alright, I'm making an attempt now to see if it worked; will update when its done...
EDIT: ...Did absolutely nothing different? Re-Generating cache to see if I missed a step...
EDIT2: Nope, literally no difference... No crashes, no different animation, no glitches. The move is exactly the same. Maybe SaltySD won't load it for some reason? But it popped up in the cachegen.py cmd window when it got cached, so I don't really know...
Gotta get to bed now; I've been awake too long.
FINAL MORNING EDIT: I just realized what that motion.mtable does.... It seemed like it wasn't doing anything, but come to think of it, its because I already copied the Main/SFX/GFX and whatnot over to the other move; motion.mtable determines where in the code each move is, not which animation it plays. Its sort of like the Subroutine Command, which does not change the animation itself either.
EDIT: Yep; testing confirmed, I reverted all the code changes, but with motion.mtable, one move is still replaced with the other one.
EDIT: ...Did absolutely nothing different? Re-Generating cache to see if I missed a step...
EDIT2: Nope, literally no difference... No crashes, no different animation, no glitches. The move is exactly the same. Maybe SaltySD won't load it for some reason? But it popped up in the cachegen.py cmd window when it got cached, so I don't really know...
Gotta get to bed now; I've been awake too long.
FINAL MORNING EDIT: I just realized what that motion.mtable does.... It seemed like it wasn't doing anything, but come to think of it, its because I already copied the Main/SFX/GFX and whatnot over to the other move; motion.mtable determines where in the code each move is, not which animation it plays. Its sort of like the Subroutine Command, which does not change the animation itself either.
EDIT: Yep; testing confirmed, I reverted all the code changes, but with motion.mtable, one move is still replaced with the other one.
Last edited by Mattshark,