What a month what a month... Well as a long time player, I'm not looking at Deep Dives anymore, I'll never spend on early access bundle ever again, and some of the CCP YT vids showcasing new champs not watching them... It used to be exciting to see a champ.. want it.. now even after you get it.. rank it.. sig it... Its just a gamble... Its really surprising how they are willing to take this much negativity after many people bought those r5 gems during 4th of july... Its just a champ targetted rank down.. so much negativity over 1 RDT
I unterstand your point. But there are some crazy Skill Champions out there. Zemo cant stand his ground against them without his mechanics. His damage is just not high enough @Dukenpuke
Agreed, I should have r4d kingpin or valk instead now.. gutted
I unterstand your point. But there are some crazy Skill Champions out there. Zemo cant stand his ground against them without his mechanics. His damage is just not high enough @Dukenpuke
I don't disagree. I'm just saying there are a lot of people that like him that chose to R5 him even without using the indefinite root lock mechanic.
Good response regarding Kraven. The level of detail is much appreciated but…
It remains an absolutely trash response regarding Zemo… sorry it just is. The Trello board is not easily visible or a wide spread communication. Instead the team remained silent while video after video was put out by content creators on this ability. A cacophony of promotional material vs. a poorly visible whisper that lacked context. Zemo deserves RDTs as well, because this change to root should have been highlighted at his balancing announcement it’s a big miss, not a small one and sorry is a poor replacement for the RDTs that should be there instead.
I do appreciate the thoughtful response, but disagree with the conclusion.
I bought many deals to get Zemo to rank 5 and never in my life before this incident heard about the trello board. The lack of communication on both champions is completely understated in Miike’s reply, you cannot just hack the usability of a champion in half and not offer compensation for those changes, even if you communicated it properly in the
First, we want to apologize for this situation. It was not our intent to leave any of this information out of our release notes or make any changes silently. We do not purposely make silent changes to the game, but there are processes in place that, in this case, didn’t work and this information was not disseminated the way it should have been.
Instead of asking the Devs a bunch of questions, and then translating them into communications for you, I’ve asked the Developers directly to write something up, and share it with you. This covers why we made these changes, and where we messed up on the communication process.
History of the bug and identifying it:
Back in January as Zemo was heading out the door, someone made an offhand comment about how the defender’s heavy bias while rooted seemed really reliable in keeping the opponent from throwing specials, to the point where they couldn’t remember it ever not working. No AI bias should ever be 100%, and that was not the intent with which we had been building characters. Our engineers informed us that root fully special locked the defender, preventing all three special attacks, and always had.
This was a problem because there is a big difference between designing a character that reduces specials and grants openings, and designing a character that prevents them.
Zemo in particular had the most aggressive use of the mechanic yet, because we were evaluating it in the former terms and not the latter. As a team, we knew a change was necessary, but had to decide what change to pursue. There were some good arguments made in favor of removing the special lock entirely and leaning on the very high heavy bias already present, since that was the original intent behind the mechanic. We decided against this because, as we said earlier, no AI bias is ever 100% reliable, and instead chose the middle ground of leaving the AI bias alone, preserving the inability for the defender to throw Special Attack 1 or 2, and just unlocking their Special 3.
This account may cause some confusion because root didn’t use to cause the defender’s power bar to grey out, a visual we normally associate with special locks, and now does. This was an accidental knock-on of the prep we needed to do for the change, but the change below three bars is exclusively visual.
Some of you may also wonder why defenders could break out of Spider-Man (Sorcerer Supreme)’s root before if root prevented all specials, and that’s actually because there was a 0.1s delay before his root activated to allow for VFX to kick in, during which the defender could activate a special because of the way Special 3 animations work. We have actually replaced this delay with an invisible special lock to make his root mechanic more consistent with other characters and easier to use.
How did we Miss This?
First, we announced that Zemo was bugged via the Trello board as quickly as we could. This is why we have created that board, so we can share identified bugs as soon as we know about them, regardless of if we know what the resolution will be. At the time, we were still having conversations about how broad the fix needed to be, and so the listed bug only referred to Zemo.
At the time, we were unaware of the extent to which players were relying on the existing interaction to use Kraven, or we would’ve mentioned him by name as well. It was very much our mistake for not understanding that, and we apologize.
When we did ultimately make the call that we were going to be fixing all root effects, we should have updated that post, but didn’t have systems in place for doing so. We’ll be amending our internal tracking process to make sure that the Trello board is better up to date with new developments going forward.
Second, we decided not to discuss this in Zemo’s rebalancing post because we sincerely did not consider it to be part of his rebalancing process. This is, in retrospect, another mistake on our part. “Root-locking” the opponent was never one of his goals, most players weren’t doing it anyway, and we weren’t holding the outliers against him when evaluating his data, so it didn’t factor into whether we considered him balanced or not. Additionally, we considered the bug public knowledge due to the Trello board.
Lastly, we missed this change in the most recent patch notes. Writing patch notes is a very collaborative process that requires many different teams working together, and it’s easy for something to slip through the cracks. We will be re-evaluating the way in which we collect information for our patch notes in the future to help ensure that something like this doesn’t slip through the cracks again.
Root in the Future
Moving forward, this is how we intend for all Root effects to function unless otherwise specified, and will be expanding the in-game glossary to clarify as much.
Rooted defenders will be more likely to perform heavy attacks and unable to activate Special Attack 1 or 2, and any root that does not match this behavior should be considered to be bugged unless stated otherwise.
Dealing with the Current Situation
Because this bug was publicly announced via the Trello board during the 3-month window where Zemo was subject to change, we do not plan to issue any rank-down tickets for him, nor do we plan to offer any for Spider-Man, who is actually stronger after this change than before.
However, because Kraven is an older Champions and was not mentioned as affected by this bug in the past, we do plan to offer rank-down tickets to anyone with a ranked up 5 or 6-star Kraven as of the time of this post. Only those that have ranked up Kraven prior to this message going live (2:30pm PT on July 14, 2023) will receive those Rank Down tickets, so please do not rank up Kraven expecting a Rank Down ticket in the future. We plan for these to go out before the end of the month.
Once again, we want to apologize for our misunderstanding around Kraven and for the failures in communication, and will be making process changes to prevent repeats.
So what you’re saying is that root was never bugged. What you’re saying is that you intentionally decided to nerf it because it was too strong/reliable… and all this without communicating about this? Even if you did, stop calling this a bug, it’s simply not, it’s a nerf to the feature! That in itself warrants compensation!
Just out of curiosity, isnt this situation WORSE than Moleman's?.. at least it was known that it was bugged... We never knew if he was even gonna be fixed.. and we got RDT after it was fixed.. This wasn't even called bugged...
Good response regarding Kraven. The level of detail is much appreciated but…
It remains an absolutely trash response regarding Zemo… sorry it just is. The Trello board is not easily visible or a wide spread communication. Instead the team remained silent while video after video was put out by content creators on this ability. A cacophony of promotional material vs. a poorly visible whisper that lacked context. Zemo deserves RDTs as well, because this change to root should have been highlighted at his balancing announcement it’s a big miss, not a small one and sorry is a poor replacement for the RDTs that should be there instead.
I do appreciate the thoughtful response, but disagree with the conclusion.
I bought many deals to get Zemo to rank 5 and never in my life before this incident heard about the trello board. The lack of communication on both champions is completely understated in Miike’s reply, you cannot just hack the usability of a champion in half and not offer compensation for those changes, even if you communicated it properly in the
First, we want to apologize for this situation. It was not our intent to leave any of this information out of our release notes or make any changes silently. We do not purposely make silent changes to the game, but there are processes in place that, in this case, didn’t work and this information was not disseminated the way it should have been.
Instead of asking the Devs a bunch of questions, and then translating them into communications for you, I’ve asked the Developers directly to write something up, and share it with you. This covers why we made these changes, and where we messed up on the communication process.
History of the bug and identifying it:
Back in January as Zemo was heading out the door, someone made an offhand comment about how the defender’s heavy bias while rooted seemed really reliable in keeping the opponent from throwing specials, to the point where they couldn’t remember it ever not working. No AI bias should ever be 100%, and that was not the intent with which we had been building characters. Our engineers informed us that root fully special locked the defender, preventing all three special attacks, and always had.
This was a problem because there is a big difference between designing a character that reduces specials and grants openings, and designing a character that prevents them.
Zemo in particular had the most aggressive use of the mechanic yet, because we were evaluating it in the former terms and not the latter. As a team, we knew a change was necessary, but had to decide what change to pursue. There were some good arguments made in favor of removing the special lock entirely and leaning on the very high heavy bias already present, since that was the original intent behind the mechanic. We decided against this because, as we said earlier, no AI bias is ever 100% reliable, and instead chose the middle ground of leaving the AI bias alone, preserving the inability for the defender to throw Special Attack 1 or 2, and just unlocking their Special 3.
This account may cause some confusion because root didn’t use to cause the defender’s power bar to grey out, a visual we normally associate with special locks, and now does. This was an accidental knock-on of the prep we needed to do for the change, but the change below three bars is exclusively visual.
Some of you may also wonder why defenders could break out of Spider-Man (Sorcerer Supreme)’s root before if root prevented all specials, and that’s actually because there was a 0.1s delay before his root activated to allow for VFX to kick in, during which the defender could activate a special because of the way Special 3 animations work. We have actually replaced this delay with an invisible special lock to make his root mechanic more consistent with other characters and easier to use.
How did we Miss This?
First, we announced that Zemo was bugged via the Trello board as quickly as we could. This is why we have created that board, so we can share identified bugs as soon as we know about them, regardless of if we know what the resolution will be. At the time, we were still having conversations about how broad the fix needed to be, and so the listed bug only referred to Zemo.
At the time, we were unaware of the extent to which players were relying on the existing interaction to use Kraven, or we would’ve mentioned him by name as well. It was very much our mistake for not understanding that, and we apologize.
When we did ultimately make the call that we were going to be fixing all root effects, we should have updated that post, but didn’t have systems in place for doing so. We’ll be amending our internal tracking process to make sure that the Trello board is better up to date with new developments going forward.
Second, we decided not to discuss this in Zemo’s rebalancing post because we sincerely did not consider it to be part of his rebalancing process. This is, in retrospect, another mistake on our part. “Root-locking” the opponent was never one of his goals, most players weren’t doing it anyway, and we weren’t holding the outliers against him when evaluating his data, so it didn’t factor into whether we considered him balanced or not. Additionally, we considered the bug public knowledge due to the Trello board.
Lastly, we missed this change in the most recent patch notes. Writing patch notes is a very collaborative process that requires many different teams working together, and it’s easy for something to slip through the cracks. We will be re-evaluating the way in which we collect information for our patch notes in the future to help ensure that something like this doesn’t slip through the cracks again.
Root in the Future
Moving forward, this is how we intend for all Root effects to function unless otherwise specified, and will be expanding the in-game glossary to clarify as much.
Rooted defenders will be more likely to perform heavy attacks and unable to activate Special Attack 1 or 2, and any root that does not match this behavior should be considered to be bugged unless stated otherwise.
Dealing with the Current Situation
Because this bug was publicly announced via the Trello board during the 3-month window where Zemo was subject to change, we do not plan to issue any rank-down tickets for him, nor do we plan to offer any for Spider-Man, who is actually stronger after this change than before.
However, because Kraven is an older Champions and was not mentioned as affected by this bug in the past, we do plan to offer rank-down tickets to anyone with a ranked up 5 or 6-star Kraven as of the time of this post. Only those that have ranked up Kraven prior to this message going live (2:30pm PT on July 14, 2023) will receive those Rank Down tickets, so please do not rank up Kraven expecting a Rank Down ticket in the future. We plan for these to go out before the end of the month.
Once again, we want to apologize for our misunderstanding around Kraven and for the failures in communication, and will be making process changes to prevent repeats.
So what you’re saying is that root was never bugged. What you’re saying is that you intentionally decided to nerf it because it was too strong/reliable… and all this without communicating about this? Even if you did, stop calling this a bug, it’s simply not, it’s a nerf to the feature! That in itself warrants compensation!
Setting beef aside for a second. I do want to remind everyone that these are words from the developers communicated to us through Kabam Miike and not his own words.
Agree with the kraven RDT’s as he’s been out for well over a year.
But Zemo? He already had his rebalance info come out. No mention of changing root and only NOW it takes effect. So as far as I’m concerned, that grace period of 3 months where the champion can change does NOT apply here. Root was changed very recently and it directly affects Zemo, and to not document that change anywhere other than a 3rd party website that isn’t available anywhere in game (and tricky to find in forums) isn’t really good enough.
Just out of curiosity, isnt this situation WORSE than Moleman's?.. at least it was known that it was bugged... We never knew if he was even gonna be fixed.. and we got RDT after it was fixed.. This wasn't even called bugged...
Yes it is. The fact that people are comparing the two is laughable. Mole Man had the described intention of his ability written clearly in game. Zemo and Kraven did not (and still don't)
Just out of curiosity, isnt this situation WORSE than Moleman's?.. at least it was known that it was bugged... We never knew if he was even gonna be fixed.. and we got RDT after it was fixed.. This wasn't even called bugged...
Yes it is. The fact that people are comparing the two is laughable. Mole Man had the described intention of his ability written clearly in game. Zemo and Kraven did not (and still don't)
And at least mole man’s fix was listed as a bug fix in the patch notes… nothing about Zemo’s root fix.
Just out of curiosity, isnt this situation WORSE than Moleman's?.. at least it was known that it was bugged... We never knew if he was even gonna be fixed.. and we got RDT after it was fixed.. This wasn't even called bugged...
Yes it is. The fact that people are comparing the two is laughable. Mole Man had the described intention of his ability written clearly in game. Zemo and Kraven did not (and still don't)
Wait im comparing the 2 🤔 am i being laughable? Cause i feel you agreed and then kicked me in the nuts 🤣
Just out of curiosity, isnt this situation WORSE than Moleman's?.. at least it was known that it was bugged... We never knew if he was even gonna be fixed.. and we got RDT after it was fixed.. This wasn't even called bugged...
Yes it is. The fact that people are comparing the two is laughable. Mole Man had the described intention of his ability written clearly in game. Zemo and Kraven did not (and still don't)
Wait im comparing the 2 🤔 am i being laughable? Cause i feel you agreed and then kicked me in the nuts 🤣
Nah my bad, I mean the people saying this is just like the Mole Man fix instead of stating the obvious: this is far worse than the Mole Man fix
Its like fraud. They just opened a shopping centre in the game-dropped all events bugged-dropped aw persistent placement completely bugged-dropped BG bugged-destroyed zemo that is a champion who brought kabam a lot of money
Just out of curiosity, isnt this situation WORSE than Moleman's?.. at least it was known that it was bugged... We never knew if he was even gonna be fixed.. and we got RDT after it was fixed.. This wasn't even called bugged...
Yes it is. The fact that people are comparing the two is laughable. Mole Man had the described intention of his ability written clearly in game. Zemo and Kraven did not (and still don't)
Wait im comparing the 2 🤔 am i being laughable? Cause i feel you agreed and then kicked me in the nuts 🤣
Nah my bad, I mean the people saying this is just like the Mole Man fix instead of stating the obvious: this is far worse than the Mole Man fix
I used MoleMan as an example as that situation was definitely not as egregious but also has similar echos of poor communication… as I was expecting RDTs for both champs to be the conclusion.
Yeah I have been playing for a long time and I have been a forum member for quite a while. I have never heard or read anywhere a reference to a “trello board.”
Yeah I have been playing for a long time and I have been a forum member for quite a while. I have never heard or read anywhere a reference to a “trello board.”
Is the trello board the bug tab on the forums?
It's linked in the bugs and issue tracker pinned thread
Completely disagree about not providing rank down tickets for Zemo.
This affects him (Baron Zemo) more than Kraven as more people use and ranked up Baron Zemo.
I don't see how saying this was mentioned on "Trello board" should be something most players even know about. No one in majority of my Line chats know what this is, and the fact it's not in the forums or in-game already is a big problem.
The simple fact is that the people on the forum are about 50% of your player base at most shows there is a major disconnect with this reasoning. There's many who don't use the forums and that's why it's important to communicate in-game mail and notifications more than anything else.
Never has there been in-game communication stating we need to use this "Trello Board" (or a link to this) in order to ensure we don't rank champions up that are deemed "bugged" many months after release.
I humbly ask to have this reconsidered and offer all Summoners the ability to rank down Baron Zemo as well as Kraven as this affects any that don't have anything to do with a off-site and non-in-game place for information.
It's best to remember that many do not play this game as much as others and have family and jobs that require them to focus on that more than this game. Asking those players to keep track of 3 different places (in-game, forums and now Trello Board) is asking something beyond a reasonable request.
Kabams logic more people use zemo and ranked him up and he's newer so no Rank down maybe like 5 people in the game ranked up kraven let's give them Rank down tickets
I feel like @BloodyCruelty is karatemikes alt forum acc that kabam doesn't know it's him so this is how he lets out his true feelings about them..... Probably not tho
Completely disagree about not providing rank down tickets for Zemo.
This affects him (Baron Zemo) more than Kraven as more people use and ranked up Baron Zemo.
I don't see how saying this was mentioned on "Trello board" should be something most players even know about. No one in majority of my Line chats know what this is, and the fact it's not in the forums or in-game already is a big problem.
The simple fact is that the people on the forum are about 50% of your player base at most shows there is a major disconnect with this reasoning. There's many who don't use the forums and that's why it's important to communicate in-game mail and notifications more than anything else.
Never has there been in-game communication stating we need to use this "Trello Board" (or a link to this) in order to ensure we don't rank champions up that are deemed "bugged" many months after release.
I humbly ask to have this reconsidered and offer all Summoners the ability to rank down Baron Zemo as well as Kraven as this affects any that don't have anything to do with a off-site and non-in-game place for information.
It's best to remember that many do not play this game as much as others and have family and jobs that require them to focus on that more than this game. Asking those players to keep track of 3 different places (in-game, forums and now Trello Board) is asking something beyond a reasonable request.
Thank you,
Mando
Even the term "bugged" is wrong, the developers outed themselves in their reply by saying they considered the root an op ability and they decided to nerf it. Labeling it as a bug even in that stupid trello board is plainly put disingenuous. Zemo rank down tickets are necessary, ESPECIALLY after that reply that CONFIRMS that it is not a bug, but a NERF to root.
Completely disagree about not providing rank down tickets for Zemo.
This affects him (Baron Zemo) more than Kraven as more people use and ranked up Baron Zemo.
I don't see how saying this was mentioned on "Trello board" should be something most players even know about. No one in majority of my Line chats know what this is, and the fact it's not in the forums or in-game already is a big problem.
The simple fact is that the people on the forum are about 50% of your player base at most shows there is a major disconnect with this reasoning. There's many who don't use the forums and that's why it's important to communicate in-game mail and notifications more than anything else.
Never has there been in-game communication stating we need to use this "Trello Board" (or a link to this) in order to ensure we don't rank champions up that are deemed "bugged" many months after release.
I humbly ask to have this reconsidered and offer all Summoners the ability to rank down Baron Zemo as well as Kraven as this affects any that don't have anything to do with a off-site and non-in-game place for information.
It's best to remember that many do not play this game as much as others and have family and jobs that require them to focus on that more than this game. Asking those players to keep track of 3 different places (in-game, forums and now Trello Board) is asking something beyond a reasonable request.
Thank you,
Mando
Even the term "bugged" is wrong, the developers outed themselves in their reply by saying they considered the root an op ability and they decided to nerf it. Labeling it as a bug even in that stupid trello board is plainly put disingenuous. Zemo rank down tickets are necessary, ESPECIALLY after that reply that CONFIRMS that it is not a bug, but a NERF to root.
Did they say that?
The way I read it was that the original intention of the root mechanic was to have the AI of rooted champs "bias" towards heavy attacks. However, in practice, that bias meant that a rooted champ would never actually throw a special while rooted.
At worst, it's a miscommunication between the design team and the development team about the intended functionality of the mechanic. The design team never intended for these champs to not throw specials, but that's how it ended up being implemented.
It's a legitimate gripe to say that it was labeled as a "Zemo bug" instead of a "root bug," but I don't think there's any issue with calling it a "bug." It was a mechanic that was implemented in a way that was not intended.
A few things that stand out to me after thinking about this for a bit.
They said they first noticed a problem when Zemo went out the door in January. That means they knew he was “bugged” and still released him and said nothing in his deep dive or to preface his pre release bundles or at any point until April 18, almost 3 months after his release.
Then there is this quote: “ Because this bug was publicly announced via the Trello board during the 3-month window where Zemo was subject to change, we do not plan to issue any rank-down tickets for him, nor do we plan to offer any for Spider-Man, who is actually stronger after this change than before.”
It’s extremely tone deaf and a little condescending. Many others have pointed out how much they overestimate the value putting it on the trello board. But they go so far as to say they put it there during his rebalance window so everyone should have factored that in to rankup decisions even though they never mentioned it in his rebalance update. I don’t think I’m alone in assuming part of the rebalance update was to make us aware of any bugs or other unintended interactions they planned to address with a champ. That kinda seemed like half the reason for the process, the other half being adjusting parts of the kit that are over/underperforming. This response implies we have to track bugs that may never be fixed on top of the rebalance updates to have any confidence in our rank up decisions.
On top of that, they threw in some nonsense about not offering RDTs for mystic spidey which nobody was asking for at all and felt the need to point out this makes him better which is completely irrelevant to the issue of an RDT for Zemo.
And this also means they felt no need to tell CCP members that their content was teaching people to exploit what they are claiming was a “known bug” with Zemo.
Completely disagree about not providing rank down tickets for Zemo.
This affects him (Baron Zemo) more than Kraven as more people use and ranked up Baron Zemo.
I don't see how saying this was mentioned on "Trello board" should be something most players even know about. No one in majority of my Line chats know what this is, and the fact it's not in the forums or in-game already is a big problem.
The simple fact is that the people on the forum are about 50% of your player base at most shows there is a major disconnect with this reasoning. There's many who don't use the forums and that's why it's important to communicate in-game mail and notifications more than anything else.
Never has there been in-game communication stating we need to use this "Trello Board" (or a link to this) in order to ensure we don't rank champions up that are deemed "bugged" many months after release.
I humbly ask to have this reconsidered and offer all Summoners the ability to rank down Baron Zemo as well as Kraven as this affects any that don't have anything to do with a off-site and non-in-game place for information.
It's best to remember that many do not play this game as much as others and have family and jobs that require them to focus on that more than this game. Asking those players to keep track of 3 different places (in-game, forums and now Trello Board) is asking something beyond a reasonable request.
Thank you,
Mando
Even the term "bugged" is wrong, the developers outed themselves in their reply by saying they considered the root an op ability and they decided to nerf it. Labeling it as a bug even in that stupid trello board is plainly put disingenuous. Zemo rank down tickets are necessary, ESPECIALLY after that reply that CONFIRMS that it is not a bug, but a NERF to root.
Did they say that?
The way I read it was that the original intention of the root mechanic was to have the AI of rooted champs "bias" towards heavy attacks. However, in practice, that bias meant that a rooted champ would never actually throw a special while rooted.
At worst, it's a miscommunication between the design team and the development team about the intended functionality of the mechanic. The design team never intended for these champs to not throw specials, but that's how it ended up being implemented.
It's a legitimate gripe to say that it was labeled as a "Zemo bug" instead of a "root bug," but I don't think there's any issue with calling it a "bug." It was a mechanic that was implemented in a way that was not intended.
Valid argument if a small thing called "testing new mechanics you’re putting into your game" didn’t exist. It’s not a bug if you suddenly decide it needs to do something else completely, they are nerfing a FEATURE of root.
Man… I keep thinking about the content creators that put out videos on the Root-Lock… if it was me I’d pull it all down and redo any Zemo related content that relies on this mechanism
Comments
Well as a long time player, I'm not looking at Deep Dives anymore, I'll never spend on early access bundle ever again, and some of the CCP YT vids showcasing new champs not watching them...
It used to be exciting to see a champ.. want it.. now even after you get it.. rank it.. sig it... Its just a gamble...
Its really surprising how they are willing to take this much negativity after many people bought those r5 gems during 4th of july... Its just a champ targetted rank down.. so much negativity over 1 RDT
This wasn't even called bugged...
But Zemo? He already had his rebalance info come out. No mention of changing root and only NOW it takes effect. So as far as I’m concerned, that grace period of 3 months where the champion can change does NOT apply here. Root was changed very recently and it directly affects Zemo, and to not document that change anywhere other than a 3rd party website that isn’t available anywhere in game (and tricky to find in forums) isn’t really good enough.
Kabam, communication is everything.
Silly me.
Is the trello board the bug tab on the forums?
This affects him (Baron Zemo) more than Kraven as more people use and ranked up Baron Zemo.
I don't see how saying this was mentioned on "Trello board" should be something most players even know about. No one in majority of my Line chats know what this is, and the fact it's not in the forums or in-game already is a big problem.
The simple fact is that the people on the forum are about 50% of your player base at most shows there is a major disconnect with this reasoning. There's many who don't use the forums and that's why it's important to communicate in-game mail and notifications more than anything else.
Never has there been in-game communication stating we need to use this "Trello Board" (or a link to this) in order to ensure we don't rank champions up that are deemed "bugged" many months after release.
I humbly ask to have this reconsidered and offer all Summoners the ability to rank down Baron Zemo as well as Kraven as this affects any that don't have anything to do with a off-site and non-in-game place for information.
It's best to remember that many do not play this game as much as others and have family and jobs that require them to focus on that more than this game. Asking those players to keep track of 3 different places (in-game, forums and now Trello Board) is asking something beyond a reasonable request.
Thank you,
Mando
The way I read it was that the original intention of the root mechanic was to have the AI of rooted champs "bias" towards heavy attacks. However, in practice, that bias meant that a rooted champ would never actually throw a special while rooted.
At worst, it's a miscommunication between the design team and the development team about the intended functionality of the mechanic. The design team never intended for these champs to not throw specials, but that's how it ended up being implemented.
It's a legitimate gripe to say that it was labeled as a "Zemo bug" instead of a "root bug," but I don't think there's any issue with calling it a "bug." It was a mechanic that was implemented in a way that was not intended.
They said they first noticed a problem when Zemo went out the door in January. That means they knew he was “bugged” and still released him and said nothing in his deep dive or to preface his pre release bundles or at any point until April 18, almost 3 months after his release.
Then there is this quote:
“ Because this bug was publicly announced via the Trello board during the 3-month window where Zemo was subject to change, we do not plan to issue any rank-down tickets for him, nor do we plan to offer any for Spider-Man, who is actually stronger after this change than before.”
It’s extremely tone deaf and a little condescending. Many others have pointed out how much they overestimate the value putting it on the trello board. But they go so far as to say they put it there during his rebalance window so everyone should have factored that in to rankup decisions even though they never mentioned it in his rebalance update. I don’t think I’m alone in assuming part of the rebalance update was to make us aware of any bugs or other unintended interactions they planned to address with a champ. That kinda seemed like half the reason for the process, the other half being adjusting parts of the kit that are over/underperforming. This response implies we have to track bugs that may never be fixed on top of the rebalance updates to have any confidence in our rank up decisions.
On top of that, they threw in some nonsense about not offering RDTs for mystic spidey which nobody was asking for at all and felt the need to point out this makes him better which is completely irrelevant to the issue of an RDT for Zemo.
And this also means they felt no need to tell CCP members that their content was teaching people to exploit what they are claiming was a “known bug” with Zemo.