Implement means of storing hitbox/hurtbox/sequence data apart from AnimationClips.

[Skyloh]

AnimationEvents are nice, but they're wholly bound to the clip they're on. If you want to reuse animations w/ new anim events, you have to make completely new clips.

Think of a way to separate this information. Here are some brainstorms:

• Unity Timelines: I'm not very familiar with them, and they seem to be for longer sequences than just an attack that lasts a few tens of frames. Might be way too much overhead, too.
• Sequence ScriptableObject (SSO): an SO that stores data on a sequence of time associated with a AnimClip. It begins playback when the associated animation is requested, checking the elapsed time to fire its "events".
  • issue: How do I hook stuff into the SSO's events? What even needs to be hooked into it?
  • idea: Flags. State, hitbox enabling, OTG, etc. are all "toggleable" things. Maybe "events" just set/fire a string flag w/ a value.
  • issue/idea: How will I start the SSO? Do I have to make a decorator component/raw class that fires the "start sequence" method? Perhaps a universal pair of AnimEvents for "Start Seq" and "Stop Seq". How will an SSO's elapsed time be updated (since SOs don't have .Update())?
• Animator StateMachine states? I will need to do more research, but what I'm thinking is that since the states are monobehaviours, perhaps I can serialize a SSO for each clip state. There would only be one state monobehavior (used on each AnimState), and that would be in charge of playing back the SSO.
• Playables? Another area of big research. Apparently I can "bind" playables to animators; what does that mean?

[Skyloh]

The AnimatorStateMachine states seem like a really, really good option. They can be serialized, they're easy to use, the whole shebang. There even is a method on Animator to get all Behaviors of a type! I can use that to grab all the behaviours to hook them to stuff. Only issue is minor; they all have the exact same name when serialized:

If the script name is SampleScript and I serialized 3 different versions, they all look like (SampleScript), (SampleScript), (SampleScript).