Xygon ★
Réponses
-
No calendar. No crystals. About half our alliance had them, half doesn’t.
-
Undo this. Communicating that it doesn’t count, then after it matters, saying that it does (partially) is a big deal!
-
This! He has a “MoleGod” moniker, but he was great for specific things, good for everything else. I use KP more, and bring MoleMan when his kit fits the bill. He was a great champ, but it’s not like you saw him on 100% of attack teams.
-
My AQ deaths are going up significantly on day 4/5. This is rough
-
Yup. Making AQ much harder.
-
Literally holding down block today and my character starts walking toward the defender. Never in my many years has that happened. On top of parry and evade that is as bad as it ever was, plus attackers suddenly moving in the wrong direction. I was pleased enough when the beta controls came out. Now it seems as bad as the…
-
Like 1-2 hours earlier than normal. Oops!
-
Are the item compensations going to be daily? I made it through with half of it used. Some used all. Some used none. Not sure the whole week is sustainable with just that one gift.
-
So AW ended, some item use was compensated, enough to cover days 1 and 2 probably, but why is AQ still live?
-
If I parry early, I get it. If I parry later, I get hit. If I evade late, I get a parry instead. Evading Gwen’s unblockable s1 was impossible. 7x5 AQ35, usually itemless. I’m now two revives and three heals into day 1.
-
It's not just parry is off. The timing is off, such that I go to evade, and get a parry instead. Everything timing-wise is just pushed back by about a ms.
-
iPhone 11 Many, happening in every fight.
-
Now why did it double post, and not post as a reply to the thread I was in? Ugh!
-
Because the reward message on the forums wasn’t specific, and it was the most rare reward. I (and at least one other in my alliance) assumed the reward was better based on the description.
-
It’s the most rare reward. I was expecting at least a +5 stone. And I’m not sure what’s meant by “reel” I just got a single random stone
-
This gave me hope to try again. Nope, still down.
-
Some or all? Should I have another officer try?
-
Obviously they're aware, but yes, me too.
-
And it's gone again. Looks like the curse is only staying put for one fight, not two. At least it was consistent for me across the last four fights.
-
And it went again. First fight through, next fight looking at the curse, 2/2 remaining (like it should). Following fight, it's not there any more. So I have to fight without parry on one I had planned to be able to parry through.
-
Reminds me of the Eddie Izzard Engelbert Humperdinck bit
-
I wholly agree here (and I've had this happen twice, too). The idea of sig stones is at least equitable, 20 same-class just gets to move it over to someone else. Or 10-20 generic becomes even more valuable, which a dupe of a s200 should be! Even better would be some blend including significant 6* shards for those that were…
-
And for the devs, this is "Mind's Eye" that is not working.
-
Agreed. Brought killmonger, True Strike is preventing the evade (not ability accuracy modification), but I'm not getting the furies.
-
I'm just glad it's off season. We had three missed placements because of this.
-
I would say it's only abuse if you knew it wasn't supposed to act that way. The awakening gems was obvious. This was not. I had no idea (though a-I didn't get shards every time, and b-I only ran it two or three times, not 98)
-
It is supposed to be run multiple times, but apparently the shards aren't supposed to be on every run. I didn't get it with every run, looks like some did. Because they weren't clear this was not supposed to happen, hopefully there aren't bans this time.
-
Essentially, Kabam already realized that the changes were worth adjusting him. Implemented the changes in 7.5, and they regressed in 7.5.1. Options have already been explored, it's possible to get through him, but it's really more powerful of a combination than designed, post HB adjustments.
-
My dream solution: don't delay, don't restart. Edit the current map realtime to have him with 1 health so we can move on till this regression is fixed.
-
It wasn't on the 7.5.1 list, but it was on the previous lists. Too bad we (all) didn't catch it earlier