[SM64] ASM Bones Erroneously Changed into CUSTOM_CMD Bones #677
Description
When working on an older .blend file (probably first created with 4.2,) on 4.5, I noticed a bunch of random CUSTOM_CMD commands added to my exported geolayout.c file.
Upon further inspection, I had discovered 3 formerly ASM/Function bones had been changed in Pose Mode to have their Geolayout Command listed as "Custom" instead of "Function".
I ended up manually correcting the bones and everything was fine from that point onward, but somehow Fast64 changed a pre-existing Function bone into a Custom CMD bone, and it would be a good idea to figure out when this might've happened and why.
I noticed someone else in the Fast64 discord was having issues with CoopDX trying to load a Geolayout with CUSTOM_CMD's as well, so it's likely I'm not the only victim of this bug.