Cactus Game Design Message Boards

Redemption® Collectible Trading Card Game HQ => Official Rules & Errata => Ruling Questions => Topic started by: browarod on January 07, 2014, 02:13:05 PM

Title: Discussion about Current First Strike vs First Strike rules
Post by: browarod on January 07, 2014, 02:13:05 PM
Redoubter is correct on all counts except #6. In the case of mutual first strike, the one that is active first takes precedence. In your example, Simon's first strike would overrule Goat's and Goat would lose by the numbers and be discarded.

MOD EDIT: This topic was split, this was originally a reply to this post (http://www.cactusgamedesign.com/message_boards/ruling-questions/questions-about-certain-rules-and-cards-2/msg520113/#msg520113).
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: Redoubter on January 07, 2014, 02:25:36 PM
Redoubter is correct on all counts except #6. In the case of mutual first strike, the one that is active first takes precedence. In your example, Simon's first strike would overrule Goat's and Goat would lose by the numbers and be discarded.

I addressed this in another thread recently, and that is incorrect.  There is nothing in the rules to indicate that this is true, and first strike is not the same as protection or ignore where the 'first in' rule can come into play; in these latter cases, the targets for the subsequent abilities are protected or immune to the new effect.

The clarification from First Strike:
Quote from: REG 2.0
If there are first strike abilities on both sides of battle, then the side that activated a first strike ability first gets the first opportunity to move the battle away from the mutual destruction state. If that side of battle is unable to move the battle
away from the mutual destruction state, the other side of battle then gets a chance.

This part shows who has initiative, not who would not be discarded.  If both characters have first strike, it is still a mutual destruction scenario.  Both are discarded if it remains so.
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: browarod on January 07, 2014, 02:28:01 PM
Which thread was that? The last time I saw an elder post on this issue they agreed with what I said, that the initial first strike would keep that character alive.
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: Redoubter on January 07, 2014, 02:30:49 PM
Which thread was that? The last time I saw an elder post on this issue they agreed with what I said, that the initial first strike would keep that character alive.

The last post (http://www.cactusgamedesign.com/message_boards/ruling-questions/first-strike-vs-rome/msg443356/#msg443356) with your answer was 2.5 years ago and referenced the Glossary, which is no longer part of the rules.  The new REG (with all of its changes) takes precedence, and I can see nothing to rule any way other than that both are discarded there.

EDIT: Added link.  Also, note YMT's case, which I share, that precedence only refers to initiative, just as made clearer in the current rules.
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: browarod on January 07, 2014, 02:51:28 PM
Are there any elder posts saying that the ruling has been changed? Because something missing from the REG could just be an oversight, lol. Unless there's specifically been a rule change I see no reason to change how it's been ruled, even if the new REG doesn't explicitly state that.
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: Redoubter on January 07, 2014, 03:01:40 PM
Many things changed in the new REG which were never announced.  Unless it is there or in another post recently, it is not a rule, that's been the precedent the Elders have set regarding other rulings (as I was told when I questioned changes to previous rules that were never spelled out elsewhere).

Unless an Elder has input on this, the rules do not give "first" status for first strike.  It isn't even possible, by the way that first strike works; it does not target the other character and stop their own first strike, and it only affects the character with the ability.  It is not the same as two character with ignore on opposite sides of the battle, which also grants immunity; there is no second component, first strike is on its own.
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: browarod on January 07, 2014, 03:32:41 PM
I don't think I ever said it was at all related to double ignore because it's not, so you're right there. It's more akin to Wandering Spirit versus Tartaros in that you have 2 things trying to control a game rule and only one of them is allowed to. First strike means initiative as well as winning a mutual destruction, but 2 characters with first strike can't both have initiative or both win a mutual destruction, so it makes perfect sense (to me) to have the first one active take precedence (which the rules DO say in regards to initiative). It DOESN'T make sense (to me) to just completely ignore the battle resolution component of first strike (which the REG's current definition does) just because both sides have it which is why it DOES make sense (to me) to continue the old ruling of "first active" conflicting ability takes precedence in the case of first strike. Just as you said, first strike doesn't target the other opponent to stop their first strike, so there's no rule basis for the battle resolution aspect not applying just because the opponent's character also has first strike.

:2cents:
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: Redoubter on January 07, 2014, 03:35:43 PM
Just as you said, first strike doesn't target the other opponent to stop their first strike, so there's no rule basis for the battle resolution aspect not applying just because the opponent's character also has first strike.

And on the same token, there is no reason why the second character's should not apply, since the first does not have a monopoly on their ability applying.

I'm making this another thread, hold on.
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: browarod on January 07, 2014, 03:37:46 PM
Just as you said, first strike doesn't target the other opponent to stop their first strike, so there's no rule basis for the battle resolution aspect not applying just because the opponent's character also has first strike.

And on the same token, there is no reason why the second character's should not apply, since the first does not have a monopoly on their ability applying.

I'm making this another thread, hold on.

But since both can't work you have to have some kind of tie-breaker, which there's already a provision for in the rules. Why should this have a special case with a different tie-breaker?

Thanks! Didn't mean to be spamming the other thread. :P

EDIT: Somehow I edited instead of quoting...silly mod powers, sorry, restored!
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: Redoubter on January 07, 2014, 03:42:27 PM
But since both can't work you have to have some kind of tie-breaker, which there's already a provision for in the rules. Why should this have a special case with a different tie-breaker?

The only provision in the rules is for determining initiative.  The "tie-breaker" would be the default case, which would be that both characters are discarded in a case of mutual destruction.

Also, this is an important discussion, not spam ;) I just didn't want it lost in the bigger thread.
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: browarod on January 07, 2014, 04:14:36 PM
I don't mean a tie breaker in the rules for first strike specifically because (as we both agree) the only one there is for initiative. The tie-breaker I meant was the general one for cards with conflicting abilities (such as my WS/Tartaros example from earlier), which I feel opposed first strikes would fall under. Opposed ignores aren't conflicting per se because the one having it first is just protected from being affected by part of the second (which 1. fits with the rules of those abilities and 2. also actually fits with the standard tie breaker I am referring to as the first active ignore gets to fully take place whereas the second one can only partially affect its target).

I feel like having neither first strike affect battle resolution is inconsistent with every other resolution of abilities conflicting with each other, including ignore. With ignores, the first one still gets the battle winning aspect of ignore even though the second one grants immunity to the ignored character (I think that's how it works?) so then why does a second first strike negate the battle winning aspect of the first first strike (lol, first first)?
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: YourMathTeacher on January 07, 2014, 04:43:01 PM
EDIT: Added link.  Also, note YMT's case, which I share, that precedence only refers to initiative, just as made clearer in the current rules.

To clarify (since that was a long time ago), I have no problem with First Strike trumping later First Strikes. However, I think we need to spell that out in the rules with proper wording. What if two banded heroes both have First Strike, does the second (and subsequent ones) get discarded in a Mutual Destruction? If an enhancement grants FS to all heroes, wouldn't that only apply to the first one anyway, thus making the term "all" useless?

The term "first" in First Strike is not a positional term any more, just like "Play the first enhancement" isn't. We have moved Redemption to a more literal interpretation of rules (which can be annoying at times). First Strike only means that the character does not get discarded in a Mutual Destruction. I see no reason why other characters cannot have that same ability in the same battle.

This is not like other situations (i.e. Ignore), because First Strike does not target other characters.
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: Redoubter on January 07, 2014, 04:55:13 PM
With ignores, the first one still gets the battle winning aspect of ignore even though the second one grants immunity to the ignored character (I think that's how it works?) so then why does a second first strike negate the battle winning aspect of the first first strike (lol, first first)?

First, on Ignore, the first character with it is immune to the battle-winning component of the second character's ignore, that's the key.  They are both immune, but since the first one already had immunity, the battle-winning component cannot affect it.  That is where this is different, there is no protection or immunity, so you cannot have the exact same situation with first strike (and besides, there is no actual 'tie-breaker' there, as they both bounce).

The first first-strike is not negated, but the situation is still mutual destruction after their first strike is considered, as there are still characters in battle opposing each other that were not removed.

I understand your point YMT, and I'll amend my position to: Either both characters are discarded or they both survive.  There can be no middle ground by the rules (where only the first one survives), but by the rules one of those two things should occur.
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: browarod on January 07, 2014, 05:01:37 PM
Either both characters are discarded or they both survive.  There can be no middle ground by the rules (where only the first one survives), but by the rules one of those two things should occur.
I still think that there IS grounds in the rules for the first one to take precedence, but both surviving also makes sense to me as that way the "survives mutual destruction" clause of first strike still functions. I feel like both being discarded makes first strike not as effective since its effects can be disregarded so easily, though.
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: Redoubter on January 07, 2014, 05:08:02 PM
I feel like both being discarded makes first strike not as effective since its effects can be disregarded so easily, though.

Well, first, we all know that keeping cards from being made less effective isn't a real part of the rulings ;)

Second, I have yet to see a FS vs FS battle.  While possible, it's only going to happen in very, very limited situations.  25 total cards (with different-brigade duplicates included in the count); 7 heroes and 7 EC (again, duplicates in different brigades), of which only a handful get used; Rome, which is very narrowly used; a few random enhancements that don't see play.
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: browarod on January 07, 2014, 05:24:26 PM
I'm of the opinion that rules should always be consistent and well-written regardless of how often they might come up.

The MtG (extended) rulebook, for example, has many, many, many pages of well-written examples/resolutions for situations I've never seen or even heard of in my many years of playing casually. While I understand that Redemption doesn't have the production/tester/drafter base that MtG has, I feel like issues that do come up at least should be corrected/clarified as needed even if a limited card pool is affected. And I feel like there are plenty of people even outside Rob/Elders that would be more than willing to assist with that (including myself).
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: Master KChief on January 07, 2014, 07:43:56 PM
Fwiw, FS vs FS in MtG results in both creatures dealing damage to each other simultaneously (effectively FS cancelling out FS).
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: TheHobbit13 on January 07, 2014, 07:48:54 PM
I found this quote on Redemption Wiki  (http://redemption.wikia.com/wiki/First_Strike)under the definition of First Strike:

"A first strike ability allows a character to survive if a battle ends in the mutual destruction state."

Synthesizing that with what the REG 2.0 says:

So If I choose Goat with Ehud and nobody can play enhancements (Ehud gets first priority then passes to Goat who cannot play anything) the battle ends in a mutual destruction state. Since they both have FS they both survive but the Hero wins the lost souls because that's what Heroes do in mutual destruction.
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: Redoubter on January 07, 2014, 07:55:33 PM
So If I choose Goat with Ehud and nobody can play enhancements I would say, based on this definition of first strike they both survive and Ehud wins the lost soul.

If they both survive, Ehud cannot win a soul.

Quote from: 4th Edition Rulebook
Mutual Destruction by Numbers
The battle ends in a mutual destruction by numbers if both the Hero(es) and the Evil Character(s) have enough strength to defeat each other. In this case both the Hero(es) and the Evil character(s) are discarded. All enhancements played during the Battle Phase are discarded to each player’s respective discard pile. JUST AS CHRIST LAID DOWN HIS LIFE TO REDEEM US, THE HERO IS WILLING TO LAY DOWN HIS LIFE TO RESCUE A LOST SOUL. Therefore, in a mutual destruction by the numbers, the rescue attempt is successful. Your opponent must select and surrender to you one available Lost Soul from his Land of Bondage. This is considered a defeat of the Evil Character because the Hero was able to make a successful rescue even though the Hero was discarded.

If the characters are not discarded, then it is not the condition that leads to a rescue by mutual destruction.

I'd also like to point out that the rules for mutual destruction support the idea that both are discarded in this case, as the clarification for First Strike specifically states that the players may move the state from the Mutual Destruction condition.  If it ends in that condition, the rules say all characters are discarded.
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: TheHobbit13 on January 07, 2014, 11:31:24 PM
"In this case" means in the case that Ehud had enough numbers to beat Goat or Goat has enough numbers to beat Ehud which is true. It just so happens that both characters have first strike and by the definition on wiki they live. "Even though the Hero is discarded" is not a rule its supplementary to theology. The character have to be in mutual destruction because their FS fire. They have to live because they both have it. And the Hero has to get the lost soul because the battle went to mutual destruction.
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: Praeceps on January 08, 2014, 12:19:35 AM
The way I see it you have two options. Either They both die and the  is rescued because it resulted in MD, (think both parties using their First Strike Blow to kill the other resulting in both dying) or they both survive and no LS is rescued because it resulted in a stalemate (think they both get the first move and thus thwart the other's killing blow).
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: Redoubter on January 08, 2014, 07:45:19 AM
by the definition on wiki

First, the wiki is not the rulebook.  Go by the rulebook and the REG themselves, which lay out that they are discarded in the case of mutual destruction, and that when they are both discarded by mutual destruction by the numbers, a soul is rescued.

Second, "In this case" refers to a situation where there is mutual destruction.  In First Strike, it specifies that when both sides have the ability each has a chance to "move the battle away from the mutual destruction state" (exact quote from the REG), meaning it is still in that state.  So, if we end the battle, then "In this case" they are both discarded.
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: AJ on January 08, 2014, 08:16:38 AM
by the definition on wiki

First, the wiki is not the rulebook.  Go by the rulebook and the REG themselves, which lay out that they are discarded in the case of mutual destruction, and that when they are both discarded by mutual destruction by the numbers, a soul is rescued.

Second, "In this case" refers to a situation where there is mutual destruction.  In First Strike, it specifies that when both sides have the ability each has a chance to "move the battle away from the mutual destruction state" (exact quote from the REG), meaning it is still in that state.  So, if we end the battle, then "In this case" they are both discarded.
+1
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: browarod on January 08, 2014, 10:29:35 AM
First, the wiki is not the rulebook.  Go by the rulebook and the REG themselves, which lay out that they are discarded in the case of mutual destruction, and that when they are both discarded by mutual destruction by the numbers, a soul is rescued.
The wiki is copied directly from the REG for cases of special ability definitions so you needn't really be splitting hairs like that. :P

And while I get that this is the current interpretation of what the REG says, my whole point is that it shouldn't be that way because of how first strike works. If that means chancing the REG, then that's fine, but having mutual first strike shouldn't just magically invalidate the "survives mutual destruction" aspect of the ability. And since nobody wants to agree with me that there's precedent for "first active wins" I'm moving my stance to the state that both survive since that also makes sense AND is consistent with the definition of first strike.
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: Master KChief on January 08, 2014, 11:40:01 AM
That's not logically intuitive then. The reason a first strike character survives in mutual destruction is because that character is 'hitting' before the other character has a chance to assign lethal damage back. What is intuitive about letting two characters that are hitting each other first both survive the battle?
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: browarod on January 08, 2014, 11:42:51 AM
That's not logically intuitive then. The reason a first strike character survives in mutual destruction is because that character is 'hitting' before the other character has a chance to assign lethal damage back. What is intuitive about letting two characters that are hitting each other first both survive the battle?
MtG first strike =/= Redemption first strike, there is no "hitting first" in Redemption, lol. The rules state that a character with first strike survives in a mutual destruction scenario. Logically, if 2 characters have first strike then shouldn't they both survive?
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: Redoubter on January 08, 2014, 11:45:21 AM
The rules state that a character with first strike survives in a mutual destruction scenario. Logically, if 2 characters have first strike then shouldn't they both survive?

The rules also state that when both sides have it, each side has the opportunity to "move the state away from mutual destruction," meaning that is still the state.  The rules for mutual destruction says if the battle ends in that state, both sides are discarded.  You can also say that, following the rules logically, both are discarded.

So, we are at an impasse.  Is there any Elder input we can get on this?  I think that, regardless of the ruling they want, the entry is going to need to be updated, as it is obviously able to be read in completely different ways currently.
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: Master KChief on January 08, 2014, 11:49:58 AM
Surviving in mutual destruction because of first strike is just another way of saying one character hits another character first at battle resolution. It's not hard to make that logical leap.

However, saying both survive because they both have first strike makes no sense and is just an exploitation of what the rules say versus what they actually mean. Does double first strike somehow put a magical immunity bubble around them both? That doesn't sound intuitive in the least.
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: YourMathTeacher on January 08, 2014, 12:22:07 PM
Surviving in mutual destruction because of first strike is just another way of saying one character hits another character first at battle resolution. It's not hard to make that logical leap.

I'm OK with the logical leap, but we need the rules to state as much. As evidenced by this thread (and apparently previous threads), we are all not in agreement with what the rules are saying.

A simple addition like:

If more than one character in a battle has a First Strike ability, only the first character presented in that battle will not be discarded in a Mutual Destruction. All other characters will be discarded regardless of their First Strike ability.
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: browarod on January 08, 2014, 12:48:49 PM
First Strike entry in REG:
A first strike ability allows a character to survive if a battle ends in the mutual destruction state.

The rules also state that when both sides have it, each side has the opportunity to "move the state away from mutual destruction," meaning that is still the state.  The rules for mutual destruction says if the battle ends in that state, both sides are discarded.  You can also say that, following the rules logically, both are discarded.
I'm not denying, nor have I ever denied, that it says that. I fully agree that it says that (I can read, you know :P). First strike only applies in mutual destruction scenarios so obviously it's still in a mutual destruction state if we're discussing first strike, and the part I quoted above (which is the part I've always been referring to) also states the same. We're not in disagreement on that point, haha.

However, first strike specifically states, as quoted above, that it allows a character to survive mutual destruction. There's nothing later in the definition or clarifications that says a character doesn't get to survive if an opposing character also has first strike. The only clarification is how to determine initiative if both sides have first strike which makes sense. It doesn't say anything about changing the fact that first strike keeps the character alive.

I feel like people are getting stuck on the name of the ability (first strike) and assuming that means something is sneaking in before something else when that's not the case by the definition of the ability. If the ability was called "vacuum cleaner" and the entry said "A vacuum cleaner ability allows a character to survive if a battle ends in the mutual destruction state" I don't think we'd have people clamoring that the vacuum cleaners end up sucking each other up and both dying. :P

Spoiler: Obligatory Vacuum Cleaner card (hover to show)
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: Master KChief on January 08, 2014, 01:13:27 PM
Special abilities for the most part are named so they do something associated with its namesake. That's what makes special abilities intuitive towards the player on how they're possibly supposed to operate. 'Vacuum Cleaner' and surviving mutual destruction draws no parallels whatsoever.

I can understand where you're coming from based on a strict reading of the ability which can cause some workarounds and exploits, but I have a strong feeling that is not what is intended with the ability.
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: redemption collector 777 on January 08, 2014, 01:23:21 PM



Maybe this has been already addressed , just a thought

While discussing about First strike rules maybe we could also consider what might/would happen if 2 heroes in battle have first strike and 1 (or 2) EC has First strike and both sides have enough strength to defeat each other. who would survive? etc
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: TheHobbit13 on January 08, 2014, 01:31:16 PM
I can understand where you're coming from based on a strict reading of the ability which can cause some workarounds and exploits, but I have a strong feeling that is not what is intended with the ability.

I lol'ed the first time I read that definition. Your interpretation is much more intuitive, however, many rulings are far from that way and follow strict readings of the rules. So I agree with you and everyone else that things need to be cleared up. Even if it is clear to some people its obviously not to others which is unneccessary given.


What could you really do about it? Just define FS along the lines of defeating and therefore the character indirectly suvives? So like

FS.  "A first strike ability allows a character to defeat the opposing character in battle in the mutual destruction state." And add a clarification about FS vs FS too. I wonder if there is a problem there with defeat since both characters are "defeating" each other but maybe not because that is what is happening in mutual destruction anyways.

Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: redemption collector 777 on January 20, 2014, 03:14:22 PM
Just wondering did we come to a conclusion about First strike vs First Strike?

Is it do both discard each other , whoever had it first or both return to territory?? 

or is this topic still debatable?
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: Redoubter on January 20, 2014, 04:36:51 PM
We pretty much need some Elder input, all sides have basis in the rules.  We'll try to get some Elder input on it.
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: Prof Underwood on January 21, 2014, 05:44:52 AM
1 - I'm not completely convinced one way or another, and reserve the right to change my opinion on this after reading input from other elders and forum members :)

2 - I have had the traditional view that "First Strike" means that a character strikes first in a mutual destruction situation and therefore discards the other character and survives.  I have also always played by the "first person with First Strike wins" caveat.  Therefore my leaning would be something like YMT proposes:
If more than one character in a battle has a First Strike ability, only the first character [to activate that ability] in that battle will not be discarded in a Mutual Destruction. All other characters will be discarded regardless of their First Strike ability.

3 - Without this clarification being added to the rules, I think that the most logical outcome would be that both characters are discarded and a LS is won.  I am most opposed to the idea that both characters survive.
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: Redoubter on January 21, 2014, 01:49:21 PM
I have had the traditional view that "First Strike" means that a character strikes first in a mutual destruction situation and therefore discards the other character and survives.  I have also always played by the "first person with First Strike wins" caveat.

I'd be concerned about this view due to the overhaul necessary to First Strike in order to make it work that way, because you'd have to make it so that any other First Strike abilities aren't able to work, and that involves that first activation being able to 'restrict' the other activations, which also seems illogical (that those other abilities do nothing, even when not being targeted).  It would also lead to some very complicated rules involving multiple First Strike abilities and negation/undoing negation.

My recommended rule:

"If more than one side of a battle has at least one character with First Strike, first compare the strength and toughness of each side, only using the strength on those characters with First Strike; if one or both sides would be discarded by that strength alone, then those characters are defeated (being defeated for the purposes of determining initiative, or defeated and discarded if during Battle Resolution).  If any characters remain after this step, resolve the battle without considering First Strike present."

So, basically, all First Strike strength is used first, and one or both sides could be defeated in that step, then you could determine initiative exactly as the current rules specify, but you'd also have the ability to use it to determine mutual destruction or defeat at the end of battle.
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: Praeceps on January 21, 2014, 02:06:20 PM
O we could resolve it with a shot and sweet addition. If both sides of a battle have first strike, it is resolved with all dying. Keeps things simple. No funky math, no worrying about whose was negated and reactivated or anything similar. If both sides have an active first strike ability both sides die. Easy, clear, no misunderstandings.
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: Redoubter on January 21, 2014, 02:33:00 PM
O we could resolve it with a shot and sweet addition. If both sides of a battle have first strike, it is resolved with all dying. Keeps things simple. No funky math, no worrying about whose was negated and reactivated or anything similar. If both sides have an active first strike ability both sides die. Easy, clear, no misunderstandings.

I think this is made in jest, but we obviously wouldn't want to have a situation where one side would be discarded if they have more toughness than the other side's strength ;)
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: The Guardian on January 21, 2014, 02:51:40 PM
I think Praeceps was implying a mutual destruction situation with First Strike on both sides.

I have also always been under the impression that the "first" First Strike takes effect and all future First Strike abilities are essentially ignored. I don't see the need for an overhaul simply because that is what I always believed the rule to be, and I thought that it was stated in the rulebook and/or REG. I'm like 99% certain I've read that rule in the REG before--though it was likely an old version of the REG.
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: Redoubter on January 21, 2014, 03:26:29 PM
The rules specifically mention that there can be two different sides with First Strike, and even goes into how to handle them for initiative:

Quote from: REG 2.0
If there are first strike abilities on both sides of battle, then the side that activated a first strike ability first gets the first opportunity to move the battle away from the mutual destruction state. If that side of battle is unable to move the battle away from the mutual destruction state, the other side of battle then gets a chance.

So, according to the rules, we know that the other first strike activations aren't 'ignored'.  I'm not even sure how you could have that happen, since the ability doesn't target anything so that it could do so.  It would be an overhaul to actually put it in the state that only the 'first' works.
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: The Guardian on January 21, 2014, 03:36:44 PM
That is the current REG, which I agree is the final word, however I am unaware of when such a change was made. Apparently the "overhaul" already happened.  :P
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: CactusRob on January 21, 2014, 03:43:36 PM
MtG first strike =/= Redemption first strike, there is no "hitting first" in Redemption, lol. The rules state that a character with first strike survives in a mutual destruction scenario. Logically, if 2 characters have first strike then shouldn't they both survive?

Correct. I misread browarod's last sentence.  Since there is no advantage if both have first strike then in a mutual destruction both characters are discarded.  When I re-read it today, I saw that it sounded like I was saying both characters survive in a mutual destruction.

First strike adds an advantage if one character has it and the opposing character does not.  If two opposing characters each have first strike neither has an advantage as it relates to First Strike.

Using rulings on a things like protection, I can understand how players could assume that "first in" might apply to First Strike.  But, with First Strike it does not matter.
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: redemption collector 777 on January 27, 2014, 01:22:35 PM
MtG first strike =/= Redemption first strike, there is no "hitting first" in Redemption, lol. The rules state that a character with first strike survives in a mutual destruction scenario. Logically, if 2 characters have first strike then shouldn't they both survive?

Correct I misread browarod's last sentence.  Since there is no advantage if both have first strike then in a mutual destruction both characters are discarded.  When I re-read it today, I saw that it sounded like I was saying both characters survive in a mutual destruction.

First strike adds an advantage if one character has it and the opposing character does not.  If two opposing characters each have first strike neither has an advantage as it relates to First Strike.

Using rulings on a things like protection, I can understand how players could assume that "first in" might apply to First Strike.  But, with First Strike it does not matter.




Should this ruling that Cactus Rob just said , should be added to the REG in the First Strike Definition asap?  The if two opposing characters each have first strike part of it?
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: Redoubter on January 27, 2014, 05:04:19 PM
Should this ruling that Cactus Rob just said , should be added to the REG in the First Strike Definition asap?  The if two opposing characters each have first strike part of it?

I'm sure it will be added in an update to the REG when that next occurs, but there will be an updated FAQ soonish that should help put these types of boards-only rulings together until the update is able to happen.  It is the rule, we'll just have to get it to the right places (once the wording is hammered out, too) :)
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: browarod on January 27, 2014, 05:42:13 PM
In the meantime (until the REG is updated) I have added the clarification (I don't think anything changed, just confirmed to be how it's usually ruled) to the appropriate page of the Wiki which displays on the right-hand side of the home page/landing.
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: CactusRob on February 06, 2014, 03:40:56 PM
I edited my post above.
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: browarod on February 06, 2014, 05:13:20 PM
I edited my post above.
Thanks for the clarification! :)
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: The Guardian on February 07, 2014, 01:47:06 AM
I have also always been under the impression that the "first" First Strike takes effect and all future First Strike abilities are essentially ignored. I don't see the need for an overhaul simply because that is what I always believed the rule to be, and I thought that it was stated in the rulebook and/or REG. I'm like 99% certain I've read that rule in the REG before--though it was likely an old version of the REG.

Quote from: 10th Anniversary Rulebook
If opposing characters in battle both have first strike ability, the character who gained it first takes precedence.

I'm fine with Rob's ruling, but it is a change...I knew I wasn't crazy, well not that crazy anyway...  :o
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: Redoubter on February 07, 2014, 07:09:09 AM
Yeah, I was actually wondering if that quote was expanded into the new REG for the initiative order, and if perhaps that is what it was initially supposed to refer to (precedence in playing, not in surviving).  Who knows, but at least we have a ruling?
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: MonMaster on February 07, 2014, 11:50:32 AM
That's not logically intuitive then. The reason a first strike character survives in mutual destruction is because that character is 'hitting' before the other character has a chance to assign lethal damage back. What is intuitive about letting two characters that are hitting each other first both survive the battle?
MtG first strike =/= Redemption first strike, there is no "hitting first" in Redemption, lol. The rules state that a character with first strike survives in a mutual destruction scenario. Logically, if 2 characters have first strike then shouldn't they both survive?
Ok,
1) I know that CURRENTLY MtG FS =/= Redemption FS, but for GAMING RULE SAKE, PLEASE listen to the reasoning!
2) since i'm using another game as an example (MtG) I took their ruling wordings from their customer service page as follows(copy & paste from http://wizards.custhelp.com/app/answers/detail/a_id/133 <- only listed as a resource for argument):
Comprehensive Rules:

