Still not 100% sure on that, went over the tutorial again in full (didn't skip any) yesterday to make sure I'd gotten all the rules figured since a few parts I wasn't fully clear on. And was wondering how those cases were happening where I was seemingly taking a hit while my own familiar was inactive, or they just weren't reacting since in other testing even on delay a familar seems to react when tussling. Makes me wonder if there was a wall or other card/skill in effect on some of those, but not recalling anything visually on the field for it on several cases other than the harpy (or something in front of it we didn't hit either), though with no log another played card or ability might have been affecting things, as I was still less familar with all of them at that point. Do plan to try to figure that out alongside some other things with more testing, have to put them back in my decks (mostly removed them on the general play ones after ten or so games with them). And do screen recording to make sure I don't miss anything that happened after the fact. Memory can be unreliable at times.
Though am curious on the exact rules of tussels.
By my understanding, if you are active/off delay, in your own attack phase you will have a familiar attack the first non tusseled (yet attacked) enemy familiar thats active. Lastly character if only option.
Then once attacked, if it is a familar, even if power is 0, it will return attack the first non attacked entity on your side.
The tutorial just says familairs wont attack a tusseled entity, but then say your first familiar is a wall, it attacks the enemy first (a bunny), that bunny then react attacks into the wall right? So now your third entity, another familiar has its attack, it attacks the enemy second familiar, the hostile second familiar now finds the first non tusseled entity on your side and... attacks your second familiar right? Despite it already initiating a tussle? The tutorial description felt a bit innacurate/brief there I think unless I"m mis remembering it.
Though this also leads me to question how a splash damage option would work, unless its an ability and not part of the default attack logic like the overpenetration example I gave previously. It it is, but just doesn't trigger any reaction to it specificly.
Add notes for familiar/entity/etc... category so you know what a card is/can be affected by, as while many like walls feel somewhat intuitive, it has been a point of confusion at times on why an ability didn't seem to do anything to something.