TacoScotty wrote: » I r5 my 5* AA knowing he had this as an additional tool on his belt for certain content. Removing it and I would have preferred to leave him as r4. I have used a generic awakening gem on him as well on my other account. This is setting up for them to change how other champions behave and call it a bug only a few days before they make a change instead of more of a runway of known bugs.
DNA3000 wrote: » Kabam Miike wrote: » Hey Everybody, I'm sorry to report that a moderator gave you incorrect information when this was first reported. We know how important it is for us to be sure that we are giving you the most accurate information that we possibly can. This was a bug, and although it was a long standing one, it doesn't mean that we didn't have to fix it. Archangel’s Stun was not acting like every other stun in the game. I have no problem with the stun being changed. However, it honestly isn't enough to simply acknowledge that prior information given was incorrect. Players need to know that the information they are being given is trustworthy, and we aren't talking about a typo. The moderators have zero knowledge about design intent except by asking the developers and passing that information along. Such an error should therefore never take place. Kabam as a company must know at all times what information is being given to the players, and must correct errors when they are detected. It is not acceptable for Kabam representatives to make statements about gameplay Kabam cannot detect are in error. Mistakes happen. But there must be a way for Kabam to detect them and correct them. When this "bug" was determined to be a high priority bug, Kabam should have had a way to review all the information and discussions that had occurred about this issue prior to that point, if for no other reason than to be certain all the relevant information about the bug was known before the developers tackled it. During that review, the fact that the behavior was officially stated to be intended should have been detected at that time. If no part of the bug fix process reviewed all the statements and reports made by the players and the subsequent responses made by the developers and/or moderators, how would you even know whether you actually fixed all elements of the problem? I don't think it is unreasonable for players to expect that Kabam itself as an organization knows at all time what it is collectively telling the players, and to expect that information to remain consistent. Mistakes happen, and changes happen, but in both cases the players should reasonably expect that they will be promptly informed. Saying: "we've discovered that players were given incorrect information about the mechanics of Archangel's neurotoxin stun in the past, and unfortunately this behavior was not intended and is being changed" would not be perceived as fantastic, but it would be better than simply changing reality on the fly. And saying "we've discovered that a particular behavior that was originally intended has side effects that make it necessary to change the behavior" is also acceptable. Notice how much more generally understanding the community was about the Gwenpool change when it was simply straight up admitted that the behavior was originally intended but had to be changed due to an unforeseen exploit. Kabam's position continue to be that transparency is important, but to be candid you're only acknowledging what we already know. We were given wrong information, and now we're being told something different. I'm not saying don't fix the bug and I'm certainly not asking for RDTs or any other compensation. I'm asking if Kabam believes that giving us accurate information is important, why does it seem to not matter at all when incorrect information is given? Shouldn't there be some acknowledgement that the process failed to do so in this case, and that means the process needs to be improved in a way to prevent it from happening in the future?
Kabam Miike wrote: » Hey Everybody, I'm sorry to report that a moderator gave you incorrect information when this was first reported. We know how important it is for us to be sure that we are giving you the most accurate information that we possibly can. This was a bug, and although it was a long standing one, it doesn't mean that we didn't have to fix it. Archangel’s Stun was not acting like every other stun in the game.
DrZola wrote: » That noise you hear is wagons still being circled. Past experience suggests the approach will be to throw out a shiny object (new, better than average offer) and hold out for new content to distract. Then continue radio silence until any hue and cry over AA dies down. I don’t care whether restitution is RDTs or not. But I do care about candor and competence. When suicides and 12.0 hit, Ad0ra at least tried hard to interact and level with the community. I didn’t often like what she had to say, but she had guts to step up and say it. I miss her for that. Dr. Zola
Patchie93 wrote: » So lets see in one patch Changed AA Neurotoxins completely (passive to debuff) Made it so Drax can't bypass mordo astral evade with his first medium Made it so sun spideys spider sense is now passive and not a buff. And adjusted how magiks sp2 works so that she no longer can attain an ongoing power lock chain. Oh best part only 1 of these things were in the patch notes. So much for Kabam transparency@Kabam Miike @Kabam Vydious
Patchie93 wrote: » So lets see in one patch ...Made it so Drax can't bypass mordo astral evade with his first medium.
Magrailothos wrote: » Patchie93 wrote: » So lets see in one patch ...Made it so Drax can't bypass mordo astral evade with his first medium. Sorry, what? Has this happened?
Patchie93 wrote: » Screenshot taking right from his spotlight. So you are fundamentally changing something that isn't a bug as he is advertised this way
AlCapone2727 wrote: » Patchie93 wrote: » Screenshot taking right from his spotlight. So you are fundamentally changing something that isn't a bug as he is advertised this way This is getting lost in this thread. Please post on Reddit