Are any of those in the data model somewhere so it could be done programmatically or are we hardcoding in specific handling? Because if we're hardcoding it's probably be good to build it around an extendible hooking system so custom lcps could in theory use it
One: on initiate an attack, we pre-populate all of these fields based on statuses and weapon tags, etc. Having a hook that can modify this config in flight would be good
Yeah may not need to be an explicit hook for the first one tbh, could just be an object containing name/func/condition to trigger that's set at the system level