**UPDATES TO ENLISTMENT GIFTING EVENT:**
To prevent exploitation, we will prevent new Accounts from being able to Gift enlistment crystals. We will also be taking action on those who are using 3rd Party Sellers, Bots and other farms to gift themselves mass amounts of Enlistment Crystals. Lastly, we will be adding an expiration timer to Enlistment Crystals. All unopened Enlistment Crystals will expire on Oct 18 @ 17:00 UTC. For more information, please see this post: https://forums.playcontestofchampions.com/en/discussion/346104/updates-to-enlistment-gifting-event
To prevent exploitation, we will prevent new Accounts from being able to Gift enlistment crystals. We will also be taking action on those who are using 3rd Party Sellers, Bots and other farms to gift themselves mass amounts of Enlistment Crystals. Lastly, we will be adding an expiration timer to Enlistment Crystals. All unopened Enlistment Crystals will expire on Oct 18 @ 17:00 UTC. For more information, please see this post: https://forums.playcontestofchampions.com/en/discussion/346104/updates-to-enlistment-gifting-event
Comments
Further, the AW and AQ Comp have not changed calculations at all. We started them early, and have kept them going. They're probably a little bit much, considering nobody is using all of those resources, but we're not going to change them now.
Android users, and not just what Kabam has identified as being an IOS issue, have had a sliding window on Parry/Dex timing for a VERY long time now, where it changes some times week to week, but most certainly changes practically every release.
Most of us have just gotten so disenfranchised and tired of always reporting it, we just stopped and gave up.
You also haven't replied to my question: if I understood you are checking data of only those accounts that are affected by the control input issue, but why? Why not others too? We are experiencing the same problems for the same period of time if not even longer, so we should be considered too...
We should get enough to help us complete that content the same way we used to be able to, which would be more than your skewed data shows, and it shouldn't matter if we are on Android or iPhone because bugs negatively affecting our ability to play without taking unnecessary damage cost the same health regardless of device.
I would like to know why an iPhone bug deserves compensation but the Android bugs that have been going on even longer, though granted not for everybody all the time, didn't and apparently according to your comment still don't deserve compensation. Yes, you aren't restricting the current compensation to just iPhone users but Android users deserved compensation before and still now also, especially if you don't fix them by the time you fix the iPhone and presumably stop the meager solo compensation.
Also, can you explain if your comment about trying to figure out people's losses more accurately means you plan to start targeting compensation to only iPhone users since you say you aren't compensating for Android issues now?
I was expecting a nexus plus plus plus for the shear pain and lack of enjoyment in crushing content I can’t appreciate due to data leaks and input drops.
However, it is not. I was honestly a little shocked
In normal circumstances I would be embarrassed admitting that.
However, I’ve been playing this game at a reasonable level for 6 years so know when I’ve made a mistake or been hit because something was “off”.
I lost count the number of times I got clattered because of parry issues. Cosmic spidey was especially bad.
I also used an (in normal circumstances) embarrassing number of revives on my initial clear of 7.3 Kang.
I lost count the amount of times dex failed. I’m going nowhere near Kang until the game is fixed.
For me at least, the solo compensation feels woefully inadequate.
I don’t understand why I’m given compensation for alliance events that constantly expires in overflow… but have to use resources I wouldn’t normally use in solo events but not compensated sufficiently for that
The balance is way off.
I believe you said last month's and this most recent update combined were supposed to fix the memory leak (I think that was it) that could be causing issues for Android that you said might manifest as the input issues and unreliable champ behavior. I don't believe these issues have been resolved (freezing, skipping frames, blocking instead of activating specials even when done when the button is lit up, doing wrong attacks or moving the wrong way, etc.) so I would like to know if that means you guys view your work as done on this issue or if you are still going to try to fix it.
Secondly, the brief update notes indicated a fix for blocking instead of activating the special, but there was no mention of this power bar dimming change. Are we to understand this was the bug fix for that issue? My issue with block happening instead of special activation was never due to the enemy using their special when I tried to activate mine. My issue has been either after I do a combo and activate special I block sometimes instead of when intercepting an enemy attack I get block instead of special. This is not a timing issue on my part because the game has the time to make my champion block when it should instead be a special. Is this supposed to be fixed, are you done with that also by just making the special button and power bar almost disappear or will that still be worked on also?
Put me down for missed parries, missed blocks, stop blocking in the middle of the defender's combo, inability to dash back and my personal favourite, the attacker randomly stopping in heavy attack, whether or not I tried to throw a heavy, and being stuck there until I throw a special, hopefully not into the defender's block so I get countered to the face AND waste my power or I get hit and knocked and released from suspended animation, The best frozen mid heavy champ is Hyperion...he hangs in the air, mid punch and looks great. I have all of those multiple times every day.
Thanks