[ad_1]
No, you aren’t getting “on assault” triggers for creatures that enter the battlefield “tapped and attacking”.
The cause is that being declared as an attacker is a single occasion that occurs solely as soon as per fight, on the finish of the “declare attackers” step of the fight part. It’s the occasion that triggers Kaalia of the Vast‘s potential within the first place, so by the point a creature is placed on the battlefield on account of Kaalia’s potential, that time has already handed and can’t set off the flexibility of Aurelia or Tyrant’s Familiar.
- Declare Attackers Step
508.1. First, the energetic participant declares attackers. [..]
[..]
508.1m Any talents that set off on attackers being declared set off.
508.1m is when Kaalia’s potential triggers. It goes on the stack afterwards:
508.2. Second, the energetic participant will get precedence. (See rule 116, “Timing and Priority.”)
508.2a Abilities that set off on a creature attacking set off solely on the level the creature is said as an attacker.
508.2b Any talents that triggered on attackers being declared or that triggered through the course of described in guidelines 508.1 are put onto the stack earlier than the energetic participant will get precedence; the order wherein they triggered would not matter.
Kaalia’s potential goes on the stack now, finally resolves, and a creature is placed on the battlefield tapped and attacking. That creature by no means sees the top of the “declare attackers” step described in 508.1m and due to this fact doesn’t set off its personal “on assault” potential.
[ad_2]