702.66a Gravestorm is a triggered ability that functions on the stack. “Gravestorm” means “When you cast this spell, put a copy of it onto the stack for each permanent that was put into a graveyard from the battlefield this turn. If the spell has any targets, you may choose new targets for any of the copies.”
When casting Bitter Ordeal, does the number of copies lock in once the Gravestorm trigger goes onto the stack, or does it included any permanents sacrificed between that point and the resolution of said trigger? My impression is that it would indeed include them, but I wanted to confirm.
The Storm mechanic (below) specifies that only spells cast previously in the turn count. If triggers naturally locked in the values at the time they hit the stack, this phrasing should be redundant. Also, I'd expect Pandemonium to deal damage equal to the creatures power upon ETB, rather than power upon trigger resolution (which Gatherer currently indicates).
702.37a Storm is a triggered ability that functions on the stack. “Storm” means “When you cast this spell, put a copy of it onto the stack for each other spell that was cast before it this turn. If the spell has any targets, you may choose new targets for any of the copies.”
10/4/2004 The triggered ability does not check the creature's power until the ability resolves. If the creature is not on the battlefield when the ability resolves, it does damage equal to the power of the creature right before it left the battlefield. This means that if a creature enters the battlefield which can destroy itself as a "enters the battlefield" ability, the order of resolution of the triggered abilities does not matter. [/auote]
