I’m not picky, heck I even liked 1.0 suicide rez mercy. As someone who enjoys ana or moira more currently despite many many mercy hours I hope they find a middle ground where she is balanced AND fun.
1 Like
Not at all.
She was NEVER Tier 1 pre rework which is must pick material.
She was Tier 2 in lower ranks because, for the thousandth time, she is the easiest and most reliable healer.
She wasn’t optimal at the higher ranks but she was still viable.
This is going to be my last reply to you because I am actually losing my mind.
So as a summary:
Mercy was never a must pick, but was incredibly strong in lower elos due to her basic kit that was easy to utilise. She was also incredibly strong due to the fact the only other main healer is difficult to play as well as being F-Tier.
Current Mercy and pre rework Mercy are both balanced. The first is preferred by the community, where as the latter is preferred by a lot of the people who play her.
2 Likes
You are always welcome! the battle continues, avoiding ignorance and making clear answers is the most civil way of handling this things and you and some others are ones of the few capable of doing so. It was a matter of time before you and some others would have come here too!
1 Like
D’aaaw, thanks! I can only hope to one day be on the level of Mercy community leaders like Macster and Titanium. We’ll keep fighting the good fight until our Angel is ressurected!
I can assure you with 100% certainty that if Jeff said this, the last part would be ignored and there would be a daily thread asking for the status of the Mercy changes because “they were promised.”
I’m not sure what line of work you’re in, but this is exactly how customers of a product (especially in software) behave when you give them any kind of official response.
By “people keep posting in it” I really mean they make new Mercy threads (typically entitled “Stop ignoring the Mercy megathread!”) that get merged in, and thus it is a common source of an ever increasing post count, which likely has about 50 useful posts in the entire thing.
For example, this thread now has 127 posts and not a useful thing has been said or agreed upon by any party involved. It will be merged and then suddenly the megathread added an additional 127 replies! Then another thread will be created saying that theres another 127 replies that the devs haven’t read yet.
Well, you are right too, i’m sure the phrase could be developed more and thinked better by the professionals but i’m pretty sure our friend Melke here just wanted to make us an example phrase… You are right tho on stating that even the smallest word coming from a CEO do matters and that’s something to be kept in mind.
I have more then 50 useful posts in my offline archive in case the online threads gets deleted and i can assure you i’ve not saved every good post there was in there, also because i can’t physically read them all, lol…
What do you consider to be a “useful post”? Your and my definitions may be different.
A useful post to me is something constructive that takes care of the needs of both parties involved and tries to find an acceptable agreement for both sides.
I’m not judging, you could be considering useful some other aspects i’m not looking that much into, what did you look into to consider them good?
And btw, i do agree that we have not came to anything final in this thread 'till now, but that was not the scope of this thread. I wanted to discuss this topic and give attention to it in case someone from the company actually read it…
So you’re basing your argument that Mercy wasn’t a must-pick based on 2% of the playerbase?
1 Like
Generally the only replies I considered to be useful are the ones that gave direct examples of what to change. Bear in mind I’ve by no stretch of the imagination read every post and I’m filtering out a lot of duplicates in my head from what I remember to come up with a ballpark of 50. The other 7000+ replies have all just been bickering disagreements like pretty much this entire thread (myself included).
So if he said that they knew what the problem was but they had more urgent things (namely that list and maybe something after that)
we might have the same response but at least defenders would have a leg to stand on other then “hurr durr he wasn’t gonna win”
He couldn’t win but he didn’t even try to, all he did was give a tone deaf response that made it look like he never even looked at the thread at all.
You two are free to post this discussion here as much as you want because it’s interesting but i would suggest you to avoid in the future discussing about numbers if they don’t come from an official source and are provable… It’s a bit pointless…
You are right but do consider the place where i’m coming from too, we have given tons of actual feedback and there are surely valid points too in that thread. If the problem was really the lacking of ideas anyone could simply browse that mess and find them easily, they could even ask for advice… I love the fact that you are so concrete when discussing this topic but we’ve put a lot of effort and it would be stupid by me to post any ideas and pass them as the best that in 90’000 post have been posted. I do have valid posts saved but those are valid for me, in a forum someone could disagree and find them less useful than others you will find there…
It’s fine if you don’t, but I was curious if you could post those ideas, there’s just too much in the megathread to go through and I’m really interested in other peoples’ ideas and thoughts. ty :3
1 Like
The devs actually have posted the specific ratios of active playerbase per rank.
M+GM is less than 2%.
Sure then! I’ll be glad to do it in a second!
Then it’s my bad and i beg your pardon, please do post every link in here to those numbers in case it’s needed to the conversation. That’s not a problem of trust but to actually avoid going in circles with the discussion.
Huh, guess I was off by a bit.
https://us.forums.blizzard.com/en/overwatch/t/competitive-mode-tier-distribution/972
M+GM is 4%, although I thought they posted it with decimals before.
Thank you 
I’ll be posting here the ideas of other users and i will put their name to give them credit when linking is unavailable, do keep in mind this are all different kind of posts i found useful to different situations, so they may not be all talking about the same things.
first is Macster's post
then you have Silawatsi's post, the guy that was up here a while ago
SmellyToast had some interisting ideas too
I have been for:
- A revert
- A rework
- Removing rezz
I dont care which one it is, but mercy brings no diversity. Feel free to prove me wrong.
You can pick zen for burning shields or tank comps.
You can pick ana if you want to combo with certain dps ults.
You can pick lucio if the map favors him or if he has a very immobile comp for speed boosts.
You can run ana or moira in heavy brawls to aoe heal your teammates.
Mercy fits everywhere and nowhere. She has nothing special that would make picking her better or worse for your team.
You have no gameplay potential in her kit (and repeatedly explained this 10 times already.)
Rezz:
- Requires teammates to die in sensible places
- Requires protection from the rest of the team
- Once a teammate dies enemy team can and will hard engage due to the advantage.
- You have to stop healing to rezz that person which can result in another death of a teammate or your own
- There is no difference between a bronze mercy rez count and a GM mercy rezz count.
- Rezz IS powerful and therefore should be earned, not given every 30 seconds
- Apart from killing mercy a boop by dva rein pharah lucio etc etc can simply cancel her rezz without refund
Valkyrie:
- Now gives her flight. She never had her own flying so why put so much value in it acting like we cant live without it?
- You can stay on the floor where you can get attacked by 80% of the heroes or you can fly up to the sky where you will get highnooned or tac visored. (Granted idk what ranks you play, but in diamond + flying high up just gets you killed)
- Now enhances her basic kit and splits her healing to all teammates in range. This incentivizes teammates stacking and opening oportunities for enemies to aoe ult them.
- The healing from said beams is 60 hps. Every tank and dps hero’s normal attacks can outdamage this. You dont even have to focus mercy to completely negate her ult.
- You are better off using it to engage. This is true, but as soon as ONE enemy pulls an offensive ult, valkyrie loses the entire value. You can’t keep teammates alive through that and you certainly can’t help to mitigate the impact of that ult.
Mercy was reworked for 3 reasons (as explained by jeff):
- Hiding: whilst the old mercy hid exclusively during their ult (a minority of mercy players actually), the new mercy hides every time she rezzes or casts valk (unless you play in a potato league where even 3 hitscans cant take you out of the sky).
- Mercy stopped healing during this time: Now she has to stop healing everytime she attempts to rezz a teammate. This leaves your team low of a main healer and countless times have i experienced or seen this happen to my teams and enemy teams.
- It is “unfun” to play against: subjective reason. As a support main i find tracer and winston unfun to play against. So what? If we can use “unfun” as a reason to nerf something then i can use “unfun” as a reason to buff it.
As you can see above, it is obvious that the goals for the rework all failed and did the opposite.
Its good that there are people out there who enjoy the new mercy. It is good that they give feedback and say what they like aboit it. But instead of taking a hero that has existed since launch and rework her so drastically, blizz could have implemented those ideas into a new hero and given mass rezz a LOS.
Your claims that huge amounts of people are happy with her rework can be proven wrong by those statistics you hold so dear.
Current mercy has less pickrate than mercy 1.0 even though you see her in owl and new players joined the game since the rework. That should be a very big indication as to who really is happy with her rework, because as it stands, the majority are not. This isn’t even my personal bias or opinion, this is a fact.
The problem i and many others have isn’t about wanting her to be OP or “unfun” to play against.
The problem i personally have is that i find being a sitting duck and giving up my whole purpose (healing and mobility) for a rezz that is so easily counteres a bad game design.
The other problem i have is that an ultimate is meant to have a “wow” effect. It is used to win fights or to save teammates (support ults mainly) and be unique. Mercy just doesnt have that effect. Her ult gives her a spectator mode and her 60 hps beam spreads onto more allies. That is neither impressive or helpful. It is bland, requires 0 target priority, 0 decision making and any other ult could do it better. I could initiate with a moira E + ult or an ana offensive nade + ult and completely change the agression in that fight. So why would anyone ever want to pick mercy? Shes bad at defending her team and any other supp can engage much better and safer with their teammates than her.
So where does that leave her? In a bad spot.
As we can all agree, “fun” and “unfun” are subjective. But you cant change things for dps players feeling one way, yet refuse to appeal to the feelings of other roles (which as I stated earlier is the majority of mercy players that quit playing her between 1.0 and the current interation.
and the last one is the most detailed one, famous perk of Titanium
Some of you might have seen this coming…
Hi!
I’m making this post to spell out exactly what I hate about the current iteration of Mercy, being a former Mercy main. Technically, this is part three of this thread, but because it is the first version of this thread on the new forums, I conveniently decided not to add that to the title for maximum clickbaitiness (that’s a word now). For those of you who did not see the two previous threads when they were on the old forums, here they are:
https://us.battle.net/forums/en/overwatch/topic/20760797128#post-1
https://us.battle.net/forums/en/overwatch/topic/20760708489#post-1
Don’t worry! This thread doesn’t appear to be as long as either of those two threads, but that’s only because I’ve started using the “hide details” function.
Example (click me!)
Yay!
Also unlike those previous two posts, I will be saving the “Developer Comments” section (the fun one) for after I have explained purely the current situation and the problems therein.
Who’s ready for some reading?
Resurrect
Functionality:
Resurrect is an ultimate that was forced into the slot of a basic ability.
In order to make an ultimate fit as a basic ability, absurd exceptions needed to be made to reduce its power level, or in our case, its potential to have any impact. To accomplish this, the following changes were applied:
30 second cooldown, no exceptions.
Single target.
5 meter range.
LoS/direct FoV requirement.
1.75 second cast time.
75% movement speed reduction while casting.
Abilities and attacks are disabled while casting.
The developers clearly had the goal in mind to balance Resurrect as a basic ability. For that goal, these changes were needed. The method to reach that goal was fine; the goal of forcing an ultimate into a basic ability was comically stupid.
Resurrect is now the most situational non-ultimate in the game with the longest cooldown duration out of all basic abilities. However, it is still powerful. Why? Because it’s an ultimate.
As a result of these changes, Resurrect feels less like something a player would want to consider an “asset” and more like something a player would consider a chore. It’s anticlimactic, and it interrupts the otherwise smooth mobility-based flow of Mercy’s kit with a standstill ability. Rather than jumping at the opportunity to use it, the player is left with more of a great-one-of-my-allies-got-themselves-killed-and-now-I-need-to-handicap-myself-to-save-their-sorry-butt feeling. After pulling off a successful Resurrection, the player is often left wondering why the hell they just forced themselves through that to recover an ally from their own mistakes. It simply feels bad to use.
However, using Resurrect often is practically a requirement, as it is clearly the best way to play Mercy. The problem is that the best way to play Mercy in regards to this ability is also the least fun way to play Mercy.
Cooldown Vs. Charge:
When Resurrect was an ultimate, it had a fluid cooldown that depended upon the performance of the player. If the player was a Mercy god, they would have their ultimate up in 31 seconds or potentially less; if the player was a vegetable, they would have it in 5 minutes and 25 seconds.
Because Resurrect was often one of two or fewer ultimates on the team designed to counter four or more ultimates on the enemy team, there was a consistent need to charge it as quickly as possible after its previous use. Players would play more aggressively, making choices that would be considered too risky to execute under normal circumstances, to secure that last 10-20% ultimate charge just before the teamfight broke out. They might overextend to heal an ally they would otherwise force to come to them to receive healing; they might draw their pistol and lay down some fire of their own, exposing themselves to enemy fire in return; they might stop healing a high-priority target to quickly amplify a target about to deal a lot of burst damage. A Mercy who did not have Resurrect in their possession before a teamfight would rush to charge it, taking calculated risks to do so. By taking these risks, the player receives that same rush of excitement felt on other heroes when they take risks of their own.
This incentive to make these hazardous plays increased the skill ceiling of Mercy’s base kit, as the capacity to get in and out of a dangerous situation that would otherwise be impractical to enter is now rewarded. Playing Mercy became a game of balancing risk and returns.
When the player took these risks and came out on top, they were rewarded in the form of a Resurrect and a feeling of accomplishment. Skilled Mercy players would have their ultimate available more often than Mercy players of lower skill, and those players who were not so successful had something to strive toward throughout their normal playstyle. Mercy players could take pride in how often Resurrect was an available asset to them, as they knew that it had been earned by their own performance.
Resurrect currently functions on a static 30 second cooldown. It cannot be earned. There is no reason to play aggressively like there was before; there is no return for placing yourself in jeopardy. If there is no reason to do something, and there is good reason to not do that same something, then the best choice is always to not do that something.
Why risk getting yourself killed and losing the fight because of it when you would be just as effective without taking that risk?
Mercy’s gameplay isn’t about balancing risk and reward anymore. It’s about avoiding risk altogether and at all costs, removing yourself from the fight as much as possible to do so. The aggressive play is not there anymore and neither is the rush from it.
Every game is a constant cycle of reversing the first pick in a fight (for reasons I will get to in the next section), not having Resurrect if/when it is needed during the following fight, and watching it become available between engagements. It is upsetting to not have Resurrect when it is needed, completely incapable of accelerating its cooldown process, and it feels cheesy and borderline insulting to have Resurrect become available again after it is way too late for it to be useful.
“I don’t have another Resurrect for this fight, but don’t worry guys; I’ll have it immediately after we all respawn.”
Or
“I just love participation awards. There’s nothing better than receiving my most game-changing ability shortly after getting my [gluteus maximus] handed to me.”
Also a consequence of the static cooldown on Resurrect, the availability difference of Resurrect between good Mercy players and bad Mercy players is nonexistent, therefore lowering the skill ceiling. There is no longer pride taken in how many Resurrections a player can charge because that’s not something a player can take pride in anymore.
Thought Process:
I often saw (and still do see) non-Mercy players making remarks along the lines of “Now Mercy players have to think before using Resurrect” in response to objections to the cast time on Resurrect.
What a joke.
Sure, you need to think about Resurrect, but only as much as you need to think before crossing a neighborhood street. Look left. Now look right. Any cars coming? Yes/No. The answer is that clear.
The part of the current Resurrect that requires the most thought is remembering to look both ways before crossing. Remembering to check and see if it’s safe to use Resurrect is more difficult than actually checking to see if it is safe enough to use Resurrect. There is no grey area; it’s either safe, or it’s not.
If we were to take that same analogy and make it relevant to Resurrect when it was an ultimate, it would be an intersection of two different freeways that the player is trying to cross diagonally without the presence of traffic lights or speed limits. The people driving the cars have no regards for pedestrians, and the player is simultaneously trying to prove trigonometric identities while crossing.
Does it seem like I’m going off on a tangent to respond to a hilarious misconception? I’m not. Part of the fun of Mercy 1.x was not only balancing risk and reward to earn Resurrect, but also to the mind game that came with trying to use it to its maximum potential.
Resurrect as an ultimate had enormous variation in its value. This value was never tied to one specific thing, requiring that the Mercy take in the entire situation as a whole to accurately predict the significance of the hypothetical Resurrect. Numbers weren’t everything. A five-man Resurrect could be useless or potentially detrimental if the team is down right in front of spawn or separated by walls in the midst of the enemy team. Conversely, a single-target Resurrection could rapidly swing a losing battle into a victory if the target is in a good position and/or has their ultimate ready.
In the original version of this thread, I constructed a single hypothetical scenario to illustrate what was considered when determining if and how to use Resurrect as an ultimate. I could have simply copy/pasted that here, but because I have a lot of spare time, I decided to elaborate much more than I did previously and go further into specifics for different scenarios. However, if you want the more compressed version you can see it here:
The short (ish) version
For those of you who have a surprising amount of patience and spare time:
The slightly less short (ish) version
Resurrect as an ultimate had huge variation in value. On a scale from 0-10 as to how effective abilities can be, Resurrect had a range of -5 to 11 and was never predefined in value. There was never a single optimal time to use Resurrect as an ultimate.
In contrast, Resurrect as a single-target basic ability will always have an optimal time of usage. It’s rigid cooldown and its lack of flexibility due to reduced range, single-target mechanic, and cast time, close the system down to whether or not it is possible to revive the target and whether or not there is a point in doing so.
Resurrect as a basic ability will always be most effective when used to negate an early-fight pick. Mercy no longer has the capacity to reverse the tide of the battle once one side has gained a clear advantage, so the best thing she can do is to prevent the scales from tipping too far in the enemy’s direction to begin with. Not only does a single-target Resurrect lose value as the fight goes on, but it also becomes more risky to attempt to revive targets as the fight grows older. More allies down means a lower chance of successful reversal and less protection to attempt any reversal. Thus, it is always best to reverse a kill as early as possible. This prevents the enemy team from snowballing an advantage and minimizes risk; yet another way that the game of balancing risk versus reward has been tossed out the window and replaced with minimizing risk whenever possible.
The thought currently required for Resurrect is simply checking a few parameters. It has no regards for how those parameters interact with one another, and it doesn’t require knowledge of nearly the amount of parameters that mass-rez did.
For example, the player doesn’t need to track enemy ultimates anymore. They can if they really want to, but it doesn’t impact their playstyle at all. There’s nothing they can do to stop or mitigate enemy ultimates, so why bother worrying about it?
When it comes to using Resurrect as an ability, there is only one question to consider:
Will attempting to revive the ally in question get myself or the ally killed?
It is no longer a question of how could the player best use Resurrect, it is now a question of if the player can use Resurrect at all; the rest is already decided.
The awareness of an experienced Mercy pre-rework is easily capable of exceeding the capacity at which awareness stops being valuable for the new Mercy. The skill ceiling for awareness is drastically lower than it used to be, and that skill ceiling was never expanded anywhere else to compensate.
The mind game and the sense of accomplishment that came with winning that game is gone. Now there’s just looking both ways before crossing the street.
Valkyrie
Functionality:
Valkyrie is what you get when you take a bunch of existing abilities/ultimates, cram them into a single ability, and try to balance it as an ultimate.
We have Pharah’s flight but better, an off-brand Transcendence that was bought from Walmart (or the aura of a very hyperactive Lucio, depending upon how you look at it) that comes with a very long selfie stick, and a discount Supercharger minus the Orisa. Reinhardt’s ammo capacity was slapped onto Mercy’s pistol, and poof! We have Valkyrie.
Except… it’s kind of a… bad ultimate…
It’s a team-wide 60 HPS or a team-wide 30% damage boost or a 100 constant DPS with her pistol. Comparing this to other ultimates…
Transcendence heals all allies within its radius at a rate of 300 health/second. It makes Zenyatta invincible and the rest of his team basically immortal outside of a few specific attacks and abilities. Valkyrie allows Mercy to fly away and have uninterrupted health regeneration, and it provides 60 health/second to all allies affected by Mercy’s healing stream. Valkyrie has 1/5th the potency of Transcendence.
Supercharger increases the damage output of all allies within its range by 50%, including Orisa, the one who used the ultimate. Valkyrie increases the damage output of all affected allies by 30%. Mercy is not affected by this amplification, nor is she able to shoot at all, for that matter. Valkyrie is a weaker Supercharger that does not allow the player activating the ability to utilize it themselves.
With how weak Valkyrie is in comparison to other ultimate abilities, it would have a good place as a basic ability with a 2-4 second duration. It would be great as an asset the player has to manage throughout the fight. Makes sense, doesn’t it?
The balancing team decided not to take that route because… reasons?
Instead, they tried to put something that fits just fine as a basic ability into the place of an ultimate; the reverse of what they tried to do with Resurrect.
In order to stretch Valkyrie’s power and make it somewhat-worthy of fitting into the ultimate slot, the balancing team did something very creative:
They made it last for 15 seconds (originally 20 seconds).
https://i.imgur.com/CHoyD6b.gif
This didn’t really succeed in making it more useful, it just made the ability great at doing specific things, like making your team slightly more annoying for the entire teamfight and escaping just about any threat for the entire teamfight. The ultimate is pretty pathetic overall; it isn’t likely to change the outcome of the fight if any other ultimate is involved.
I often see players reply to the complaint that Valkyrie is weak by saying, “It’s weaker than Transcendence, but it charges faster than Transcendence, so it balances out”.
Which I find pretty funny. The statement that Valkyrie charging quickly might balance out Valkyrie’s lack of impact isn’t necessarily wrong; it’s the assumption that Valkyrie charges quickly that is wrong.
Before I run the math, let’s throw a reference into this. Resurrect, when it was an ultimate, already charged slower than Transcendence. I ran the numbers, and you can find them here:
https://us.battle.net/forums/en/overwatch/topic/20758647473#post-1
When Mercy’s ultimate was changed from Resurrect to Valkyrie, it’s charge requirement was increased by 325 charge points, a 20% charge requirement increase.
Let’s grab some data from Overbuff and do some math.
Mercy:
393 damage = 393 charge.
11926 healing = 9540.8 charge (4/5 conversion ratio).
555 damage amplified = 2405 damage dealt by amplified target = 1603.33 charge (2/3 conversion ratio).
3000 passive gain from existing for 10 minutes.
Total charge: 14537.13.
Charge Requirement: 1950.
Ignoring usage delay, that’s 7.45 ultimates/game, assuming each game is 10 minutes long.
Zenyatta:
8644 damage = 8644 charge.
6911 healing - 2089.97 Transcendence healing = 4821.03 non-ult healing = 6363.76 charge (33/25 conversion ratio).
3000 passive gain from existing for 10 minutes.
Total charge: 18007.76.
Charge requirement: 2075.
Ignoring usage delay, that’s 8.68 ultimates/game, assuming each game is 10 minutes long.
Did you notice something that was missing from Mercy’s side? We don’t have values for how much healing/damage/amplification Mercy players are getting while in Valkyrie; the data is generalized. This means that we are including values that should not be included, which means Valkyrie would have an even slower charge rate than the rate that is represented by the above numbers. We already know that Zenyatta gains ultimate faster than Mercy does, but even those numbers above do not fully show how large the gap between the two heroes is.
Not only did inflating the duration of Valkyrie fail to actually solve its lack of impact, but it also caused negative side effects. Explaining those side effects are what the following three sections are for.
The Best Defense:
Is to stay as far away from the fight as possible.
This is the same issue that we are seeing with the risk/reward concept in Mercy’s basic kit. Valkyrie is just as effective when activated and utilized in a dangerous way as it is when utilized in a far safer way. The effectiveness of Valkyrie has no regards for where the player positions themselves as long as their beams can reach their team, and that isn’t much of a restriction considering Mercy’s beams reach up to 30 meters in Valkyrie. A Mercy placing a beam on a target while flying 10 meters above her team contributes just as much as a Mercy placing a beam on that same target while flying 29 meters above and behind her team. The difference is that the Mercy staying closer to her team is at a significantly greater risk of dying to enemy fire than the other Mercy.
As a result, we have the same issue we have with Mercy’s base kit in relation to Resurrect no longer being a chargeable ability; if there is no reason to do something, and there is good reason to not do that same something, then the best choice is always to not do that something. The less risk the player takes, the better.
Because Valkyrie promotes taking as little risk as possible, players take full advantage of Valkyrie’s beam range, disengaging themselves from the fight as much as possible; it’s safer 29 meters away than it is in the fight. Where most ultimates are designed to draw the user into the battle, Valkyrie pushes the player out of it.
War of Attrition:
Valkyrie lacks the sudden impact that other ultimates have to swing the tide of the fight. It grants one team an advantage for the entire fight that can be easily overturned by another ultimate on the opposing team. If the fight is already going somewhat downhill, it has no shock value or sudden impact to negate that tipping.
As a result, Valkyrie is best used early on to grant a team an advantage for most of, if not the entire teamfight. It does not do this by rapidly changing the scales, but by allowing the affected team to slog through more than the opposing team. If no more ultimates are involved, or if they are used very poorly, the fight comes down to a matter of “Which team can take a beating for longer”, a battle that is typically won by the team using Valkyrie. There is no “wow” in Valkyrie. It’s not a playmaking ability.
Tracer can blink behind the enemy’s frontline, stick a Pulse Bomb to an enemy, and blink away as they get a quick single or double kill. That’s exciting.
Zarya can use Graviton Surge and gather the entire enemy team into a single location allowing for a rapid teamwipe. That’s exciting.
Reinhardt can Eathshatter four enemies and instantly swing the tides in his team’s favor. That’s exciting.
Lucio can save his entire team from a series of ultimates by using Sound Barrier. That’s exciting.
Mercy uses Valkyrie and disengages while the rest of her team, mildly stronger than before, pushes ahead. She then stays disengaged for the next 15 seconds. That is utterly unimpressive.
Valkyrie feels incredibly underwhelming as an ultimate. It doesn’t offer much power compared to most other ultimates in the game, and none of that power is left in Mercy’s own hands (unless the player goes full Battle Mercy, in which case they are typically hurting their chances of winning, but I honestly cannot blame them for that with how boring Valkyrie is) because they are too busy being their team’s mobile Shield Generator. There is no way to increase Valkyrie’s effectiveness once the beam is already chaining to all five allies. If any of the following ultimates are used effectively, Mercy is powerless to intervene in a meaningful way to save her teammates:
Rip-Tire.
Rocket Barrage.
Earthshatter.
Configuration: Tank.
Blizzard.
Death Blossom.
Self-Destruct.
Deadeye.
DragonBlade.
EMP.
DragonStrike.
Whole Hog.
Graviton Surge.
Meteor Strike.
Pulse Bomb.
Tactical Visor.
“But she can fly.”
No, seriously, I see this a lot. The most common justification I see for the lack of impact Mercy has on the fight with Valkyrie goes along the lines of “Mercy can fly for 15 seconds, becoming effectively unkillable for that time; stop complaining”.
Sure, Mercy is incredibly hard to kill in Valkyrie (because of the constant regeneration, faster movement speed, and both the capacity and good reason to stay 29 meters away from her team at all times), but that doesn’t really say much. 60 health/second isn’t potent enough to protect teammates from normal focus fire; throw an ultimate into the equation and you can ignore the Mercy entirely, as she isn’t having enough impact to matter at that point. Winston alone is able to negate that rate of healing without even looking directly at his target and ignores barriers to do it. What do you think would happen when the entire enemy team is there as well?
You don’t need to shoot the Mercy. You can ignore her and kill her team without any more resistance than you would encounter while trying to kill a team protected by a Shield Generator. If Zenyatta’s Transcendence only healed for 60 health/second, the fact that he is invulnerable wouldn’t be a concern in the fight; his team would still be killed due to sheer damage. Consequently, Zenyatta mains would have every right to complain about how lackluster their ultimate is.
Valkyrie isn’t decisive. It prolongs the fight in favor of Mercy’s team and fails to provide any source of excitement for the player. The fact that it is underwhelming while it simultaneously pushes the player away from the fight for its duration makes Mercy’s base kit of Guardian Angel, healing, and damage amplifying more entertaining and engaging than using Valkyrie; the exact opposite of what should be happening when a player presses Q.
Skill Ceiling:
To put this bluntly, Valkyrie does just about everything the player normally needs to do for them. To illustrate this, we should to declare a few things.
Mercy’s two main priorities for the entire game are:
Sustain and empower her team.
Keep herself alive.
With these two priorities and the given tools within Mercy’s base kit, the player needs to learn healing prioritization, Guardian Angel discipline, positioning, utilization of damage boost, and awareness.
A brief summary of each:
Healing prioritization is how and when the player uses Mercy’s beams; who they choose to heal under certain circumstances, how well they can juggle their team’s health, who they choose to save in scenarios in which they cannot save everyone. A Mercy with good healing prioritization is more capable of sustaining a team than a Mercy who does not know how to prioritize.
GA discipline is how good the player is at selecting GA targets and controlling their flight. A Mercy with good GA discipline will be able to flow from location to location easily, seeming to fly independently if their allies are in good positions relative to the Mercy. Simultaneously, that Mercy is less likely to fly to allies who are in situations that are too dangerous for the Mercy to survive.
Positioning is self-explanatory. It’s how the Mercy places themselves spatially so they can influence the battlefield while making it difficult for the enemy to hit them. This includes cutting line of sight entirely with the enemy team around corners, taking the high ground or staying in enclosed spaces to allow for more advantageous fighting locations, and peeking around corners to heal teammates by utilizing the 2 second decay time on Mercy’s beams. A Mercy with good positioning is less dependent upon GA discipline, but it is impossible to eliminate the need for GA discipline entirely.
Utilization of damage boost is how often/effectively the player amplifies their team’s damage. Its how well they recognize opportunities to use it and how efficient they are with its timing, allowing for both maximum damage and healing output. For example, a Mercy who knows how to use damage boost effectively will amplify a Roadhog when he hooks a target a split second before he fires his shotgun. This allows the Mercy to help secure a kill without leaving much of a pause between healing allies, granting both herself and the Roadhog more ultimate charge.
Awareness is how well the player identifies threats/opportunities and how well they capitalize on them. Good awareness is needed to use the above skills.
These skills led to a nearly limitless skill ceiling in Mercy’s base kit; there were always ways for the player to improve in any or all of these areas.
With that in mind, let’s consider what Valkyrie does:
Beams now split to connect to all allies within 10 meters at full strength.
Mercy is granted free flight at an increased movement speed.
Beam range is extended to 30 meters.
Mercy now has uninterrupted self-regeneration.
And with that, we have almost entirely removed the need for any of the skills mentioned before.
AoE beams means the player hardly needs to worry about healing prioritization; all allies are already receiving the full benefits of Mercy’s healing at once. Switching targets is both pointless and puts a very slight pause in healing, and isn’t at all necessary unless the team splits up a lot.
GA discipline and actual positioning skill isn’t needed when Mercy can fly wherever she wants at a speed of 9 meters/second. Fly up and away to minimize risk, and stay there for the rest of the fight. Her uninterrupted passive regeneration will cover for any chip damage the enemy manages to deal to her at that distance.
Utilization of damage boost is still somewhat needed, but it no longer requires that the player worry about who they amplify. The only thing the player really needs to consider when using Valkyrie is whether or not they should be using their healing stream or their damage amplification stream.
Awareness is significantly less important in Valkyrie, as there are fewer threats to worry about and Mercy’s beams affect her entire team at once.
If the player is flying at the skybox and healing/amplifying their entire team with a 30 meter long tether, they have reached their maximum capacity for the duration of Valkyrie. No amount of skill is going to increase their effectiveness for the following 14 seconds.
There lies the problem. The player is no longer limited by their own skill, but by the ability itself. The player can be an absolute god when it comes to playing Mercy’s base kit, but as soon as they activate Valkyrie, they have the same influence over the fight as a Gold Mercy who is also using Valkyrie.
Combine this with how underwhelming the ultimate already feels because of how diluted it is over a 15 second duration, and a particular adjective works perfectly to describe how the player feels in this situation:
Useless.
This is why I and many others refer to Valkyrie as a glorified spectator mode. It’s 10% hitting buttons to make a difference in the fight, and 90% watching to see what happens. There is no rush of adrenaline, no “in the zone” moment, no feeling of self-gratification while using Valkyrie to its fullest potential. It’s just watching to see what the team will do.
“I will watch over you!” is a very fitting line for this ultimate. Remove the preposition, and you have Mercy saying exactly what the player will be doing for the next 15 seconds:
“I will watch you!”
Commitment:
This section is pretty straight forward. The activation as Resurrect in Mercy’s 1.x versions meant that Mercy was there for the rest of the fight, regardless as to how bad things might look. Using it effectively required that she be in the middle of the battlefield when it activated, placing her directly in the action. The following fight was typically very intense, and Mercy just expended her greatest asset. The Mercy was both in the position physically and mentally where they were committed to the fight, even if it seemed to be going south.
Valkyrie on the other hand, doesn’t seem like much of an asset, and the player is 29 meters from the fight while it’s active. If things go south…
Meh. Whatever. I’m already halfway back to the spawn location. No point in getting myself killed too.
Valkyrie doesn’t mean “I am here with you until this fight ends one way or another” like Resurrect did. It means “I’ll be over here. Have fun”.
Developer Comments
Reasons for the Rework:
When Mercy’s rework was introduced to the PTR, a Developer Update was released with it:
https://www.youtube.com/watch?v=vDlCqJ1tD3M&t=2s
Between 0:39 and 2:12 in that video, we are given two reasons for the rework which come down to “hide and rez” and “it wasn’t fun to play against”. Let’s start with the “hide and rez” assertion.
There are two ways to interpret what Jeff Kaplan said in that video regarding “hide and rez”. One way is that he is suggesting that Mercy players were routinely hiding as soon as they had their ultimate fully charged, which he disliked. The other interpretation is that Jeff didn’t want a main healer to “stop healing for some period of time”. Both interpretations are poorly thought out, and that lack of thoroughness has led to both concepts reappearing through the successive patches to Mercy following the rework.
Addressing the first one… Partially because I am feeling a little bit lazy at this time, partially because I stated it beautifully back on August 12th, 2017, I am going to quote myself from the old forums when I discussed “hide and rez”:
“It’s just hide and rez.”
This quote illustrates that the person saying it has no idea what they are talking about. No, it’s not an oversimplification, it’s just plain wrong.
“Hide and rez” is a great strategy… assuming your goal is to get wiped after the resurrection. Hiding turns the fight into a 5v6 with a main healer down. Any competent team would be able to walk through your team without expending ultimates, except to counter any ultimates expended by your team. The enemy team already has the positioning advantage and the first shot after the resurrection. “Hide and rez” would also give them the advantage of more ultimate abilities. Doing so sets your team up for failure.
A good Mercy sustains her team until they can no longer be sustained, or until she can no longer do so safely. By doing this, she allows the team to bait more ultimates before dying, giving your team the ultimate ability advantage after the resurrection.
A team playing against a hiding Mercy would have a significantly easier time dealing with the opposing team, as Mercy is putting her own team at a disadvantage. It wouldn’t even come down to being aware enough to consciously notice the 5v6 (although most players should be able to recognize a 5v6 when they see one), but a matter of knowing how much force the team needs to apply to overcome a given resistance; if the enemy is crumbling, don’t expend limited resources to push a structure that will fall on its own.
Because the opposing team is already at a numbers disadvantage in the initial fight, pushing into them without using any ultimates, except to counter ultimates expended by the enemy, will be sufficient for eliminating the opposition. This further leads to more loaded ultimates, as killing 4-5 enemies in a 2-2-2 composition is roughly equivalent to 1500 charge in HP. That is also excluding additional charge gained through allied healing and allied damage through enemy healing. Combine this with the absence of a need to expend ultimates, and the team with the hiding Mercy is revived looking down the barrel of an incredibly large gun, has no time to draw their own, and is in a poor position to capitalize on it even if they did have the time to draw their own.
As a result, hiding prematurely was detrimental to the team’s chances of winning the fight in the long term, even if it was more risky in the short term. It was a misuse of an ultimate.
To add some perspective to this, using “hide and rez” as a reason to remove Resurrect as an ultimate is about the same as using the fact that some Pharah players Barrage themselves on occasion as a reason to remove Rocket Barrage.
By this interpretation of Jeff Kaplan’s words, Blizzard’s intent was to prevent Mercy from leaving the fight, keeping her engaged. Rather than giving more reason to stay in the fight through modifications to Resurrect as an ultimate and the introduction of a decent E ability, the balance team decided to remove Resurrect as an ultimate entirely, and here we are.
Did someone say Valkyrie?
If the intention was to keep Mercy in the fight, why was her ultimate, which punished hiding prematurely and rewarded active play, replaced with an ultimate that rewards staying as far from the battle as possible?
According to this interpretation of Jeff’s words, the developers’ statement is, “We didn’t like how some Mercy players would leave the fight before using their ultimate…”. This statement is then finished by the patch history with, “…so we replaced the previous ultimate with one that is best utilized by leaving the fight”.
Let’s examine the second interpretation.
“We think it’s wrong to tell a main-healing character to go off and hide somewhere and stop healing for some period of time.”
1:32 - 1:42 of that same developer update.
The bold section is the one I am focusing on. Let’s pretend that the first interpretation is incorrect, and assume that Jeff Kaplan doesn’t want a hero to stop doing their main job for any period of time. In this case, the assertion may have some merit to it, as there was often a 3-5 second break in healing before Resurrections. This happened for two reasons, both of which came down to practicality:
60 health/second will not save the team from the incoming enemy ultimates.
Mercy’s healing/amplification beams are obvious, and will lead the enemy straight towards her.
The would often result in the Mercy player staying further back or taking cover, possibly substituting healing/amplifying with whatever damage they could deal with their pistol. She would then use Resurrect and finish off or severely weaken a target they shot at before the Resurrection. In these scenarios, there is a short duration in which not doing Mercy’s primary job was the best way to use her.
That’s how it looks in a vacuum.
Look beyond just Mercy, and most heroes often perform very similar maneuvers to reach the same goal. Some examples of this are Rocket Barrage and Death Blossom, in which the player stops shooting at the enemy (their primary job) to reposition, obscure their position, and gain the advantage of surprise when they use their ultimate. This then begs the question: Why weren’t these ultimates changed for the same reason Mercy’s was changed?
The stupidity doesn’t stop there. We once again have a statement that identifies a perceived problem and proceeds to contradict itself through the actions of the developers:
Developers: “We didn’t like how Mercy would stop healing for a short duration before using Resurrect…”
Patch notes: “…so we removed Mercy’s ability to heal for an additional 1.75 seconds leading up to Resurrect’s activation.”
If the developers wanted Mercy players to heal more leading up to a Resurrection, why did they make it physically impossible for her to do so?
One interpretation of this argument brings us an assertion built on ineffective use of an ultimate as a reason to change the ability; an assertion that appears to have been said once and then disregarded with the following patches. The other interpretation yields an assertion that is a double-standard that has also been disregarded in the following patches.
Let’s look at the second provided reason for the rework.
“…it’s pretty disheartening to have Mercy just erase that moment with a full-team rez.”
Yeah, I get that it can be disheartening to have a near teamwipe negated, but do you know what else sucks? Getting wiped.
That’s how PvP games work; if one side is feeling pretty good, chances are that the other side is feeling pretty bad. Removing any one ability because “it was disheartening to play against” is as illogical as removing any or every ability because “it was disheartening to play against”.
If it is not a legitimate balance concern, meaning it is not oppressively powerful (which Mercy and Resurrect were not), then how it feels to play against is irrelevant, as that is treading into territory that is clearly a double standard.
How do you react when your team gets wiped by a Dragonblade? Earthshatter? Tactical Visor? Death Blossom? Rocket Barrage? Rip-Tire? Self-Destruct? Graviton Surge?
Do you squeal with joy? Do you feel all warm and fuzzy inside? Do you attain a sense of accomplishment?
No. For all of these scenarios, you likely feel disappointed, or possibly even angry at yourself or your team for how the fight went. The same emotions are felt by the attacking team when support ultimates are used to negate these same plays; Resurrect was no exception to this pool of ultimates, nor was it exceptionally potent in arising these emotions.
If it is fine for Resurrect to be removed as an ultimate because of this reason, what reason is there to rationalize the existence of any other impactful ultimate? Those are also disheartening to play against.
Post-Reveal Contradictions, Disconnects, and Failures:
I’m going to pick apart some of the other developer comments on Mercy to show just how far the developers backtracked from their original claims.
Developer Comments: September 19th, 2017 (initial rework release):
… This version turns Resurrect into a single target ability. It’s still an important part of Mercy’s kit, but plays much better for both Mercy players and her enemies. Valkyrie, her new Ultimate, gives her the opportunity for big game-making plays and opens a number of new options for her.
The bold parts are the important parts. Looking at the first section of bold text made me want to both laugh and cry at the same time, so I just kind of stared at it awkwardly for about 5 seconds before I resumed typing.
Would I rather have Resurrect as a chargeable, instant-cast, AoE multi-target ability, or would I rather have Resurrect on a static cooldown with a cast time and lockdown movement, further combined with a shorter range and single-target capacity?
This question is the equivalent to asking:
Would I rather immerse myself in an ongoing mind game for both charging and using Resurrect with huge variation in impact, have the capacity to swing the tide of the fight, and have a feeling of self-accomplishment when I use Resurrect well; or would I rather know if/how to use Resurrect by glancing at the situation, be constantly annoyed by the availability of an ability with the longest unchanging cooldown in the game, be subject to becoming a stationary, helpless target every time I activate the ability, and be utterly underwhelmed when I successfully pull of a Resurrection?
That’s a lot of text for a single question, so let’s simplify that:
Would I rather enjoy using Resurrect, or would I rather not?
The answer should be pretty clear. An ability that is comparably less powerful, unengaging, and inflicts negative status effects on the player upon use is far worse for the player than one that is or does none of those things, even if the alternative has a lower uptime.
Resurrect does not play better for the Mercy player. It only plays better for her enemies.
“Valkyrie, her new Ultimate, gives her the opportunity for big game-making plays and opens a number of new options for her.”
I am going to leave this quote for a second, as I want to take these contradictions and failures in chronological order.
On November 3rd, Jeff Kaplan was interviewed on the topics of Moira, Mercy, and in-game toxicity:
https://venturebeat.com/2017/11/03/overwatch-lead-jeff-kaplan-on-moira-mercys-troubles-and-fixing-toxicity/
In that interview, he said the following:
“We want the top two things you notice about Mercy to be, “Oh my God, she’s an amazing throughput healer,” and “Wow, look at that mobility, she’s just flowing back and forth through the map.” And we don’t want her to be the resurrect bot that’s just erasing kills.”
That same month, Mercy received a cast time on Resurrect with a 75% movement speed penalty and an inability use to attacks or abilities, including Guardian Angel.
If you wanted Mercy to be about mobility, why was your first order of business after saying that to apply a standstill function to one of her basic abilities?
Let’s see how the healing part played out…
Average healing/game as of June 28th, 2017 (pre-rework): 11905.
Average healing/game as of August 12, 2017 (pre-rework): 11912.
Average healing/game as of March 21st, 2018 (post-rework): 11926.
Mercy’s average healing output hasn’t increased by any significant amount through this rework. This begs the question: How does that happen when Mercy now has an ultimate that quintuples her healing output?
Could it be because the developers also failed to provide a reason for the Mercy to stay in fights she no longer has any influence in? The same reason Mercy players took cover for the handful of seconds leading up to a Resurrection, but now there is no Resurrection to use? So they just walk away?
As for the “And we don’t want her to be the resurrect bot that’s just erasing kills” part, you have done exactly that with the current Mercy. She’s still Resurrecting an average of 1.5 more players/game than she was before the rework, and the lack of thought or variation in Resurrect usage screams “bot”.
Returning to that earlier quote from the patch of September 19th, 2017:
“Valkyrie, her new Ultimate, gives her the opportunity for big game-making plays and opens a number of new options for her.”
This quote seemed to be further reinforced in the developer comments of the November 16th patch:
“We feel that Mercy’s recent rework has been successful, but her Resurrect ability still feels too strong and frustrating to play against. Now that it has a cast time, enemies are more able to counter the ability. However, Resurrect will cast instantly when Valkyrie is active. This should make her feel powerful when she transforms on the battlefield.”
According to these developer notes, the balancing team seemed interested in at least keeping a little bit of playmaking capacity in Valkyrie.
Haha, nope.
January 30th, 2018:
Valkyrie no longer provides a charge of Resurrect upon activation.
Valkyrie no longer removes Resurrect’s cast time.
Valkyrie’s duration reduced by 15 seconds.
Speed increase from Guardian Angel while in Valkyrie decreased by 50%.
Developer comments:
“Mercy’s recent Resurrect changes have helped in allowing enemies to have more counter play in dealing with her, but she was able to use Resurrect through Valkyrie enough to largely mitigate the impact of the previous changes. Additionally, we’re toning back the amount of mobility Valkyrie provides through Guardian Angel and reducing its duration to overall reduce the power of this ability.”
So… When you say she was mitigating the impact of the previous changes, do you mean that Mercy players were still making plays with her?
You know, the thing you supposedly wanted Valkyrie to be capable of? And now you’re removing it.
Let’s revisit those two other quotes.
“Valkyrie, her new Ultimate, gives her the opportunity for big game-making plays and opens a number of new options for her.”
“This should make her feel powerful when she transforms on the battlefield.”
Is she capable of making game-making plays with Valkyrie? No.
Does she have a number of new options? Sure, but one is clearly better than the rest; fly away and utilize the maximum range of her beams. If one option is always better than the other ones, there’s not much point in even considering the other possibilities as “options”.
Does she feel powerful when she transforms? Powerful enough to watch her team die from the skybox. No.
January 25th, 2017:
After months of negative feedback on the Overwatch Forums and at least 6 megathreads on the topic of Mercy, we received a developer update, some of which addressed Mercy: https://www.youtube.com/watch?v=5P1Md792fF8
Jeff Kaplan spends his time addressing Mercy by looking at only how “balanced” she is, ignoring what most of the feedback was complaining about in the first place.
“If we tone her down too much, we will bring her back”
6:39 - 6:43
We don’t care about being “meta”. We care about the fact that you have taken Mercy from us, and replaced her with something that isn’t Mercy. I would be content with being in F-tier so long as I enjoy playing my favorite character. If Mercy is brokenly overpowered but not at all engaging or entertaining to play, I won’t play her because I won’t enjoy doing so.
Mercy’s balance state means little to me in comparison to how fun Mercy is to play.
On February 1st, 2018, Jeff Kaplan commented in the existing Mercy megathread by saying the following:
“Thanks to everyone for taking the time to write up thoughtful feedback here. We’re reading the responses daily.”
This raised hopes. Maybe Blizzard would actually acknowledge the concerns we have, something they have failed to do so far?
Nope.
One week later, Jeff Kaplan appeared in some other thread (rather than the megathread, which would have made sense) to say this:
"We have no plans to revert Mercy. We also feel like she’s not in a horrible place or unplayable.
It’s still to be determined if she is exactly where she should be because it has been too soon and the dust needs to settle. Her playtime in QP and Comp is still incredibly high. Her winrate is still above 50% but more in line with what we’d expect.
But I’d like to put the notion that Mercy is going to be reverted to rest.
Also, we don’t agree with the statement that all supports are weak. Support heroes are extremely powerful and impactful in OW."
It’s not the fact that he basically said “We don’t want to revert Mercy”, that pisses me off, it’s that fact that once again, despite them “reading the responses daily”, they still refuse to acknowledge what our concerns are (or maybe they still have no idea what they are), and proceed to pretend that it is purely a balance issue. It is either ignorance or arrogance, and neither seems to be curable.
And now we have radio silence from the developers on this topic and another megathread that is sure to be ignored, like the past 7+ megathreads.
Potential Solutions
I am literally copy/pasting this entire section from one of my previous posts, “Overwrite - Let’s Fix Everything: Part 2”.
https://us.forums.blizzard.com/en/overwatch/t/overwrite-lets-fix-everything-part-2/4520
Yes, that was a shameless plug. Want something?
Please note that the following text was typed up a little over a month ago, so any statistics included may not be exact for today’s numbers.
CTRL+V in 3… 2… 1…
Build 1:
Resurrect: Removed as a usable ability unless Valkyrie is active. One again sets Guardian Angel’s cooldown to 0 upon use. Does not have a cast time.
Resurrect needs to be locked behind an ultimate if it is not an ultimate by itself. It is impossible to balance Resurrect and simultaneously make it feel good to use if it is locked behind a basic cooldown.
Double Jump: By pressing the jump key twice in rapid succession, the player gains extra lift, the animation showing Mercy’s wings activating to give her an altitude boost. This can be used to establish LoS to targets on high ground, or get a better view of allies who are currently obscured by closer allies. It cannot be used more than once since touching the ground.
This is mainly out of preference, but Mercy would feel better if she wasn’t 100% dependant on allies to not be a sitting duck.
Valkyrie 2.0:
Duration reduced to 8 seconds.
Free flight removed.
Current beam setup removed.
Regeneration passive during Valkyrie removed.
GA range during Valkyrie reduced from 50 meters to 35 meters (30 is normal GA range).
Resurrect becomes available when Valkyrie is activated. Upon using it, it has a 3 second cooldown, and will continue to run on 3 second cooldowns for the rest of the ultimate.
Once the ultimate ends, if Resurrect is not on cooldown, the player has 6 seconds to use it before it is no longer usable. If it is on cooldown, the ability completes its cooldown and then has 5 seconds to be used before becoming unavailable.
New passive while Valkyrie is active- Angelic Presence: All allies within 8 meters of Mercy including herself receive an uninterrupted 10 health per second.
Mercy no longer points her staff at her allies and engages a healing stream, she now swings her staff in an upward arc at a rate of once per second whilst using one of her streams (damage boost or healing). Each swing causes an eight-meter cone AoE effect of the current beam, but amplified because this is an ultimate.
If Mercy’s healing stream is activated when she swings, all allies within the AoE receive a burst 100 HP. If her damage stream is activated when she swings, all allies within the AoE receive a 60% increase in damage for 1 second.
Pistol damage during Valkyrie increased from 20 to 25.
Mercy’s base movement speed and Angelic Descent horizontal speed increased by 0.6 to 6.1 (5.5 is the base movement speed for all heroes except Genji and Tracer, 7.1 is Lucio’s speed aura).
This forces Mercy to be in the fight, as Mercy has neither the free flight, nor a 30 meter beam range. Being this close to the fight will jeopardize the player, yet it still open lots of opportunities for the player to feel heroic. The reduced duration and increased stats makes Valkyrie more potent but for a shorter duration and less annoying to play against, as Mercy is now directly in the fight rather than 30 meters away. Because Mercy is now forced to be in the fight, commitment is required to use Valkyrie, and the player must use it carefully because of the reduced range and duration. Target prioritization will need to be considered in the event that not all players can be healed in a single arc of Mercy’s staff.
Variant 1:
Rather than a Double Jump ability, 3 seconds of free flight at base movement speed are granted to the player upon hitting the jump key twice in rapid succession. This ability has a 7 second cooldown, which begins once its 3 second duration has ended. This results in a maximum uptime of 30%. Can be used in Valkyrie.
This is mainly to appease the players who enjoyed the free flight granted by Valkyrie and want to keep it to some degree. Note that none of the other bonuses from the current version of Valkyrie (chain beams, range increase, etc.) apply to this ability.
Variant 2:
Free flight is added to Valkyrie.
This variant was created for the same reason Variant 1 was created; to appease the players who enjoyed free flight. I, personally, would not prefer this variant, but it would still be miles better than Mercy’s current iteration.
Build 2:
Valkyrie:
Duration reduced to 10 seconds.
All outputs (healing, damage amplification, pistol damage) increased by 50%, Meaning: Healing → 90 HPS, damage boost → 45% increase, pistol → 30 damage.
Primary beam range reduced from 30 meters to 20 meters.
This makes Valkyrie more potent with a shorter duration, making it feel more impactful. The reduced beam range is to prevent players from spending the entire fight in the skybox, and makes it feel a little more fair to play against.
Resurrect:
Players can now reduce the cooldown time for Resurrect by healing/dealing damage/amplifying damage.
Cooldown is doubled or tripled.
Movement penalty upon activation reduced from 75% to 50%.
Mercy can now heal, damage boost, and shoot while reviving.
If this change is executed properly, this could overall be a cooldown nerf to Resurrect without feeling like it. The cast time was modified in order to make Mercy feel less helpless upon using Resurrect.
Variant 1:
Duration of Valkyrie reduced to 8 seconds, outputs increased by 60%: 96 HPS, 48% amplification, 32 pistol damage.
This is basically the same as the above version but even shorter and more potent.
Variant 2:
Valkyrie has a 10 second duration, primary beam target receives 120 HPS/60% damage increase, secondary beams apply 80 HPS/40% damage increase.
The goal for this was to create a need to prioritize targets. To do this, the strength of the primary beam was increased while the strength of the secondary beams were decreased.
Variant 3:
Valkyrie has an 8 second duration, primary beam target receives 128 HPS/64% damage increase, secondary beams apply 85 HPS/43% damage increase. Mercy’s blaster deals 32 damage.
Variants 1 and 2 mixed together.
Build 3:
Mercy reverted to 1.x.
Guardian Angel:
GA modifications from Mercy 2.x applied.
Resurrect:
Range reduced to from 15 meters to 10 meters.
Line of sight requirement added.
Valkyrie:
Added as an E ability.
4 second duration, 12 second cooldown. Cooldown begins once the ability’s duration has been exhausted, allowing for a 25% uptime at the very most.
Primary beam range only extends to 20 meters, down from 30.
Movement speed reduced from 9 meters/second to 6.5 meters/second.
Guardian Angel range is not extended when Valkyrie is active.
Passive self-regeneration is no longer constant.
A revert is the most definite fix. The line of sight requirement and range decrease were applied to Resurrect for two reasons; one, to compensate for Valkyrie becoming an E ability, and two, to incentivise tempo-resurrections without forcing them. Note that the charge requirement was not increased for the latter of those two reasons.
Variant 1:
Resurrect has a 15 meter range and no line of sight requirement, but can Resurrect a maximum of 3 players at once. If more than 3 players are within range, the 3 closest players to Mercy are revived.
Just an idea. There really isn’t any justification for this idea, and there doesn’t really need to be.
Variant 2:
Valkyrie no longer grants free flight, GA range is once again extended, beam range is again set to 30 meters. A double jump ability is added to Mercy’s kit.
This allows Valkyrie to be used to heal allies that are otherwise unreachable, but does not make Mercy herself unreachable. The double-jump was added to provide Mercy with a little independant mobility.
Variant 3:
Valkyrie’s primary beam applies 80 HPS/40% damage increase, secondary beams apply 53 HPS/27% damage increase.
Valkyrie but with the added requirement of healing prioritization.
Variant 4:
Any combination of Variants 1, 2, and 3.
Have fun.
Build 4:
A build I stole from ReinStein (with permission, so i didn’t actually steal it) and then modified:
Valkyrie:
Removed.
Resurrect:
Is once again Mercy’s ultimate.
Now uses a charge/stack-based system, stores a maximum of 3 stacks. 1320 ultimate charge is required to gain a single stack of Resurrect.
Cast time removed.
Resets GA cooldown upon use.
Otherwise functions like Resurrect does currently.
This fixes the issue that Resurrect is not earned and adds variation to its availability. I didn’t just pull 1320 charge out of my butt; I took the amount of ultimate charge the average competitive Mercy player was earning every game by healing/damaging/amplifying (11562.4), added the passive ultimate gain from existing for 10 minutes (3000 charge) to total 14562.4, and decided I wanted the average Mercy to earn 11 Resurrect charges/game. 14562.4/11 ~ 1320 (rounding to the nearest ten). For reference, Resurrect from Mercy 1.x required 1625 ultimate charge.
New E ability: Alter Stream
Pressing E activates Mercy’s chain beams, which function as they currently do in Valkyrie but without the primary beam range increase. Pressing E again returns the beams to normal.
The strength of Mercy’s beams is decreased, reducing her damage boost amplification to only 10% and her healing to only 20 HPS.
This ability has no cooldown.
This adds more depth to Mercy’s allied prioritization, allowing her to choose between affecting one ally with a potent beam or multiple with weaker beams.
Changes to damage boost in relation to ultimate charge:
Ultimate charge is no longer generated based on how much damage a target amplified by Mercy is dealing, but by how much damage is amplified.
For every 2 damage amplified, Mercy gains 5 ultimate charge points.
There’s a reason for this change. If you are not interested in watching me crunch numbers, I suggest you skip over this part. If you enjoy math like I occasionally do, feel free to stick around.
Currently, the amount of charge Mercy gains from amplifying teammates is determined by the total amount of damage the ally in question is dealing to enemies. Note that this is not the base damage, but the amount of damage the ally is dealing total, after Mercy’s 30% damage increase is factored in. This is then fed through a 2/3 conversion ratio before giving us the final amount of ultimate charge gained through damage amplification. In other words…
If [player currently being amplified by Mercy] deals 200 base damage to [enemy], Mercy’s 30% amplification increases that damage by 60, resulting in a total of 260 damage dealt. This number is then multiplied by 2 and divided by 3 (because reasons, the developers slapped a random conversion ratio on top of this), resulting in a grand total of 173.3333… ultimate charge gained from this endeavor. 60 damage amplified resulted in 173.3333… charge points.
Why the developers made this conversion so unnecessarily complicated is beyond me, but I digress. The reason this is no longer an effective system is because of the proposed E. Why? Let’s compare Mercy’s normal damage boost to the suggested chain boost:
For Mercy’s normal boost, she gains 173.3 charge for 60 damage.
For Mercy’s group boost, let’s assume she is increasing the damage output of three allies, all of whom are dealing 200 damage. With Mercy’s 10% increase, she is increasing the damage of each ally by 20, for a total of 60 damage amplified. However, the targets she is boosting are dealing a total of 660 damage. If we slap this into the same conversions currently in place for Mercy’s damage stream, we get 440 ultimate charge gained; here lies the issue.
Normal: 60 damage amplified = 173.3 charge.
Chained to three allies: 60 damage amplified = 440 charge.
The amount of charge gained is not consistent with the amount of impact Mercy is creating; this is why I very strongly suggest that Mercy’s charge gain from damage boost is determined by how much damage is amplified rather than how much damage the affected allies are dealing.
If we want the current charge rate for Mercy’s beam to remain unchanged while solving the issue, we simply divide the amount of charge gained from the normal scenario by the amount of damage amplified in that same scenario:
173.33…/60 = 2.88…
So, for every 1 damage amplified, Mercy receives 2.88… ult charge. Because Mercy has the potential to gain ult at a faster rate by amplifying/healing more than three targets, however, I figured it would be better for Mercy to gain 2.5 charge/1 damage amplified to counterbalance. Hence the 5 charge for every 2 damage amplified.
Variant 1:
Resurrect stores up to five stacks. The range of Resurrect is increased to 15 meters and all allies within the radius (and within LoS) are Resurrected upon a single use of Resurrect. Mercy receives one second of invulnerability upon using Resurrect, and she can only use Resurrect once every ten seconds. If she uses her ultimate, it is put on a ten second cooldown.
This makes Resurrect feel more epic to use, but still actively incentivizes tempo-resurrections rather than mass-resurrections because of the line-of-sight requirement and limited invulnerability. The cooldown upon using Resurrect is inflicted for two reasons; One, to prevent Mercy players from abusing the invulnerability by chaining Resurrections, and two, to make the Mercy player think carefully about how they use Resurrect. Ten seconds is the same time it takes a player to respawn after death, so a Mercy must consider how they use Resurrect if multiple allies are down at once and some are not reachable.
TL:DRs
WHAT??? Titanium making TL:DR editions of his posts??? Who is this impostor?
Well, since this post just crossed into its 68th page of text and is by far the longest post I have ever created that focuses entirely on a single hero, I think I’ll show Mercy (that was a very intentional pun) to the people who don’t like reading excessively large posts.
Resurrect/Valkyrie TL:DRs:
Mercy has an E on an ult and an ult on an E, resulting in stupid balance decisions to force each into its respective place.
Resurrect feels bad to use and more like a chore rather than an asset.
Resurrect is on a static cooldown when it needs to be chargeable.
Resurrect no longer provides any reason to take risks. The less risk, the better.
The thought process for Resurrect has been simplified to checking for a specific set of parameters rather than how a broader set of parameters interact with each other and what that means in terms of Resurrect.
Valkyrie is underwhelming/weak. It isn’t decisive.
The reward for high risk play in Valkyrie = the reward for low risk play in Valkyrie. 29 meters is the optimal distance from the fight.
The insanely low skill ceiling on Valkyrie compounded with its lack of power results in a sense of helplessness when the team is losing the fight.
Valkyrie requires no commitment to the fight, unlike Resurrect as an ultimate.
Developer Comments TL:DRs:
Hide and rez was a bad strategy, often leading to a second wipe. Changing Resurrect because of poor play is equivalent to changing Rocket Barrage because Pharah’s occasionally kill themselves.
“We didn’t like hide and rez. Now go hide in the skybox with Valkyrie.”
Disengaging for a short duration in preparation for ultimate usage is something most heroes do at some point.
“Mercy should never stop healing. This is why she cannot heal while using Resurrect now.”
“It’s not fun to play against.” Well, I just love being killed by a literal aimbot. Or… you know… anything, really.
“Resurrect now plays better for Mercy players”, except it doesn’t.
“Mercy should be about mobility and healing. This is why she can no longer move while using Resurrect. This is also why her healing numbers have barely risen since before the rework.”
“We don’t want Mercy to be a rez-bot. This is why she now has 1.5 more Resurrects on average than she was getting before the rework and is brain-dead in comparison when it comes to using Resurrect.”
“Valkyrie should be a game-making ability.” Present day Valkyrie says hello.
Developers are ignoring the feedback. “We’re reading responses daily… Don’t worry, we have no idea what the problem is.”
Potential Solutions TL:DRs:
Build 1: Resurrect is only available in Valkyrie. Valkyrie gets overhauled.
Build 2: Resurrect is a mini-ult. Valkyrie is shorter and more potent.
Build 3: Revert Mercy to 1.x, add a discount Valkyrie as an E, do some other things.
Build 4: Resurrect is a single-target ult with multiple stacks. E is a toggle weak chain beams button with no cooldown.
If you have read everything up until this point, you have read 70 pages of text. Go make yourself a sandwich.
2 Likes
Also for reference, the only reason Mercy wasn’t used at higher levels is because “smothering” Dva matrix was still a thing.
So Winston could zap supports with impunity for 4 seconds.
Which is no longer the case.
Sorry if I’m being stupid, but where are you getting the 90,000 post number from?