702.7. First Strike

702.7a. First strike is a static ability that modifies the rules for the combat damage step. (See rule 510, Combat Damage Step.)

702.7b. If at least one attacking or blocking creature has first strike or double strike (see rule 702.4) as the combat damage step begins. the only creatures that assign combat damage in that step are those with first strike or double strike. After that step, instead of proceeding to the end of combat step, the phase gets a second combat damage step. The only creatures that assign combat damage in that step are the remaining attackers and blockers that had neither first strike nor double strike as the first combat damage step began, as well as the remaining attackers and blockers that currently have double strike. After that step, the phase proceeds to the end of combat step.

702.7c. Giving first strike to a creature without it after combat damage has already been dealt in the first combat damage step won‘t prevent that creature from assigning combat damage in the second combat damage step. Removing first strike from a creature after it has already dealt combat damage in the first combat damage step won‘t allow it to also assign combat damage in the second combat damage step (unless the creature has double strike).

702.7d. Multiple instances of first strike on the same creature are redundant.

I will now translate this seemingly mindless babel into Redemption terms:
Comprehensive Rules:

702.7. First Strike

702.7a. First strike is an ability that modifies the rules for combat.

702.7b. If at least one Hero or Evil Character has first strike as combat damage begins. The only creatures that assign combat damage in that step are those with first strike. After that step, instead of proceeding to the end of combat step, the phase gets a second combat damage step. The only creatures that assign combat damage in that step are the remaining Hero or Evil Character that had neither first strike as the first combat damage step began. After that step, the phase proceeds to the end of combat step.

