The game experienced a brief connectivity issue this morning. The team promptly fixed the issue and things are back to normal, thank you to everyone who passed along reports!
How to actually find these problems that Kabam is having with the game is actually quite easy.
SparkAlot
Member Posts: 957 ★★★★
Let's face it, the last 3 months now, every single version of the game has been broken in some way or another.
It really does seem that Kabam's QA is lacking the means to test things on as many devices as possible.
The solution would be to move the codebase to git (if it isn't already), and then start bisecting.
Then create APKs (and whatever Apple uses) of each version, and you will have a vast, willing army to test to see which exact version broke the thing everyone is complaining about.
Asking people for device details is an inadequate way to find the issues.
Then, once the version of the game is found, the devs can go back in and look over the code and see what exactly is the problem.
Yes, it is that easy.
@Kabam Miike @Kabam Lyra @Kabam Vydious @Kabam Zibiit what say you, how about letting us help you and find the broken commits that caused the latest issue of horrible lag throughout the game, arena, AW, crystals, scrolling map, danger rooms, you name it?
If you don't want it to be open to all, that is fine as well, but, for those of us suffering these drastic lag spurts, allow us access to developer builds so we can have instant feedback with them., and in turn helping out the whole community with better, more robust builds?
It really does seem that Kabam's QA is lacking the means to test things on as many devices as possible.
The solution would be to move the codebase to git (if it isn't already), and then start bisecting.
Then create APKs (and whatever Apple uses) of each version, and you will have a vast, willing army to test to see which exact version broke the thing everyone is complaining about.
Asking people for device details is an inadequate way to find the issues.
Then, once the version of the game is found, the devs can go back in and look over the code and see what exactly is the problem.
Yes, it is that easy.
@Kabam Miike @Kabam Lyra @Kabam Vydious @Kabam Zibiit what say you, how about letting us help you and find the broken commits that caused the latest issue of horrible lag throughout the game, arena, AW, crystals, scrolling map, danger rooms, you name it?
If you don't want it to be open to all, that is fine as well, but, for those of us suffering these drastic lag spurts, allow us access to developer builds so we can have instant feedback with them., and in turn helping out the whole community with better, more robust builds?
2
Comments
Then to have to worry about leaks of unfinshed content and what not, it wouldnt work well.
FYI
Point 1: if you ever want a job in programming, or want to keep your job, never show anyone this post
Point 2: there are already numerous copies of the apk floating around in the world. They're called modders, and currently they get banned for doing what you suggest, since that's how business works.
What is unfinished?
These builds I am suggesting are from the same tree that v20 was built from. There is no new info in them, the builds are just snapshots in time as each commit was made.
FYI: you don't know what you are talking about.
This is exactly how all good projects handle things, and it is the way all bugs are found in most software projects. Check out most open-source projects on GitHub or whatever, and you would see that their issue tracker is full of bisected reports on the faulty version, then the devs take that revision, and fix the issues with it.
Heck, that is also what Microsoft, Apple, Oracle and most all companies find bugs as well.
As for modding, this has nothing to do with that at all. APKs are just the Android packages of the game.
Releasing the APKs isn't a issue, these builds are all part of the same tree anyway, so no new info are in these, it is, as I said above just a snapshot in time when the commits were made.
I could say that bisection is not the best way to find performance problems, profiling is. Or I could say that bisection only really works on finely-grained modular software, which this game almost certainly is not (no game is, plus online games like this implemented in content data on customized framework environments pretty much cannot be).
Instead I'll just say that recommending that someone move their entire codebase to git so you can use git-bisect seems ludicrous to me, since accelerating the version search part of the problem makes no sense when the time to test each build is going to be several orders of magnitude longer than the time to perform the version winnowing by hand.
If its a unpublished build, I.e. not the current version, its a unfinished just like in any other beta program. Kabam isnt ready for a public beta on that scale and for what you are wanting. Regardless, even if there was a beta like that, if any issue gets missed, the community would be even more up in arms.
**** I meant legal not legs in my original comment.