**WINTER OF WOE - BONUS OBJECTIVE POINT**
As previously announced, the team will be distributing an additional point toward milestones to anyone who completed the Absorbing Man fight in the first step of the Winter of Woe.
This point will be distributed at a later time as it requires the team to pull and analyze data.
The timeline has not been set, but work has started.
As previously announced, the team will be distributing an additional point toward milestones to anyone who completed the Absorbing Man fight in the first step of the Winter of Woe.
This point will be distributed at a later time as it requires the team to pull and analyze data.
The timeline has not been set, but work has started.
Comments
When a bug benefits the company: "please, send a video showing the issue so we can investigate further"
Yo Mods, this guy broke ToS, he went and download the previous version apk from a 3rd Party site...
They previous version is built on a game engine version right?
They added their own code with SECTIONS for stuff like, new animations but mostly new content right?
NOW! Let's debug, what did they do different?
Did they work on a new version of the game engine? Yes/No
-if Yes
- rollback to previous game engine version
-if No
- inspect newly added code for bugs, slim down the code.
Did they add extra sections of code ? Yes/No
-if Yes:
- Where exactly? Check previously KNOWN reliable code for that section and look for bugs.
- What code exactly? new BALANCE (yeah right) code that might not be active?
- continue debug from here, rollback to previous code, delete EXTRA sections of code, inspect content only sections of code. Bug Found === Bug Fix
-if No
- Option 1: Magic
- Option 2: they are incompetent and can't even debug.
A few weeks ago someone even data mined and saw an option for frame rate settings.
If the unity engine changed, all versions of the game should react the same way. Its a change that Kabam made on their end on this last update.
The part that baffles me is that there are over 2k posts and they claim being unable to replicate the bug.
Using Samsung Galaxy S10+