Yea, Inherited Tasks are objects that are still owned by the Original Ability, so you can’t modify them in child abilities. They’re meant more for logic that doesn’t need to change per Ability (including fields like animations, etc). So if you have some Attack ability that always plays “Swing 1” but the particle/sound can change - you’d want to inherit the Play Animation and then just re-create the particle / sound tasks. Child objects can’t save data in Parent Objects. I could add an option that inherited Tasks actually just copy themselves into Child Abilities, rather than just referencing the originals. There’s a small memory cost there, but it’s not much and would be a bit cleaner.
Also 4.24 has a nasty bug with recompilation that is schedule for 4.24.2, so if you’re crashing randomly in FlushCompilationMgrImpl - it will hopefully clear up in the next hotfix.