MvM Rules Clarification Help

Fuzzywobbit··1 votes·4,173 views

Been playing a few games (done up to mission 6) and we've run into some complications with missing rules, or rules that can be interpreted in different ways. I'd like to get an official clarification (booklet and page references if I somehow missed them), not opinions on the following.

1a) missing rule Does a Boss push minions? 1b) missing rule If the Boss does push minions, does the boss push minions into other mechs if the situation arises? 1c) missing rule If the Boss doesn't push minions, does the Boss stomp them instead?

  1. missing rule Can the Boss stand on crystal shards?

  2. missing rule What happens to a Boss when it steps into a lava pool?

  3. missing rule What happens to a Boss when it steps onto an oil slick?

  4. missing rule Is the Boss affect by spike walls?

  5. clarification Does a mech that stops on a space that has a spiked wall on it take 1 damage, or is damage only ever dealt if a mech happens to be forced into/through the wall?

2 noticable mistakes. Mission 4 is missing the Crystal Compass. Whoever was writing the rules doesn't know that 'unpassable' is uncorrect (see what I did there? I can Engrish too :P). You'll find it written correctly everywhere but where it provides rules for Massive Boulders.

3 Comments

Sexpanda1 votes

Hey there, (Although I'm not a Riot Employee and you said you want an official clarification, I hope I can help you with this. :) )

  1. The Boss doesn't push minions. It stomps them and the minions get counted on your gear tracker as I remember correctly from the missions.

  2. No, he destroys them.

  3. Nothing. Boss takes no damage from lava. (Lava has no "colour" and through the bosses mechanic that it can only take damage from an ability with the same rune shield disabled, there is no way lava could damage him because there is no rune shield that would be recharched.)

  4. Nothing. He is too big to slide.

  5. No he is not. (Same reason as in 3. Spike walls have no colour and therefor they can't do damage to the boss due to the missing rune shield interaction.)

  6. You take one damage from the spiked wall if you run into it, ergo if you step on it in the direction of the spikes. So yes there can be multiple events happening on that field (like stomping a minion or whatever) but you nevertheless take one damage from the wall if you run into it or get pushed into it)

Your "mistakes": I don't remember Mission 4 correctly, could you say what it is about? If I remember correctly you don't need the Compass in every mission. Otherwise the Compass is orientated the same way in every mission if you look deeper into it. Red is always facing up and yellow down.

Hope this helps you, ask me if you have any further questions ;)

Have a nice day, Sincerely, Panda

Fuzzywobbit1 votes

Well, the compass is a requirement in every game that a mech can suffer damage. Some damage cards will require a rune die roll. Now that I think about it, it's also used to determine who goes first at the beginning of the game XD. We just oriented the compass with red pointing up. It's always oriented that way in the other books so far, so I do not see any reason for it to change. Just pointing out that the compass wasn't shown anywhere.

A lot of this makes sense, although I prefer if there was an offical ruling, just to avoid any disagreements with who ever I game with. The one except is a boss breaking cyrstals when it steps on them, seems a bit ... advantages to the players (oh gawd I was gonna say 'broken').

Because of wording. Just to clarify my question with rough images. @ > o X

@ = Massive Boulder space/square. o = empty space/square. .> = spike wall on the boarder of a space with spikes facing --> that direction. X = mech.

  1. Does the mech take damage If the mech moves exactly 1 space forward, which would then look like this:
    @ > X o

Technically the mech isn't walking into the spikes since they are against the wall, not on the space. 2) Would the mech take damage if it moves along the spike wall, example from this: @ > o ...to this: @ > X @ > X ...to this: @ > o

  1. One of our group members beleives a spike wall damages a mech only if a move, push, etc. would make the mech pass through that border. Example. From this:
    @ > X ...to this: X > o

Naturally the mech would stay like this @ > X because nothing can enter a space with a massive boulder in it. See the perplexing possible interpretations?

edit* numbering them so easier to answer.

Sexpanda1 votes

Well, the compass is a requirement in every game that a mech can suffer damage. Some damage cards will require a rune die roll. Now that I think about it, it's also used to determine who goes first at the beginning of the game XD. We just oriented the compass with red pointing up. It's always oriented that way in the other books so far, so I do not see any reason for it to change. Just pointing out that the compass wasn't shown anywhere.

A lot of this makes sense, although I prefer if there was an offical ruling, just to avoid any disagreements with who ever I game with. The one except is a boss breaking cyrstals when it steps on them, seems a bit ... advantages to the players (oh gawd I was gonna say 'broken').

I see your point but as we (my friends and I) played and there was some kind of shadowy thing with no specific rulement in the books we discussed it and made a choice. Just to be clear about my thoughts, I played every Mission so far so I'm familiar with every thing of the boards and the discussion side of the rules. Let's go into it.

Because of wording. Just to clarify my question with rough images. @ > o X

@ = Massive Boulder space/square. o = empty space/square. .> = spike wall on the boarder of a space with spikes facing --> that direction. X = mech.

If the mech moves exactly 1 space forward, which would then look like this: @ > X o , does the mech take damage?

Yes. Simply because he is moving directly "into" the spikes.

If the mech moves exactly 1 space forward, which would then look like this: @ > X o , does the mech take damage? Would the mech take damage if it moves along the spike wall, example from this: @ > o @ > X

to this: @ > X @ > o

No. We discussed it and we said that the Mech is not moving/being pushed (or whatever) "into" the spike wall but is just moving along it. So no direct impact --> no damage.

The spike wall doesn't occupy any space, but instead is drawn along the border of a space/square. One of our group members beleives a spike wall damages a mech only if a move, push, etc. would make the mech pass through that border.

Your friend is wrong (in my opinion) because if you are like this: @ > o X and a 1-space-movement (like Lvl1-Omnistomp etc.) would then look like this: @ >X o then you would take 1 damage because you moved "into" the spike-wall-space and were coming from the direction the spikes are pointing. A movement seen in your second example would move the Mech on the space of the spike wall but not into it simply because you came out of the 90°-direction.

As I said, the last one is just my opinion and interpretation of the rules. There is (like you said) no specified information about this so we made out of it what made the most sense to us.

But im pretty sure with the boss thing. Killing the boss is hard enough in some situations and if your little 1-space-Mechs can stomp the Crystal Shards then the boss is big enough as well.

For your last example:

From this: @ > X , to this: X > o

Naturally the mech would stay like this @ > X because nothing can enter a space with a massive boulder in it. See the perplexing possible interpretations?

We discussed this within our playing group too and came to the conclusion that a Mech would take no damage from that movement/spike wall because it's already standing on the closest space possible to the wall and there is no way of moving "into" the wall ("into": coming from a space at least 1 away from the spike-wall-space).

I hope you understood everything ;) If something's unclear, just ask! Have a nice day, Sincerely, Panda

Edit: Saw the number editing too late... Rip quotes but I'll leave it that way^^

More from Mechs vs Minions