Gamestate checks vs ETB

[FireCrafted]

I'm sorry if this was answered elsewhere but I looked and tried to find it in the comprehensive rules to no avail.

I was reading the Elesh Norn Game State article where if player 1 controls {Elesh Norn, grand cenobite} and player 2 casts {banished priest}, banished priest would enter but in response to his ETB activating, the game state would check and he would die before exiling Norn.
This lead me to the question can you respond to ETB abilities after the creature has entered? Or can the game-check only move that fast?

Like p1 plays {captain of the watch} and p2 plays {terminate} in response to the ETB, denying p1 his 3 1/1 soldiers.

[Ekann1]

I think you two are talking about two different ETB effects.  When a creature enters the battlefield with something, that happens as part of the spell resolving, before game states check.

However, when a creature has a trigger worded like "when this creature enters the battlefield...." That is different. That trigger uses the stack and can be responded to

In your {terminate}/{captain of the watch} example, you would have the opportunity to cast terminate in response to the captain's enter the battlefield trigger. But, since the trigger is already on the stack, they would still get the 1/1s even after the captain is dead.


Hope this clears things up

RESOLVED (with a slight edit) 😉

[abstractApathist]

ETBs are a static ability and are therefore part of casting the spell.  Unless I'm misreading this.

603.6e: Some permanents have text that reads "[This permanent] enters the battlefield with . . . ," "As [this permanent] enters the battlefield . . . ," "[This permanent] enters the battlefield as . . . ," or "[This permanent] enters the battlefield tapped." Such text is a static ability -- not a triggered ability -- whose effect occurs as part of the event that puts the permanent onto the battlefield.

As static abilities do not use the stack, they cannot be responded to.

Those examples aren't ETB effects, they're static abilities, which are different. An ETB effect is a triggered ability with the text "when ~ enters the battlefield..." and it does use the stack and can be responded to.

112.3c: Triggered abilities have a trigger condition and an effect. They are written as "[Trigger condition], [effect]," and include (and usually begin with) the word "when," "whenever," or "at." Whenever the trigger event occurs, the ability is put on the stack the next time a player would receive priority and stays there until it's countered, it resolves, or it otherwise leaves the stack. See rule 603, "Handling Triggered Abilities."

The {captain of the watch}'s triggered ability is independent of its source, so {terminate} will not stop it. {Banisher Priest} is different because its ability is specifically tied to how long it stays on the battlefield.

[particle]

but in this example, would {elesh norn} be exiled for any amount of time (split second jk) by {banisher priest} or it would never hit exile?

[griffin131]

Sorry for my misreading.
Should I edit and remove?

[abstractApathist]

but in this example, would {elesh norn} be exiled for any amount of time (split second jk) by {banisher priest} or it would never hit exile?

The priest will trigger as soon as it hits the battlefield, but it will be killed as a state-based action as soon as its trigger goes on the stack, meaning it will fizzle.

7/1/2013   If Banisher Priest leaves the battlefield before its enters-the-battlefield ability resolves, the target creature won't be exiled.

RESOLVED

[FireCrafted]

Thank you very much I got it now

[SoshiGanrou]

There is a {fiend hunter} for thAt