Haha. I skipped that part of the manual.
On my small mod list is a pet mod that adds a monkey with a divers helmet to try and lay something out for pet mods. Throwing sea loafs would be a nifty attack.
EDIT: I'll probably copy this to the start of the topic, but, form checklist stuff.
Song - Yes
Skin - Yes
LMB - Yes
RMB - Yes
Keyboard/Gamepad Input - Nope
Charging Skills - Nope
Simplified Custom Skills - Nope
Flourish Animation - Nope
Song Symbol Menu - Nope
Reusable Structure - Kind off...
Commented Script - See above.
If I want to get really picky. Li.lua has custom script where he reacts to certain forms Naija is using and I might add some easy function for doing a form tutorial when you first switch to a form. As you can see, I'm still quite a bit of way from being done.
My idea of hiding the original changeForm() call in scope and calling it from my own override didn't work. I just can't seem to store off the old changeForm() code into another function with a diff name without causing a crash or just failing. I've settled for using setForm() so that it matches better with setCostume(). If something doesn't come to me eventually then I'll use the same thing for locking form changes. We shall see.
I'm working on capturing the game pad input right now. I think I can even cancel out bursting and allow the user to replace it with something else by calling something if avatar_IsBursting() is true. Although I wouldn't recommend using it as it would add a futher layer of complexity to the controls which shouldn't strictly be necessary.
