Wait but he didn’t say anything about Zemo blocking while rooted and that’s what the thread was about 🤔 😂
What would you want Miike to even say? Their job is to pass along the information to the dev teams. He commented, the thread and the "problem" has been seen. He'll give it over to the devs.
At this point it’s deliberate, every patch he’s getting hit by something, it’s very tiring. And calling the root nerf a bug is straight up disrespectful.
You're right. It's being done deliberately .It's punishment to you for spamming the forums. Fir every post you make one more functionality gets nerfed. Stop now before it's too late
I’m simply making a post that shows with video proof just how horribly the AI reacts now. This comes from this patch, so why wouldn’t I report on it??
If you want to report it, I suggest using constructive criticism and putting it in the correct section of forums. All you literally had to do is go to the bugs and issues section of forums, make a post and say:
Hey guys, I found an unusual interaction with Zemo. Here is video evidence of how the AI used to react: [Video] And since the update, the AI won't drop their block anymore. [Video]
I'd greatly appreciate it if you could look into this.
If you do that, then people will be more inclined to help you.
No one cares about that section… unless more players band together in a post here, nothing gets done. That’s how I asked for rank down tickets for Kraven and because of how vocal the community was we got them.
I feel it's important to point this out, because I don't want this to be a prevalent impression that people receive, and there's a lot of misinformation here...
We absolutely pay attention to the reports here and in bugs. As @Pikolu is saying, that information doesn't need to come from a place of aggression and conspiracy theory, finger pointing or accusations. 99.9% of the time, if something is weird it's likely a mistake or a bug. Bugs happen, even if we all can agree we don't want them to.
This concept of "we need to be loud about it or they won't listen to us" is destructive at best. We listen to Summoners, and we always appreciate receiving feedback or information in a constructive manner. It's why we have "non-constructive" as a warning in these forums.
RDT for Kraven were given out because we made an inadvertent change to a Champion without communicating the base issue in the first place and we deemed it the right thing to do. Not because players came and yelled about it on the forums.
Who knows if this is a bug or if it’s a targeted nerf? Zemo has been nerfed in so many ways and still keeps getting nerfs. Are they all bugs? I don’t know. Leave him be and I won’t say a single thing. The only real Zemo bug is the one I also made a thread on where he misses his first medium if the opponent ducks during their heavy animation.
Wait but he didn’t say anything about Zemo blocking while rooted and that’s what the thread was about 🤔 😂
What would you want Miike to even say? Their job is to pass along the information to the dev teams. He commented, the thread and the "problem" has been seen. He'll give it over to the devs.
@Demonzfyre Exactly what you just said, let us know it’s actually a bug and that he’s gonna pass it on to the team 🤦🏻♂️
I thought the comment about not posting in bugs and known issues was because threads get buried and you get no response on the issues.
I don't know if you're trolling or just don't understand how things work. Miike doesn't determine what is or isn't a bug. You can't determine anything from what's presented here honestly. It's a 14 second clip and not even the entire fight and it's it's only 1 fight.
Miikes job is to now give this very thin piece of information to the devs and let them figure it out.
It's been stated dozens of times that just because a thread in the bugs section doesn't get a response, doesn't mean it hasn't been reported.
Wait but he didn’t say anything about Zemo blocking while rooted and that’s what the thread was about 🤔 😂
What would you want Miike to even say? Their job is to pass along the information to the dev teams. He commented, the thread and the "problem" has been seen. He'll give it over to the devs.
Jax not Miike
It doesn't matter. Miike and Jax both do the same thing and neither of them will tell you something like this is a bug without taking it to the team first.
At this point it’s deliberate, every patch he’s getting hit by something, it’s very tiring. And calling the root nerf a bug is straight up disrespectful.
You're right. It's being done deliberately .It's punishment to you for spamming the forums. Fir every post you make one more functionality gets nerfed. Stop now before it's too late
I’m simply making a post that shows with video proof just how horribly the AI reacts now. This comes from this patch, so why wouldn’t I report on it??
If you want to report it, I suggest using constructive criticism and putting it in the correct section of forums. All you literally had to do is go to the bugs and issues section of forums, make a post and say:
Hey guys, I found an unusual interaction with Zemo. Here is video evidence of how the AI used to react: [Video] And since the update, the AI won't drop their block anymore. [Video]
I'd greatly appreciate it if you could look into this.
If you do that, then people will be more inclined to help you.
No one cares about that section… unless more players band together in a post here, nothing gets done. That’s how I asked for rank down tickets for Kraven and because of how vocal the community was we got them.
I feel it's important to point this out, because I don't want this to be a prevalent impression that people receive, and there's a lot of misinformation here...
We absolutely pay attention to the reports here and in bugs. As @Pikolu is saying, that information doesn't need to come from a place of aggression and conspiracy theory, finger pointing or accusations. 99.9% of the time, if something is weird it's likely a mistake or a bug. Bugs happen, even if we all can agree we don't want them to.
This concept of "we need to be loud about it or they won't listen to us" is destructive at best. We listen to Summoners, and we always appreciate receiving feedback or information in a constructive manner. It's why we have "non-constructive" as a warning in these forums.
RDT for Kraven were given out because we made an inadvertent change to a Champion without communicating the base issue in the first place and we deemed it the right thing to do. Not because players came and yelled about it on the forums.
Who knows if this is a bug or if it’s a targeted nerf? Zemo has been nerfed in so many ways and still keeps getting nerfs. Are they all bugs? I don’t know. Leave him be and I won’t say a single thing. The only real Zemo bug is the one I also made a thread on where he misses his first medium if the opponent ducks during their heavy animation.
Sir, your wahmbulance is on the way. Keep your tinfoil hat on tight.
@Demonzfyre Exactly what you just said, let us know it’s actually a bug and that he’s gonna pass it on to the team 🤦🏻♂️
I thought the comment about not posting in bugs and known issues was because threads get buried and you get no response on the issues.
I don't know if you're trolling or just don't understand how things work. Miike doesn't determine what is or isn't a bug. You can't determine anything from what's presented here honestly. It's a 14 second clip and not even the entire fight and it's it's only 1 fight.
Miikes job is to now give this very thin piece of information to the devs and let them figure it out.
It's been stated dozens of times that just because a thread in the bugs section doesn't get a response, doesn't mean it hasn't been reported.
I mean, I can tell from the 1 frame in the post that the problem is AI blocking while rooted, which they shouldn't be doing.
@Demonzfyre I definitely know how it works and I have been here since 2017 just like you but I don’t spend no where near as much time on forum as you do and you keep saying Mike when it was Jax who commented and maybe he doesn’t know if it’s a bug or not but he said absolutely nothing about what the thread is actually about and that was my point.
@Demonzfyre Exactly what you just said, let us know it’s actually a bug and that he’s gonna pass it on to the team 🤦🏻♂️
I thought the comment about not posting in bugs and known issues was because threads get buried and you get no response on the issues.
I don't know if you're trolling or just don't understand how things work. Miike doesn't determine what is or isn't a bug. You can't determine anything from what's presented here honestly. It's a 14 second clip and not even the entire fight and it's it's only 1 fight.
Miikes job is to now give this very thin piece of information to the devs and let them figure it out.
It's been stated dozens of times that just because a thread in the bugs section doesn't get a response, doesn't mean it hasn't been reported.
I mean, I can tell from the 1 frame in the post that the problem is AI blocking while rooted, which they shouldn't be doing.
Where does it say rooted defenders can't block while rooted?
@Demonzfyre Exactly what you just said, let us know it’s actually a bug and that he’s gonna pass it on to the team 🤦🏻♂️
I thought the comment about not posting in bugs and known issues was because threads get buried and you get no response on the issues.
I don't know if you're trolling or just don't understand how things work. Miike doesn't determine what is or isn't a bug. You can't determine anything from what's presented here honestly. It's a 14 second clip and not even the entire fight and it's it's only 1 fight.
Miikes job is to now give this very thin piece of information to the devs and let them figure it out.
It's been stated dozens of times that just because a thread in the bugs section doesn't get a response, doesn't mean it hasn't been reported.
I mean, I can tell from the 1 frame in the post that the problem is AI blocking while rooted, which they shouldn't be doing.
I even showed the third light attack being blocked in that one frame, this guy thinks it’s only one fight, yet I was able to immediatly recreate this problem in LoL after encountering it in EQ
I wouldn't call it a nerf but they did change something (or it's just a bug). AI used to block first hit and then immediately charge heavy, now it just keeps blocking if you keep attacking.
@SecondSkriller , I think you’d get more traction if you toned down the aggressiveness and accusations a bit. It looks like you found a real issue but coming out the gate the way you did automatically turns some people against you.
For this issue, it would be nice to get some confirmation about whether this is an intended change or not and if it’s unintended, whether it is a true bug that needs fixed or if it’s just an unintended change but part of our “new normal” with the AI.
Jax/Miike - If you want people to use the bug forum I think you need to give at least some minimal feedback there. I know it’s not your job and I understand it would be more work but a simple “this has been reported to the team” and a followup - “this has been confirmed to be a bug” would go a long way. As it stands, the response of “we read and investigate all of them, we promise” isn’t enough to make people confident they’ve been heard so they come here to try to make sure it gets attention.
From what I’ve seen, the community does a good job explaining things to people that aren’t bugs when we can. Scrolling through a few pages there appear to be some legit bugs like Mr. sinister not healing from crits with no acknowledgment. If Mr . sinister was a more relevant champ I’d expect to see posts about that in the main forum to get some attention because that seems to be what works.
I also don’t believe there would have been RDTs for Kraven without that massive thread but that’s another topic all together.
@Demonzfyre Exactly what you just said, let us know it’s actually a bug and that he’s gonna pass it on to the team 🤦🏻♂️
I thought the comment about not posting in bugs and known issues was because threads get buried and you get no response on the issues.
I don't know if you're trolling or just don't understand how things work. Miike doesn't determine what is or isn't a bug. You can't determine anything from what's presented here honestly. It's a 14 second clip and not even the entire fight and it's it's only 1 fight.
Miikes job is to now give this very thin piece of information to the devs and let them figure it out.
It's been stated dozens of times that just because a thread in the bugs section doesn't get a response, doesn't mean it hasn't been reported.
I mean, I can tell from the 1 frame in the post that the problem is AI blocking while rooted, which they shouldn't be doing.
Where does it say rooted defenders can't block while rooted?
@SecondSkriller , I think you’d get more traction if you toned down the aggressiveness and accusations a bit. It looks like you found a real issue but coming out the gate the way you did automatically turns some people against you.
For this issue, it would be nice to get some confirmation about whether this is an intended change or not and if it’s unintended, whether it is a true bug that needs fixed or if it’s just an unintended change but part of our “new normal” with the AI.
Jax/Miike - If you want people to use the bug forum I think you need to give at least some minimal feedback there. I know it’s not your job and I understand it would be more work but a simple “this has been reported to the team” and a followup - “this has been confirmed to be a bug” would go a long way. As it stands, the response of “we read and investigate all of them, we promise” isn’t enough to make people confident they’ve been heard so they come here to try to make sure it gets attention.
From what I’ve seen, the community does a good job explaining things to people that aren’t bugs when we can. Scrolling through a few pages there appear to be some legit bugs like Mr. sinister not healing from crits with no acknowledgment. If Mr . sinister was a more relevant champ I’d expect to see posts about that in the main forum to get some attention because that seems to be what works.
I also don’t believe there would have been RDTs for Kraven without that massive thread but that’s another topic all together.
I’m pretty bad at that hehe, sorry. I’m good at finding these problems but bad at handling them. I made the thread on Zemo and Kraven, who were both my first r5 champs, which you can see how that enraged me, I’m still salty about that ngl. Wish I could just have my Kraven back the way he was…
Oh no @kabamJaxSucks! Your answer was good enough til you mentioned Kraven, and let me explain why. The controversy that this originally created because most people thought zemo deserved it was more than substantial. Almost no one plays Kraven. I liked your answer til you gave the comparison. It’s almost like throwing salt on an open wound. I was one of those people upset by that change and greatly upset. I literally rank 5’d him whatever that holiday sale was a ways back because I loved that you could play him multiple ways. Now he’s not as versatile and to me not as fun. I’ve probably used him less than 5 times since that nerf. I also have a few good 7 star skill champs so I don’t miss him as much. I do miss what we had when he was whole, that’s for sure. Lastly trello board? I haven’t heard any mention of that board since zemo was nerfed and it was the only reason given for why he didn’t deserve compensation. You’ll never get me to agree that anything surrounding zemo was ok.
Having said all that, bugs do happen all the time. We know this, and no one should be shocked. This is why everything before your comparison was more than adequate. Oof
Oh no @kabamJaxSucks! Your answer was good enough til you mentioned Kraven, and let me explain why. The controversy that this originally created because most people thought zemo deserved it was more than substantial. Almost no one plays Kraven. I liked your answer til you gave the comparison. It’s almost like throwing salt on an open wound. I was one of those people upset by that change and greatly upset. I literally rank 5’d him whatever that holiday sale was a ways back because I loved that you could play him multiple ways. Now he’s not as versatile and to me not as fun. I’ve probably used him less than 5 times since that nerf. I also have a few good 7 star skill champs so I don’t miss him as much. I do miss what we had when he was whole, that’s for sure. Lastly trello board? I haven’t heard any mention of that board since zemo was nerfed and it was the only reason given for why he didn’t deserve compensation. You’ll never get me to agree that anything surrounding zemo was ok.
Having said all that, bugs do happen all the time. We know this, and no one should be shocked. This is why everything before your comparison was more than adequate. Oof
Considering the fact that they’re not confiming this as a bug, I’m more than willing to bet it’s just another way to weaken the root mechanic, possibly to make Zemo less effective in Necro, but that’s still something we have to see.
Oh no @kabamJaxSucks! Your answer was good enough til you mentioned Kraven, and let me explain why. The controversy that this originally created because most people thought zemo deserved it was more than substantial. Almost no one plays Kraven. I liked your answer til you gave the comparison. It’s almost like throwing salt on an open wound. I was one of those people upset by that change and greatly upset. I literally rank 5’d him whatever that holiday sale was a ways back because I loved that you could play him multiple ways. Now he’s not as versatile and to me not as fun. I’ve probably used him less than 5 times since that nerf. I also have a few good 7 star skill champs so I don’t miss him as much. I do miss what we had when he was whole, that’s for sure. Lastly trello board? I haven’t heard any mention of that board since zemo was nerfed and it was the only reason given for why he didn’t deserve compensation. You’ll never get me to agree that anything surrounding zemo was ok.
Having said all that, bugs do happen all the time. We know this, and no one should be shocked. This is why everything before your comparison was more than adequate. Oof
Considering the fact that they’re not confiming this as a bug, I’m more than willing to bet it’s just another way to weaken the root mechanic, possibly to make Zemo less effective in Necro, but that’s still something we have to see.
I highly doubt it was intended to affect Zemo. To me it just looks like collateral damage from trying to change the AI too much.
Oh no @kabamJaxSucks! Your answer was good enough til you mentioned Kraven, and let me explain why. The controversy that this originally created because most people thought zemo deserved it was more than substantial. Almost no one plays Kraven. I liked your answer til you gave the comparison. It’s almost like throwing salt on an open wound. I was one of those people upset by that change and greatly upset. I literally rank 5’d him whatever that holiday sale was a ways back because I loved that you could play him multiple ways. Now he’s not as versatile and to me not as fun. I’ve probably used him less than 5 times since that nerf. I also have a few good 7 star skill champs so I don’t miss him as much. I do miss what we had when he was whole, that’s for sure. Lastly trello board? I haven’t heard any mention of that board since zemo was nerfed and it was the only reason given for why he didn’t deserve compensation. You’ll never get me to agree that anything surrounding zemo was ok.
Having said all that, bugs do happen all the time. We know this, and no one should be shocked. This is why everything before your comparison was more than adequate. Oof
Considering the fact that they’re not confiming this as a bug, I’m more than willing to bet it’s just another way to weaken the root mechanic, possibly to make Zemo less effective in Necro, but that’s still something we have to see.
I highly doubt it was intended to affect Zemo. To me it just looks like collateral damage from trying to change the AI too much.
Eitherway I keep testing and the opponents will not let down their block, this is terrible for him. I saw @Pikolu saying "you should stop attacking after the first medium" nah, they should let go of block. Zemo’s damage is trash already, you DO NOT need to nerf it further by not allowing players to place 31 bleeds per sp2 rotation.
@Demonzfyre Exactly what you just said, let us know it’s actually a bug and that he’s gonna pass it on to the team 🤦🏻♂️
I thought the comment about not posting in bugs and known issues was because threads get buried and you get no response on the issues.
I don't know if you're trolling or just don't understand how things work. Miike doesn't determine what is or isn't a bug. You can't determine anything from what's presented here honestly. It's a 14 second clip and not even the entire fight and it's it's only 1 fight.
Miikes job is to now give this very thin piece of information to the devs and let them figure it out.
It's been stated dozens of times that just because a thread in the bugs section doesn't get a response, doesn't mean it hasn't been reported.
I mean, I can tell from the 1 frame in the post that the problem is AI blocking while rooted, which they shouldn't be doing.
Where does it say rooted defenders can't block while rooted?
It doesn't "say" anywhere, just like it doesn't "say" they're special locked while rooted, and it doesn't "say" that AI can't cancel moves into specials.
Some mechanics are established even if unwritten, and AI spamming heavies while rooted is one of them. This was a bug that's been patched previously too.
@Demonzfyre Exactly what you just said, let us know it’s actually a bug and that he’s gonna pass it on to the team 🤦🏻♂️
I thought the comment about not posting in bugs and known issues was because threads get buried and you get no response on the issues.
I don't know if you're trolling or just don't understand how things work. Miike doesn't determine what is or isn't a bug. You can't determine anything from what's presented here honestly. It's a 14 second clip and not even the entire fight and it's it's only 1 fight.
Miikes job is to now give this very thin piece of information to the devs and let them figure it out.
It's been stated dozens of times that just because a thread in the bugs section doesn't get a response, doesn't mean it hasn't been reported.
I mean, I can tell from the 1 frame in the post that the problem is AI blocking while rooted, which they shouldn't be doing.
Where does it say rooted defenders can't block while rooted?
It doesn't "say" anywhere, just like it doesn't "say" they're special locked while rooted, and it doesn't "say" that AI can't cancel moves into specials.
Some mechanics are established even if unwritten, and AI spamming heavies while rooted is one of them. This was a bug that's been patched previously too.
Defenders have always been able to block while rooted.
@Demonzfyre Exactly what you just said, let us know it’s actually a bug and that he’s gonna pass it on to the team 🤦🏻♂️
I thought the comment about not posting in bugs and known issues was because threads get buried and you get no response on the issues.
I don't know if you're trolling or just don't understand how things work. Miike doesn't determine what is or isn't a bug. You can't determine anything from what's presented here honestly. It's a 14 second clip and not even the entire fight and it's it's only 1 fight.
Miikes job is to now give this very thin piece of information to the devs and let them figure it out.
It's been stated dozens of times that just because a thread in the bugs section doesn't get a response, doesn't mean it hasn't been reported.
I mean, I can tell from the 1 frame in the post that the problem is AI blocking while rooted, which they shouldn't be doing.
Where does it say rooted defenders can't block while rooted?
It doesn't "say" anywhere, just like it doesn't "say" they're special locked while rooted, and it doesn't "say" that AI can't cancel moves into specials.
Some mechanics are established even if unwritten, and AI spamming heavies while rooted is one of them. This was a bug that's been patched previously too.
Defenders have always been able to block while rooted.
Well here's a link to an MSD video where he calls it a bug that's only on the content creator beta. I've certainly never noticed rooted defenders blocking, and Zemo's kit almost seems designed to exploit no blocking since that's the only way he throws 2 sp1s from 1 root.
@Demonzfyre Exactly what you just said, let us know it’s actually a bug and that he’s gonna pass it on to the team 🤦🏻♂️
I thought the comment about not posting in bugs and known issues was because threads get buried and you get no response on the issues.
I don't know if you're trolling or just don't understand how things work. Miike doesn't determine what is or isn't a bug. You can't determine anything from what's presented here honestly. It's a 14 second clip and not even the entire fight and it's it's only 1 fight.
Miikes job is to now give this very thin piece of information to the devs and let them figure it out.
It's been stated dozens of times that just because a thread in the bugs section doesn't get a response, doesn't mean it hasn't been reported.
I mean, I can tell from the 1 frame in the post that the problem is AI blocking while rooted, which they shouldn't be doing.
Where does it say rooted defenders can't block while rooted?
It doesn't "say" anywhere, just like it doesn't "say" they're special locked while rooted, and it doesn't "say" that AI can't cancel moves into specials.
Some mechanics are established even if unwritten, and AI spamming heavies while rooted is one of them. This was a bug that's been patched previously too.
Defenders have always been able to block while rooted.
You know nothing about the root mechanic and you’re speaking off topic, since we are only discussing defenders letting go of the block after the first hit vs not doing so.
Comments
I thought the comment about not posting in bugs and known issues was because threads get buried and you get no response on the issues.
The only real Zemo bug is the one I also made a thread on where he misses his first medium if the opponent ducks during their heavy animation.
Miikes job is to now give this very thin piece of information to the devs and let them figure it out.
It's been stated dozens of times that just because a thread in the bugs section doesn't get a response, doesn't mean it hasn't been reported.
@SecondSkriller , I think you’d get more traction if you toned down the aggressiveness and accusations a bit. It looks like you found a real issue but coming out the gate the way you did automatically turns some people against you.
For this issue, it would be nice to get some confirmation about whether this is an intended change or not and if it’s unintended, whether it is a true bug that needs fixed or if it’s just an unintended change but part of our “new normal” with the AI.
Jax/Miike - If you want people to use the bug forum I think you need to give at least some minimal feedback there. I know it’s not your job and I understand it would be more work but a simple “this has been reported to the team” and a followup - “this has been confirmed to be a bug” would go a long way. As it stands, the response of “we read and investigate all of them, we promise” isn’t enough to make people confident they’ve been heard so they come here to try to make sure it gets attention.
From what I’ve seen, the community does a good job explaining things to people that aren’t bugs when we can. Scrolling through a few pages there appear to be some legit bugs like Mr. sinister not healing from crits with no acknowledgment. If Mr . sinister was a more relevant champ I’d expect to see posts about that in the main forum to get some attention because that seems to be what works.
I also don’t believe there would have been RDTs for Kraven without that massive thread but that’s another topic all together.
I’m good at finding these problems but bad at handling them. I made the thread on Zemo and Kraven, who were both my first r5 champs, which you can see how that enraged me, I’m still salty about that ngl. Wish I could just have my Kraven back the way he was…
Having said all that, bugs do happen all the time. We know this, and no one should be shocked. This is why everything before your comparison was more than adequate. Oof
Some mechanics are established even if unwritten, and AI spamming heavies while rooted is one of them. This was a bug that's been patched previously too.