Morning folks, welcome back to the Knowledge Pool. This week we have a Bronze scenario, so discussion of the scenario will be locked and everyone can submit their answers to the form below.

Alan and Nathan are playing in a Kaladesh/AEther Revolt Limited PPTQ. Alan casts a Foundry Hornet, then attacks with an Eager Construct that has a +1/+1 counter on it. Nathan controls his own Eager Construct, but chooses not to block with it. During his second main phase, Alan casts a second Foundry Hornet.

Alan looks at this hand for a few seconds, then says “Umm… I guess it's… WAIT!” He then reads Foundry Hornet again. “Your Eager Construct dies.” Nathan calls you to the table and explains that the first trigger is missed, since it wasn't mentioned during first main phase or combat. When you ask Alan, he tells you he forgot about Foundry Hornet's trigger and didn't realize until he played a second one.

Yes, we know that Kaladesh/AEther Revolt isn't the current PPTQ format. You can ignore that when giving your answers.
Submit your solutions here: https://goo.gl/forms/8gNSnVlDI0r9E8Yq1

Thanks everyone for the great responses this week. I want to highlight two answers.

First, Rob Marti's answer

Originally posted by Rob Marti:

The Foundry Hornet trigger, similar to Prowess, doesn't change the visible board state when the first Hornet is cast so doesn't need to be acknowledged at that time. When the second Hornet is cast Nathan's Eager Construct is now a 0/0 and must be placed in the graveyard as a State Based Action.

Rob's answer is succinct and accurate. The trigger in question is similar to Prowess, and doesn't have a visual effect on the game state, so it doesn't need to be acknowledged right away. It is noticed when relevant, and we arrive at the correct result: Eager Construct is dying.

Second, Gediminas Usevičius

Originally posted by Gediminas Usevičius:

There has not been any infraction committed. Because AP remembered the trigger until it would have had an impact on the game, everything is fine, even if he admits he forgot about it at first. In the end, Eager Construct after resolving the trigger dies and is put into the graveyard.

Gedimas points out an important thing here: there is no infraction. Neither trigger was missed, so we're not going to issue a penalty. Also worth noting that Foundry Hornet's trigger is definitely not detrimental, so there is never going to be a Missed Trigger warning assessed for it.

In summary, the KP team's answer.

While Alan does appear to have forgotten one of his triggers, he has not missed the opportunity to acknowledge it, as the first time it is relevant to the game state is now. Treat the first Foundry Hornet trigger as resolved, and the second as still on the stack, Nathan can respond if he would like. Eager Construct will die when it resolves if nothing else happens.

Oh, one final thing. Joe Kull's answer points out a valid point…

Originally posted by Joe Kull:

… Lucky Alan.

Indeed, lucky Alan.