702.7c. Giving first strike to a Hero or Evil Charater without it after combat damage has already been dealt in the first combat damage step won‘t prevent that Hero or Evil Charater from assigning combat damage in the second combat damage step. Removing first strike from a Hero or Evil Charater after it has already dealt combat damage in the first combat damage step won‘t allow it to also assign combat damage in the second combat damage step.

702.7d. Multiple instances of first strike on the same creature are redundant.

Now I realize that this covers the multiple "First Strike" I believe is in question. As for "Mutual Destruction via Multiple First Strike", refer to regular combat rulings on "Mutual Destruction" and YES, the Lost Soul IS RESCUED via our current "Mutual Destruction" Rules.

If the GAMING RULES worked for MtG, WHY can it NOT work for Redemption?
Title: Re: Discussion about Current First Strike vs First Strike rules
Post by: browarod on February 07, 2014, 12:19:36 PM
For one thing, Redemption doesn't have "combat damage," you either survive battle or you don't, there's no damage counters or reduced toughness from battles if you survive.

As such, you can't really have multiple "combat damage steps" since there is no "damage" to assign in the first place, which is why the concept of "first strike" is different.

Second, Rob's ruling is basically the same as what you suggested anyway. If both sides have first strike then they still "deal damage" (for what that means in Redemption) at the same time and, thus, neither actually has an advantage.

So, not really sure what you're arguing since the ruling agrees with you. :P
SimplePortal 2.3.3 © 2008-2010, SimplePortal