My mechanic is called lock & load. A sample card with the mechanic is below:
Scorching Salvo 1R
Instant
~ deals 1 damage to target creature or player.
Lock & load (Exile this spell as it resolves. You may cast this card as long as it’s exiled this way. Put it into your graveyard at the beginning of the next end step.)
One of our fellow forum users, Thornstrike, said the following about this mechanic, which I was calling barrage at the time:
Quote from Thornstrike »
...there's a bit of a loophole in the Barrage wording. Any instant with Barrage has potential to be kept around indefinitely, by casting it in response to the delayed trigger that would put it into the graveyard. As it currently works, I don't see any way to close this loophole without some complex wording...
Is he correct? Can you keep instants with lock & load around indefinitely, as long as you keep casting them in response to the trigger?
1) The end step referred to by lock & load begins.
2) The lock & load's triggered ability triggers.
3) In response, you cast the spell via lock & load by putting it onto the stack, paying its costs, choosing targets, etc.
4) Assuming no responses, the spell resolves, and is put into exile again due to lock & load.
5) The lock & load's triggered ability resolves, which attempts to put an object that doesn't exist anymore (the lock & load spell as it was in exile before it was cast) into the graveyard, meaning it resolves to no effect.
Private Mod Note
():
Rollback Post to RevisionRollBack
How to use card tags (please use them for everybody's sanity)
[c]Lightning Bolt[/c] -> Lightning Bolt
[c=Lightning Bolt]Apple Pie[/c] -> Apple Pie
Vowels-Only Format Minimum deck size: 60 Maximum number of identical cards: 4 Ban list: Cards whose English names begin with a consonant, Unglued and Unhinged cards, cards involving ante, Ancestral Recall
Instead of "as long as it's exiled" you can just use the Chandra, Pyromaster wording.
Lock & load (Exile this spell as it resolves. You may cast it this turn. Put it into your graveyard at the beginning of the next end step.)
Then even if you do cast it in response to the end step trigger, you can still only cast it this turn. If you cast it during the end step, there will be one turn where it is exiled and you will not be able to cast it, then it will be put into the graveyard during that turn's end step.
If you want to clean that up, instead of dropping it into the graveyard during the end step, you could drop it during the next turn's upkeep with a trigger like Arcane Denial. The first change makes that possible since you would then not be able to cast it while the delayed trigger is on the stack.
Lock & load (Exile this spell as it resolves. You may cast it this turn. Put it into your graveyard at the beginning of the next turn's upkeep.)
How do you intend this to work if the card gets stolen with something like Praetor's Grasp and another player casts it? Should that other player be the one that can reuse it from exile? or would the ability give the card back to the card's owner?
1) The end step referred to by lock & load begins.
2) The lock & load's triggered ability triggers.
3) In response, you cast the spell via lock & load by putting it onto the stack, paying its costs, choosing targets, etc.
4) Assuming no responses, the spell resolves, and is put into exile again due to lock & load.
5) The lock & load's triggered ability resolves, which attempts to put an object that doesn't exist anymore (the lock & load spell as it was in exile before it was cast) into the graveyard, meaning it resolves to no effect.
That's what I thought. Thank you very much for the detailed explanation.
Instead of "as long as it's exiled" you can just use the Chandra, Pyromaster wording.
Lock & load (Exile this spell as it resolves. You may cast it this turn. Put it into your graveyard at the beginning of the next end step.)
Then even if you do cast it in response to the end step trigger, you can still only cast it this turn. If you cast it during the end step, there will be one turn where it is exiled and you will not be able to cast it, then it will be put into the graveyard during that turn's end step.
If you want to clean that up, instead of dropping it into the graveyard during the end step, you could drop it during the next turn's upkeep with a trigger like Arcane Denial. The first change makes that possible since you would then not be able to cast it while the delayed trigger is on the stack.
Lock & load (Exile this spell as it resolves. You may cast it this turn. Put it into your graveyard at the beginning of the next turn's upkeep.)
How do you intend this to work if the card gets stolen with something like Praetor's Grasp and another player casts it? Should that other player be the one that can reuse it from exile? or would the ability give the card back to the card's owner?
Your suggested changes make sense and sound good to me. I will probably go with your version that drops during the upkeep, since, as you said, that's a cleaner execution. Thanks a ton!
As for the Praetor's Grasp question, I honestly hadn't thought about that. Obviously, the card needs to end up in its owner's graveyard. Other than that, I don't particularly care.
I believe the point is that you can repeatedly use it over and over during the same turn. A replicate variant that enables storm. Because storm is not good enough obviously.
If you want to put the card into the graveyard this turn instead of waiting around until the next turn's upkeep, you can use the Thawing Glaciers tech and say "at the beginning of the next cleanup step".
restrict it so it only exiles if cast from your hand.
I don't think that's necessary. I doubt snapcasting a lock & load card is going to break anything- you still have to pay mana for all the uses of it after all. However, it's definitively something to be aware of and playtest. Thanks for bringing that to my intention.
I believe the point is that you can repeatedly use it over and over during the same turn. A replicate variant that enables storm. Because storm is not good enough obviously.
Precisely. Though your storm comment was made in jest, you weren't entirely wrong- this mechanic was designed as a replicate variant that enables rapidfire, another mechanic in my set that does have some similarity to storm:
"Rapidfire-If you’ve cast two or more spells this turn, (effect)"
More details about and examples of that mechanic are in this thread.
If you want to put the card into the graveyard this turn instead of waiting around until the next turn's upkeep, you can use the Thawing Glaciers tech and say "at the beginning of the next cleanup step".
Not a bad suggestion. My personal preference is to use "at the beginning of the next turn's upkeep", since I think the average player is more likely to understand how the upkeep step works versus how the cleanup step works. (I've been playing since Onslaught and, off the top of my head, I don't know the exact details of all the things that happen during the cleanup step or the specific order in which they happen.)
The End phase has 2 steps: End and Cleanup. Everything that says "at the beginning of the end step" happens... at the beginning of the end step. Cleanup is when you discard down to your max hand size, "until end of turn" and "this turn" effects end, and marked damage is removed from creatures. Players normally don't get priority during the cleanup step, but they will if the game needs to process a state based action or put a triggered ability on the stack. If this happens then the game will start another cleanup step (as many times as is necessary) before moving on to the next turn.
But I understand your motivation to use a less technical solution that won't weird out the average player. This is probably a similar reason to why all the double-faced Werewolves work the way they do.
The End phase has 2 steps: End and Cleanup. Everything that says "at the beginning of the end step" happens... at the beginning of the end step. Cleanup is when you discard down to your max hand size, "until end of turn" and "this turn" effects end, and marked damage is removed from creatures. Players normally don't get priority during the cleanup step, but they will if the game needs to process a state based action or put a triggered ability on the stack.
But I understand your motivation to use a less technical solution that won't weird out the average player. This is probably a similar reason to why all the double-faced Werewolves work the way they do.
That seems likely. Maybe someone reading this should try to get an answer out of Maro? (Assuming he hasn't already addressed this somewhere.)
Private Mod Note
():
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Scorching Salvo
1R
Instant
~ deals 1 damage to target creature or player.
Lock & load (Exile this spell as it resolves. You may cast this card as long as it’s exiled this way. Put it into your graveyard at the beginning of the next end step.)
One of our fellow forum users, Thornstrike, said the following about this mechanic, which I was calling barrage at the time:
Is he correct? Can you keep instants with lock & load around indefinitely, as long as you keep casting them in response to the trigger?
1) The end step referred to by lock & load begins.
2) The lock & load's triggered ability triggers.
3) In response, you cast the spell via lock & load by putting it onto the stack, paying its costs, choosing targets, etc.
4) Assuming no responses, the spell resolves, and is put into exile again due to lock & load.
5) The lock & load's triggered ability resolves, which attempts to put an object that doesn't exist anymore (the lock & load spell as it was in exile before it was cast) into the graveyard, meaning it resolves to no effect.
[c]Lightning Bolt[/c] -> Lightning Bolt
[c=Lightning Bolt]Apple Pie[/c] -> Apple Pie
Vowels-Only Format
Minimum deck size: 60
Maximum number of identical cards: 4
Ban list: Cards whose English names begin with a consonant, Unglued and Unhinged cards, cards involving ante, Ancestral Recall
Then even if you do cast it in response to the end step trigger, you can still only cast it this turn. If you cast it during the end step, there will be one turn where it is exiled and you will not be able to cast it, then it will be put into the graveyard during that turn's end step.
If you want to clean that up, instead of dropping it into the graveyard during the end step, you could drop it during the next turn's upkeep with a trigger like Arcane Denial. The first change makes that possible since you would then not be able to cast it while the delayed trigger is on the stack.
How do you intend this to work if the card gets stolen with something like Praetor's Grasp and another player casts it? Should that other player be the one that can reuse it from exile? or would the ability give the card back to the card's owner?
That's what I thought. Thank you very much for the detailed explanation.
Your suggested changes make sense and sound good to me. I will probably go with your version that drops during the upkeep, since, as you said, that's a cleaner execution. Thanks a ton!
As for the Praetor's Grasp question, I honestly hadn't thought about that. Obviously, the card needs to end up in its owner's graveyard. Other than that, I don't particularly care.
RUNIN: Norse mythology set (awaiting further playtesting)
FATE of ALARA: Multicolour factions (currently on hiatus)
Contibutor to the Pyrulea community set
I'm here to tell you that all your set mechanics are bad
#Defundthepolice
Ah. I didn't actually realize I had mistakenly put "your" into the reminder text. Thanks!
........................
I'm Mike, from The Mana Pool.
Check out my Tapped Out profile and comment on my decks!
I don't think that's necessary. I doubt snapcasting a lock & load card is going to break anything- you still have to pay mana for all the uses of it after all. However, it's definitively something to be aware of and playtest. Thanks for bringing that to my intention.
Precisely. Though your storm comment was made in jest, you weren't entirely wrong- this mechanic was designed as a replicate variant that enables rapidfire, another mechanic in my set that does have some similarity to storm:
"Rapidfire-If you’ve cast two or more spells this turn, (effect)"
More details about and examples of that mechanic are in this thread.
Not a bad suggestion. My personal preference is to use "at the beginning of the next turn's upkeep", since I think the average player is more likely to understand how the upkeep step works versus how the cleanup step works. (I've been playing since Onslaught and, off the top of my head, I don't know the exact details of all the things that happen during the cleanup step or the specific order in which they happen.)
But I understand your motivation to use a less technical solution that won't weird out the average player. This is probably a similar reason to why all the double-faced Werewolves work the way they do.
I'm Mike, from The Mana Pool.
Check out my Tapped Out profile and comment on my decks!
I basically knew this stuff..
...but I didn't know this. Thanks for the review of that step.
That seems likely. Maybe someone reading this should try to get an answer out of Maro? (Assuming he hasn't already addressed this somewhere.)