Potential Delay to v44.1 Launch
We are currently working through some issues that may affect the release window of v44.1. This means that the update may not release on Monday as it usually does. We are working to resolve the issue holding us up as quickly as possible, but will keep you all updated, especially if the delay results in any changes to the content release schedule.
We are currently working through some issues that may affect the release window of v44.1. This means that the update may not release on Monday as it usually does. We are working to resolve the issue holding us up as quickly as possible, but will keep you all updated, especially if the delay results in any changes to the content release schedule.
Options
Comments
If we were good enough to be in tier 5 before the update it would certainly have been nice to know that the war ratings and the tier placement after the upgrade was only based on rating. What this means is you (kabam) changed the sliding scale on what a rating = tier means- you changed the dynamic and did not inform us the rating scale for tier placement was also changing- Bad form Kabam!
Also, the update changes all history data for previous wars- Tier 8 did not give 5star shards- Lame -as now all data is skewed.
Regards,
Backtothegrind
Mmm... didn't they announce that they were adding more tiers at the top and that would move people down?
Or was that supposed to start with seasons and not just the update?
This is what the announcement said:
First off, we’ve broken up the top tier into 3 smaller tiers. Tier 1 will consist of the Top 0.1% of Alliances, while Tier 2 will consist of Alliances that rank in the top 0.2%-0.5%, and Tier 3 will consist of Alliances that place in the top 0.6%-1%.
So, if you log in on the first day of 17.0, and notice your Tier dropped, don’t worry! It’s just that there are now 2 more Tiers at the Top.
knowing the situation, why are you firing off her sp2 after a combo?
you're the one costing yourself units and money.
CM was fixed. same with iron man's sp2 but now it's broken again as well.
the fixes were broken in, i believe, the 16.0 update. kabam seems to have an issue with version control. old bugs seem to have a habit of coming back like the evade+hit bug, the insane reaction time, dormammu's/maestro's super fast reaction/reach.
Unless you're using her on all or nothing nodes, they all seem like avoidable situations. Stop putting yourself in that situation and you'll stop costing yourself units and money.
I was pointing out that the problems have reached a point where we no longer discuss new features but instead of keep going on about the problems that it should be concerning. Outside of the forums, there's a growing unrest that is echoing the unrest that happened then.
well then. carry on.
Among a tiny minority of players that is not drawing the attention or concern of the vast majority of players, unlike in 12.0.
Parry is working minimally; it’s either a hit or a miss. And there seems to be a major problem with intercepting. Wth is going on??? Can we please get an answer on this, @Kabam Miike @Kabam Wolf @Kabam Vydious?
Thanks
I'm with you on this. I think 12.0 has been cited so many times, with every issue that comes up, that it's no longer really significant. Nor could it really be applied to anything since, in my mind.
I want to let you all know that we have a new update coming soon that will fix some of the issues that some of you have been encountering since the 17.0 Update. This includes a fix for the issue where players were not able to connect on their Cellular Network, and for the issues with Angela's animations being out of sync.
I don't have an exact timeline on when this new update will be available, but will update you all as soon as I have more information.
What about duels taking us back to the main screen now instead of the player select screen, missing % completed in AW and the champions has stopped running message that pops up all the time when I'm not even running the app?
Why is there not any word what-so-ever from a Kabam mod pertaining to this?