They responded they are looking into it. That’s all will happen. No more responses hoping this thread will die out. Just like others over the last 8 months.
They're already looking into it. We're not going to know anything right this second. Plus, it's not effecting everyone so they can't just stop.it because it's effecting some. Let them get some info. We'll know more in the morning. None of those mods are even on right now, tagging them is pointless.
Thanks for the answers! For those of you who are saying that this is not a timing issue and that Block isn't working at all, can you please hold Block for 1 second or longer and then confirm whether Block comes up? Even if it's late/timing is off, we'd just like to know that Block does actually come up eventually.
Why the heck doesn’t Kabam test issues? this is nuts.
There's an issue, and they're looking into it. I get that frustrations are paramount, but there's no use in dog piling on people and arguing about testing. If it was preventable before it was released, they wouldn't have released it. As much as people are frustrated, we're just going to have to wait for them to look into it.
There is this issue where game lag or there is some difference in frame rate for more than six months but there issue is solved by restarting the game or restarting my phone but after the latest version (33.3) update these issues had become permanent even restarting the app or phone are not solving these issue. I have to participate in war with these issues and have to give many kills thanks to these issues i can't play a proper game please end this war as soon as possible and from what I have seen these issues are there in most of the Android devices and i use OnePlus 8pro . And yes i also withdrawn from beta features because of this lag issue or frame rate issue or glitch i don't know what it's called but the game has died, parry not working well, dex not working well, something the attacker won't block and sometimes the attacker do heavy instead of light attack please fix this game and end the war as soon as possible because many people do play game in Android phone too
There's an issue, and they're looking into it. I get that frustrations are paramount, but there's no use in dog piling on people and arguing about testing. If it was preventable before it was released, they wouldn't have released it. As much as people are frustrated, we're just going to have to wait for them to look into it.
I agree, What's done is done but for a game that's treading on top 50 atleast there should be robust testing.
I was trying to give some constructive feedback to improve future rollout but I guess It does not work that way.
The problem is, it's not as simple as in-house testing. The game exists simultaneously between our devices (which can vary), their end, and their partners' servers. It's basically a live mesh. I'm not saying people don't have the right to ask for quality control. I'm simply saying testing isn't always enough. It would be a fair assessment if the game itself was completely stored on our devices, and it was a poorly-executed product. In this case, there are more variables than that.
At this juncture they should do parallel testing between old version and new version in test environment.
Lol did you Google a bunch of coding verbage?
Take a course it will more useful use of your time.
I don't need to, I work programmers daily. Its quite obvious you don't.
I have worked on Banking solutions and if we get bugs like this we are screwed, even a minor bug is tested out with scenario testing.
This bug was so huge the update should never had been rolled out.
I am not going to teach you more , better google software testing you may know a thing or two.
This isn't banking software. It's not even close to being the same thing. Your software is deployed on the same types of devices, PCs. You don't have a anything near what Kabam has in terms of software or hardware.
Just like with my job, I can't compare what software we work on to what Kabam does. I can understand where they are coming from though.
And you wouldn't be screwed because, like my job, banking has back methods if software goes down. You're just trying to be dramatic.
Let me know when you get some experience with Unity or anything much closer to working on mobile games.
The simplest gesture would be to Cancel WAR season as of last war and then postpone AQ starting tomorrow. You will save aggravation of millions of players - not to mention you are yet to acknowledge the issue via in-game message.
My teammates(android) heavily affected due to this update. Too many KO, and unnecessarily loosing against weak team. Half of my teammates declared not playing anymore AW. Something need to be done urgently
This is not helpful but I took out the old and dusted iphone 7 without the latest patch and managed to take down the AW boss.
I am hoping in the next few days when the app force an update, this old work horse can still run the course. For the Android phone, it will be auto-fight only.
I have worked on Banking solutions and if we get bugs like this we are screwed, even a minor bug is tested out with scenario testing.
1. Banking software is some of the worst enterprise software out there. And I’m not even talking about Fiserv or Diebold, I’m talking about the home grown stuff. I mean, it’s not hospital enterprise software, but then again nothing is that much of a train wreck.
2. Pretty much everything you’ve ever worked on has probably been modularized monolithic software. That’s where stuff like unit testing and integration testing can sometimes make sense. In game development (for this kind of game) this generally has no application, because there are no units and there is minimal integration.
There’s a lot of different software development models and expertise on one doesn’t translate to the others. Games like this are developed with non-abstracted layering. No one can just transplant their modules from one engine to another, nor can they reasonably test different modules without the others. When you ignore the kind of development or aren’t even aware of it, you get weird mismatched suggestions. Your suggestions are comparable to someone saying the developers should use a better inheritance model for champions. No matter how many years of C++ programming someone has, that suggestion would be no less weird. It might make sense if champions were C++ objects or classes, but they aren’t and nobody would make them that way (because that would break the development model everyone uses).
I've rebooted my phone several times and is continuously repeatable in AW and Arena so far since I updated my Samsung phone. Haven't tried quest yet. It isn't possible to parry champs that will lunge in.
Comments
As a user, I would prefer a content delay instead of this not- functional release ...
Why the heck doesn’t Kabam test issues? this is nuts.
Just like with my job, I can't compare what software we work on to what Kabam does. I can understand where they are coming from though.
And you wouldn't be screwed because, like my job, banking has back methods if software goes down. You're just trying to be dramatic.
Let me know when you get some experience with Unity or anything much closer to working on mobile games.
I am hoping in the next few days when the app force an update, this old work horse can still run the course.
For the Android phone, it will be auto-fight only.
2. Pretty much everything you’ve ever worked on has probably been modularized monolithic software. That’s where stuff like unit testing and integration testing can sometimes make sense. In game development (for this kind of game) this generally has no application, because there are no units and there is minimal integration.
There’s a lot of different software development models and expertise on one doesn’t translate to the others. Games like this are developed with non-abstracted layering. No one can just transplant their modules from one engine to another, nor can they reasonably test different modules without the others. When you ignore the kind of development or aren’t even aware of it, you get weird mismatched suggestions. Your suggestions are comparable to someone saying the developers should use a better inheritance model for champions. No matter how many years of C++ programming someone has, that suggestion would be no less weird. It might make sense if champions were C++ objects or classes, but they aren’t and nobody would make them that way (because that would break the development model everyone uses).
It isn't possible to parry champs that will lunge in.