Empower in general is a powerful tool but it is misplaced with mercy as (to me) it is not strong enough. It feels too random and situational. I have played it on a team but not with maw. This does mean that i have not felt the op team synergy that people keep talking about. I think if they put empower on say alchemist would be op, or on valkyrie then it would be op. If the put it on giant spider not so much but on mercy it just feels like fluff. However i do want to make a note that this is how it feels to me from my own experiance and might be different for others.
I adore Mercy as a troop, but i have been on the receiving end of her filling Maw on one turn. It happens, but with the arrival of Queen Mab, the Mercy/Maw means nothing to me. That is my PoV.
That is a respectable view on the matter. Weird place to do this but with the new troops (that are subject to change) what are your thoughts on if/when/might have any impact on the meta and if so how or to a lesser degree what teams would you build if you had access to the troops revealed?
Why do you think that it is so hard to fix Maws 3rd trait that should have a 15% devour chance?
Because the other troops sometimes will “miss” the devour and have a lesser body that is much more “killable” in a proper set of moves. Despite the glitch with skulls spam a troop that can remove another troop with 100% chance, even on a single cast, and also receive the life, attack and armor of the destroyed troop is insanely strong.
“Oh, but i can lure the A.I with skulls.”
- Yep, and if the trait triggers you are even more screwed.
“But even with three troops you can still manage to win the battle.”
- Sure, but you are facing a much bigger threat, the stronger the lost troop was the stronger will be the enemy’s Maw, and with any luck cascade things will scalate into a onslaught easily because you will have to handle a bigger Maw while the A.I can keep collecting mana because it still have other three playable troops.
“You can counter Maw, with your own Maw”
- More proof that Devour as mechanic is plainly broken… If the best you can do to beat it is join the club then something is clearly wrong.
My approach to limit devouring enemies to 50% bonus, IMHO, would help to keep more diversity in teams, Maw would still work well when you use it because you can still remove a key/troublesome troop and get a boost to Maw’s raw status. It would just not be so prevalent in almost every team composition of anyone who has this troop.
I also must add that the Mercy/Maw and Mercy/Infernal King are the only combos in the game that will give a high level player any sort of chance of gaining traction on the leaderboard. That being said, that is the current meta. They are the only combos that will net you wins or hopefully a skip.
This is true as i have noticed in high level play but this does not affect me as my levels are still low enough that random builds are what i face.[quote=“Eika, post:244, topic:1280, full:true”]
Why do you think that it is so hard to fix Maws 3rd trait that should have a 15% devour chance?
[/quote]
They would have to recode the way gems are matched.
Possibly, still it has gone some months now, I am not into any coding at all, and knows it is often difficulty from some of my friends, so I dont blame the devs.
Lol. I am no programmer. I have no clue.
haha, you never know.
Basicly if you match 2 sets of skulls then they are seen as two different attacks and you can extrapolate from there.
I see this more as a symptom than a cure. We have Maw making battles simply too fast because of the overwhelming status after devouring something, hence why people can just beat anyone as long as they have Maw. “Oh look, Gorgotha fully traited ahead… Nomnomnom…”
And we have Infernal King being just annoying by ressurrecting over and over, the highest number of ressurrections i faced were three in a battle i’ve won and five on one i’ve lost, since then i’m avoiding him…
I hope that i’m not sounding rude, but that’s just how i see things. No, i still don’t have an answer to how pvp can be improved without resorting to Maw/Mercy/Infernal King/“Metaish” teams.
I understand your logic. I will say this. Last week, I played against a Maw team and I cast my Mercy to block the AI’s Mercy. Next turn, the AI matches a brown and skull match fell top-right hand corner and My Gorgotha was devoured, extra turn and Mercy casts and devoured my Crimson Bat, cascade and I lost my last two troops on skull matched devours. Rarest thing to ever happen. Yet, it happened.
The very reasons high level play is plagued with them. You either put them on a defense team or stand in quicksand. That is the dilemma at the top sort of speak
I don’t use Maw or IK but True Damage does the job well of getting me up the leaderboard. The current state of pvp points lost per AI controlled battle is what is making it difficult. Not impossible but if the losses outweigh the wins I will end up not even trying for anything on the leaderboard and just focus on getting to tier 1 and leave it at that. The only reason I do ranked battles is the rewards. More gold for me. More trophies for my guild.
I’m not a programmer, but from my basic knowledge, in theory, they could redo that any multiple separated combinations of three or more would work just like connected combinations of four or more. Each extra skull, in separated combinations, would be adding only one extra damage and be treated as one single attack. It may have an unseen issue with this since i don’t know how GoW is coded, but as i said: “…in theory…”
You would be right however the way the skulls are programmed are the same code for the gem matches however i do not think it doubles the damage on 5+ matches anymore.
Yeah, i don’t know either, oh and one issue i see with this rework is that skull spam based troops would be nerfed as colateral damage.
Yes. True Damage is viable; but now that Queen Mab is prevalent, we are all feeling the wind taken out of our sails. I win a match and there are three defensive losses waiting for me. Now that is my experience. Results may very.
I had not thought about that actually. That would wreck so many teams.