phillgreen wrote: » GroundedWisdom wrote: » It's pretty clear AA is not intended to Stun through Immunity. Was this "pretty clear" to you prior to Wolf's post in January or after?
GroundedWisdom wrote: » It's pretty clear AA is not intended to Stun through Immunity.
ArmandStar wrote: » GroundedWisdom wrote: » ArmandStar wrote: » The issue is not the fact that Wolf was mistaken. Months ago we were given incorrect info, and that's understandable. The issue is that this change came out of the blue, and up to this point no one ever corrected the info. the fact that this change was implemented without informing the players beforehand is the problem everyone complains about How is this different than any other bug fix? They let us know when a resolution is being pushed. i'm not sure what you mean here. let me try again: for months, kabam knew this was a bug. during all these months, they had planned to fix it. during all these months, they knew the playerbase understood this bug as being "working as intended". during all these months, they never bothered to correct the information. that last part is the real problem. not the fact that we were misinformed, but the fact that they knew it and fixed the bug without correcting the misinformation
GroundedWisdom wrote: » ArmandStar wrote: » The issue is not the fact that Wolf was mistaken. Months ago we were given incorrect info, and that's understandable. The issue is that this change came out of the blue, and up to this point no one ever corrected the info. the fact that this change was implemented without informing the players beforehand is the problem everyone complains about How is this different than any other bug fix? They let us know when a resolution is being pushed.
ArmandStar wrote: » The issue is not the fact that Wolf was mistaken. Months ago we were given incorrect info, and that's understandable. The issue is that this change came out of the blue, and up to this point no one ever corrected the info. the fact that this change was implemented without informing the players beforehand is the problem everyone complains about
GroundedWisdom wrote: » ArmandStar wrote: » GroundedWisdom wrote: » ArmandStar wrote: » The issue is not the fact that Wolf was mistaken. Months ago we were given incorrect info, and that's understandable. The issue is that this change came out of the blue, and up to this point no one ever corrected the info. the fact that this change was implemented without informing the players beforehand is the problem everyone complains about How is this different than any other bug fix? They let us know when a resolution is being pushed. i'm not sure what you mean here. let me try again: for months, kabam knew this was a bug. during all these months, they had planned to fix it. during all these months, they knew the playerbase understood this bug as being "working as intended". during all these months, they never bothered to correct the information. that last part is the real problem. not the fact that we were misinformed, but the fact that they knew it and fixed the bug without correcting the misinformation We can't say what they were and were not aware of, simply because we can't speak for them. Also, the people responsible for fixing said bugs aren't responsible for moderating the Forum, perse. They may check the section, but I doubt they are in the business of clarifying Threads. This has become more blown up than is necessary. Miscommunication does not imply months of careless deceit. Honestly, people get a charge out of any mistake made.
Sirnoob2 wrote: » GroundedWisdom wrote: » ArmandStar wrote: » GroundedWisdom wrote: » ArmandStar wrote: » The issue is not the fact that Wolf was mistaken. Months ago we were given incorrect info, and that's understandable. The issue is that this change came out of the blue, and up to this point no one ever corrected the info. the fact that this change was implemented without informing the players beforehand is the problem everyone complains about How is this different than any other bug fix? They let us know when a resolution is being pushed. i'm not sure what you mean here. let me try again: for months, kabam knew this was a bug. during all these months, they had planned to fix it. during all these months, they knew the playerbase understood this bug as being "working as intended". during all these months, they never bothered to correct the information. that last part is the real problem. not the fact that we were misinformed, but the fact that they knew it and fixed the bug without correcting the misinformation We can't say what they were and were not aware of, simply because we can't speak for them. Also, the people responsible for fixing said bugs aren't responsible for moderating the Forum, perse. They may check the section, but I doubt they are in the business of clarifying Threads. This has become more blown up than is necessary. Miscommunication does not imply months of careless deceit. Honestly, people get a charge out of any mistake made. this miscommunication is being highlighted because of there failure to admit that there was a communcation breakdown on there end and try to fix it for the future an this is important because if people don't highlight it then it can happen again and again
GroundedWisdom wrote: » Shrugged off, what do you propose? It was a bug, a Moderator apologized for the miscommuncation, and it's being resolved. I don't see much room for anything else. The way I see it, people have been benefitting from an unintended bug for months, so there really is no need for some sort of compensation. What more could be said? They can't really do much else.
Sirnoob2 wrote: » GroundedWisdom wrote: » Shrugged off, what do you propose? It was a bug, a Moderator apologized for the miscommuncation, and it's being resolved. I don't see much room for anything else. The way I see it, people have been benefitting from an unintended bug for months, so there really is no need for some sort of compensation. What more could be said? They can't really do much else. hey we messed up where working on improving our way comuncating with u guys in the future we understand ur frustrations and will get back to u with the results of our work any statement like this would atleast show they care and acknowledge that there current system is messed up and that there working on improving it instead we get dead silence
GroundedWisdom wrote: » Sirnoob2 wrote: » GroundedWisdom wrote: » ArmandStar wrote: » GroundedWisdom wrote: » ArmandStar wrote: » The issue is not the fact that Wolf was mistaken. Months ago we were given incorrect info, and that's understandable. The issue is that this change came out of the blue, and up to this point no one ever corrected the info. the fact that this change was implemented without informing the players beforehand is the problem everyone complains about How is this different than any other bug fix? They let us know when a resolution is being pushed. i'm not sure what you mean here. let me try again: for months, kabam knew this was a bug. during all these months, they had planned to fix it. during all these months, they knew the playerbase understood this bug as being "working as intended". during all these months, they never bothered to correct the information. that last part is the real problem. not the fact that we were misinformed, but the fact that they knew it and fixed the bug without correcting the misinformation We can't say what they were and were not aware of, simply because we can't speak for them. Also, the people responsible for fixing said bugs aren't responsible for moderating the Forum, perse. They may check the section, but I doubt they are in the business of clarifying Threads. This has become more blown up than is necessary. Miscommunication does not imply months of careless deceit. Honestly, people get a charge out of any mistake made. this miscommunication is being highlighted because of there failure to admit that there was a communcation breakdown on there end and try to fix it for the future an this is important because if people don't highlight it then it can happen again and again How did they not admit it?
Sirnoob2 wrote: » GroundedWisdom wrote: » Sirnoob2 wrote: » GroundedWisdom wrote: » ArmandStar wrote: » GroundedWisdom wrote: » ArmandStar wrote: » The issue is not the fact that Wolf was mistaken. Months ago we were given incorrect info, and that's understandable. The issue is that this change came out of the blue, and up to this point no one ever corrected the info. the fact that this change was implemented without informing the players beforehand is the problem everyone complains about How is this different than any other bug fix? They let us know when a resolution is being pushed. i'm not sure what you mean here. let me try again: for months, kabam knew this was a bug. during all these months, they had planned to fix it. during all these months, they knew the playerbase understood this bug as being "working as intended". during all these months, they never bothered to correct the information. that last part is the real problem. not the fact that we were misinformed, but the fact that they knew it and fixed the bug without correcting the misinformation We can't say what they were and were not aware of, simply because we can't speak for them. Also, the people responsible for fixing said bugs aren't responsible for moderating the Forum, perse. They may check the section, but I doubt they are in the business of clarifying Threads. This has become more blown up than is necessary. Miscommunication does not imply months of careless deceit. Honestly, people get a charge out of any mistake made. this miscommunication is being highlighted because of there failure to admit that there was a communcation breakdown on there end and try to fix it for the future an this is important because if people don't highlight it then it can happen again and again How did they not admit it? all they said was our mod gave wrong info.... after it was already pointed out that's the problem this should've been addressed way before now
GroundedWisdom wrote: » Sirnoob2 wrote: » GroundedWisdom wrote: » Shrugged off, what do you propose? It was a bug, a Moderator apologized for the miscommuncation, and it's being resolved. I don't see much room for anything else. The way I see it, people have been benefitting from an unintended bug for months, so there really is no need for some sort of compensation. What more could be said? They can't really do much else. hey we messed up where working on improving our way comuncating with u guys in the future we understand ur frustrations and will get back to u with the results of our work any statement like this would atleast show they care and acknowledge that there current system is messed up and that there working on improving it instead we get dead silence It wasn't even noticed until now. Probably because they can't keep track of every Thread on a mental basis. They're doing a job. Which means they're focused on their responsibilities. After hundreds a day, you couldn't expect me to recall every word from months ago. There's a whole lack of understanding and compassion going on here. We expect perfection and we become righteously indignant when something slips through the cracks. Ever have a bad day? Ever lose track of something? Ever get focused on something else and lose your place? Come on now.
GroundedWisdom wrote: » Unfortunately, people were running with the money on that one.
GroundedWisdom wrote: » The point I'm making is it was a mistaken comment, as per the most recent clarification. We can either hold them over a fire, or accept the fact that mistakes can happen despite diligence. It's not that common of an occurrence, and there could be many reason behind the mistake that don't automatically imply them changing their say to suit their purpose. All I know is I have AA at R5, and none of the reasons I Ranked him involved bypassing Debuff Immunity.
GroundedWisdom wrote: » Would I be mad? No. If something is a bug, then it's a bug. I'm a lot more focused on the actual issue than someone's mistaken comment. I'm not operating on fuelling mistrust and suspicion. Whether the comment was incorrect or not is inconsequential at this point. It was a bug.
CodePlay wrote: » GroundedWisdom wrote: » The point I'm making is it was a mistaken comment, as per the most recent clarification. We can either hold them over a fire, or accept the fact that mistakes can happen despite diligence. It's not that common of an occurrence, and there could be many reason behind the mistake that don't automatically imply them changing their say to suit their purpose. All I know is I have AA at R5, and none of the reasons I Ranked him involved bypassing Debuff Immunity. Don't forget that this lead to other players to rank-up AA as they were informed AA is working as intended. It is good that they admitted about the misinformation, but they should be also responsible on the result that this has lead to players. Players deserve specific RDT, just like Brian Grant said in his video.
Stat wrote: » GroundedWisdom wrote: » Would I be mad? No. If something is a bug, then it's a bug. I'm a lot more focused on the actual issue than someone's mistaken comment. I'm not operating on fuelling mistrust and suspicion. Whether the comment was incorrect or not is inconsequential at this point. It was a bug. You are missing the point. It's only a "bug" because they now tell us it is one. At no point has it ever been pointed out as a bug; in fact, quite the opposite. It was specifically listed as NOT a bug by a forum moderator. In fact, there is a thread in the Bug and Known Issues Forum that is stickied at the top entitled "Known Issues." If this was known to the devs as a bug all this time, why has it never been up there as a known issue? So it's a "bug" when it becomes convenient for them to say it is one, allowing them to get around saying "we're changing one of this character's abilities because it is too strong" and getting the "NEEEERRFFFF!!!" outrage from everyone. Except the community (well, just about everyone but you) sees through this. If you don't see that then you are really blind to reality. Oh wait, as your post history on this forum has shown time and time again...you are.
GroundedWisdom wrote: » Primmer79 wrote: » GroundedWisdom wrote: » Animejay70 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. The issue with having a Stun that does not act like a debuff is that it was causing a lot of problems, and with more new content and modes being added, this was becoming a bigger and bigger problem. Archangel was not only able to bypass Stun Immune nodes, but his stun would bypass other Champions abilities, like Agent Venom's Tenacity or Black Panther (Civil War)'s Reflect Stun, as well as not interact with Masteries like Willpower. With this interaction becoming more and more prevalent in different game modes, we started seeing more of these problems come up, and this bug was one that became more of a priority. We don’t have any plans to distribute Rank Down tickets as this is resolving a bug and not changing an intended fundamental Champion mechanic in a significant way. You SHOULD give character specific rank down tickets for him since you're changing something that was used a lot. Since it was stated that it wasn't a bug, i took my 5* to r4 and pumped sig stones into him. I'd like the option to rank him down. Only it IS a bug. They don't give Tickets for bug fixes, and they don't come for all changes to Champs. Major changes would potentially qualify. We haven't seen alterations like those since 12.0. Didn't realize it was you with the pic change. Nice choice. Let's say this has been a bug all along. Kabam (or really rather, the player) has operated under a false comment from a moderator (who supposedly consults with other parts of the company). I think the issue is misinformation. From our side, it wasnt a bug, added to his power, then taken away. This isnt a MAJOR change, but it is (IMO) slightly higher than a minor change. but either way it is a change to his potential use. It's not much of a "let's say" situation. It was a bug. It's pretty clear AA is not intended to Stun through Immunity. I don't want to get too much into comments from Moderation out of respect, but I feel that the mistake has been exaggerated. People make mistakes. It's not a comment that has been repeatedly made. Someone did some digging to find it, from a while ago. AA's use is nowhere near exclusive to that, and we all know it. The real issue is people are upset something was commented that was mistaken. Regardless of our standards on Moderation, they are people, just like us. It's also possible the comment meant that the Parry was working as intended, but I can't speak for Wolf. For argument's sake we'll say the comment was mistaken. They are just as capable of mistakes as we are. As it so happens, it is a bug, and even if people Ranked for that reason, they still benefited from it. Now it's being fixed. No Dev would likely leave a bug active in contradiction to their intended design based on the fact that people Ranked to use it. If people Ranked AA based on that one bug alone, I would be skeptical, or suspicious of their understanding of his full use.
Primmer79 wrote: » GroundedWisdom wrote: » Animejay70 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. The issue with having a Stun that does not act like a debuff is that it was causing a lot of problems, and with more new content and modes being added, this was becoming a bigger and bigger problem. Archangel was not only able to bypass Stun Immune nodes, but his stun would bypass other Champions abilities, like Agent Venom's Tenacity or Black Panther (Civil War)'s Reflect Stun, as well as not interact with Masteries like Willpower. With this interaction becoming more and more prevalent in different game modes, we started seeing more of these problems come up, and this bug was one that became more of a priority. We don’t have any plans to distribute Rank Down tickets as this is resolving a bug and not changing an intended fundamental Champion mechanic in a significant way. You SHOULD give character specific rank down tickets for him since you're changing something that was used a lot. Since it was stated that it wasn't a bug, i took my 5* to r4 and pumped sig stones into him. I'd like the option to rank him down. Only it IS a bug. They don't give Tickets for bug fixes, and they don't come for all changes to Champs. Major changes would potentially qualify. We haven't seen alterations like those since 12.0. Didn't realize it was you with the pic change. Nice choice. Let's say this has been a bug all along. Kabam (or really rather, the player) has operated under a false comment from a moderator (who supposedly consults with other parts of the company). I think the issue is misinformation. From our side, it wasnt a bug, added to his power, then taken away. This isnt a MAJOR change, but it is (IMO) slightly higher than a minor change. but either way it is a change to his potential use.
GroundedWisdom wrote: » Animejay70 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. The issue with having a Stun that does not act like a debuff is that it was causing a lot of problems, and with more new content and modes being added, this was becoming a bigger and bigger problem. Archangel was not only able to bypass Stun Immune nodes, but his stun would bypass other Champions abilities, like Agent Venom's Tenacity or Black Panther (Civil War)'s Reflect Stun, as well as not interact with Masteries like Willpower. With this interaction becoming more and more prevalent in different game modes, we started seeing more of these problems come up, and this bug was one that became more of a priority. We don’t have any plans to distribute Rank Down tickets as this is resolving a bug and not changing an intended fundamental Champion mechanic in a significant way. You SHOULD give character specific rank down tickets for him since you're changing something that was used a lot. Since it was stated that it wasn't a bug, i took my 5* to r4 and pumped sig stones into him. I'd like the option to rank him down. Only it IS a bug. They don't give Tickets for bug fixes, and they don't come for all changes to Champs. Major changes would potentially qualify. We haven't seen alterations like those since 12.0.
Animejay70 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. The issue with having a Stun that does not act like a debuff is that it was causing a lot of problems, and with more new content and modes being added, this was becoming a bigger and bigger problem. Archangel was not only able to bypass Stun Immune nodes, but his stun would bypass other Champions abilities, like Agent Venom's Tenacity or Black Panther (Civil War)'s Reflect Stun, as well as not interact with Masteries like Willpower. With this interaction becoming more and more prevalent in different game modes, we started seeing more of these problems come up, and this bug was one that became more of a priority. We don’t have any plans to distribute Rank Down tickets as this is resolving a bug and not changing an intended fundamental Champion mechanic in a significant way. You SHOULD give character specific rank down tickets for him since you're changing something that was used a lot. Since it was stated that it wasn't a bug, i took my 5* to r4 and pumped sig stones into him. I'd like the option to rank him down.
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. The issue with having a Stun that does not act like a debuff is that it was causing a lot of problems, and with more new content and modes being added, this was becoming a bigger and bigger problem. Archangel was not only able to bypass Stun Immune nodes, but his stun would bypass other Champions abilities, like Agent Venom's Tenacity or Black Panther (Civil War)'s Reflect Stun, as well as not interact with Masteries like Willpower. With this interaction becoming more and more prevalent in different game modes, we started seeing more of these problems come up, and this bug was one that became more of a priority. We don’t have any plans to distribute Rank Down tickets as this is resolving a bug and not changing an intended fundamental Champion mechanic in a significant way.
GroundedWisdom wrote: » phillgreen wrote: » GroundedWisdom wrote: » It's pretty clear AA is not intended to Stun through Immunity. Was this "pretty clear" to you prior to Wolf's post in January or after? It was pretty clear to me all along. Nothing about AA's breakdown would enable him to Stun through Debuff Immunity.