**Mastery Loadouts**
Due to issues related to the release of Mastery Loadouts, the "free swap" period will be extended.
The new end date will be May 1st.
Due to issues related to the release of Mastery Loadouts, the "free swap" period will be extended.
The new end date will be May 1st.
Phones not affected by bugs? [Edited for Clarity]
mattyben27
Posts: 55 ★
@Kabam Miike in a different thread, you mentioned you know of certain phones that aren't affected by the main bug/bugs that have been affecting the game for the past few months. Can you please share that list? We players have been assuming that the game play issues we've had are from the main bug. If we could see that our phone isn't affected, then we can report new issues/bugs. Thank you
-5
Comments
Other than the specific “Frame Rate and Control Input” issue (due to 3rd party Unity game engine issue) that is exclusive to only iOS.
While other Parry and Dex issues are being analyzed (see their Input Robot named Kabam Tapsalot) as to what could be causing those broader problems. (But don’t think they have said it is just specific devices regarding that).
Separately as well is an Asset Memory Leak that was causing some stuttering and crashing.
All that basically was said in their initial detailed “Input System Update” post.
- Hey everybody, compensation packages should be identical to the last ones with Potions and Revives. We know that this doesn't address each individuals needs, but as we laid out in this post here, there are many factors that lead to us not being able to accurately measure the impact of these issues.
For instance, on this thread alone (and I'm not throwing any shade, just trying to illustrate), I count at least 2 people that are on devices that are not affected by the issues that we're issuing these compensation packages for. This doesn't mean there aren't issues affecting them, but it is not the control input issues.
We're going to keep monitoring the situation and how players are affected, and try and get more accurate, but it is not easy. This is why we're going with generalized packages based on the difference between the "before and after" resource use based on existing content.