Mole-Man true accuracy removed during Frenzy.

Mole Man: True Accuracy no longer remains active while in Frenzy mode.

It was bound to happen.

Comments

Going to need some rank down tickets.

That's why I ranked and used him because under 10 charges when activating Frenzy, he kept True Accuracy.

I waited a LONG time before ranking to ensure it wasn't a "bug" and after reading his abilities, it shouldn't be an issue keeping it the way it has worked for over a year now after his buff.

This is ridiculous if this change happens like this. It makes him useless a lot of the time and makes me not want him ranked. Better options and this change isn't needed as it doesn't make him overpowered.
Everyone said day 1 of his buff that it was a bug. Waiting for a long time doesn't change that. Also moleman is far from useless lmao. He's easily still a top 3 skill imo

Only top 4 now lol. Welcome to the top 3 Shang Chi

DrZola

Am I mad for thinking that Kabam should give out rank 4-3 rank down gems for 6* moleman specifically? I’ll preface that it doesn’t affect me personally, I have a rank 3 Moleman I use occasionally but never in serious content.

Leaving a bug up for over a year and then suddenly fixing doesn’t seem like a fair move to me. Not everyone goes on the forum, not everyone knows Moleman is bugged, Kabam are sometimes not super clear in their wording in game and I think after a year and four months it’s not unreasonable to assume it’s a broken description rather than a bug.

There’s no harm to the game economy giving out these rank down tickets, the change just neuters the utility of a champ that I’m sure a fair few players have ranked up to R4. The disappointment someone could feel after having rank 4d their Moleman as their first R4 *yesterday* after getting EoP and side quest R4 materials would be astounding with how rare the materials are right now.

I don’t know if Kabam have ever publicly said it’s a bug and may be fixed. If they have, then I may retract my statement. I’ve never seen Kabam comment on it and I’ve used the forum search function on all the mods that tend to comment on stuff like this. Never found anything related to Moleman.

There’s an argument for Moleman specific RTDs in general, but at minimum a rank 4 rank down ticket. Those resources are far too rare.

Maybe people should have double checked before ranking a champion, but really, this is a game and we play it to have fun. It would be a fair and kind thing for Kabam to do to offer rank down tickets here for a champion that has been bugged and left alone for a year and a 4 months. That implies a certain level of “everything is ok”. I am not one to ask for rank down tickets, I’m not even asking for them for me. I think it’s the right thing to do.

Reliance. That’s what makes a case like this different.

Where is it announced that Moleman was on the slab? Here? How many players are demented enough to regularly read forums? Was it on a banner at the top of the page, or tucked into a comment (and let’s be honest, a comment that likely got shuttled into the forums backwaters)? Was there an ingame message? Was it on YouTube?

It’s easier for players who are plugged in to keep abreast of a lot of the issues going on in-game, but that’s a pretty small minority. This has all the markings of the Drax “frame rate adjustment” years ago. Just apologize for leaving a bug in game for a year and a half and give players an option to shift resources spent elsewhere. It shouldn’t be hard.

Dr. Zola

Edit: Apparently, there was a thread discussing this from April….moved to Bugs and not addressed.

unknown

This content has been removed.

unknown

This content has been removed.

ANIMEniac

Moleman has rarely ever been the top option in the skill class unless he's one of your only champs. But he's always been a solid champ. The ability to keep True Accuracy while starting frenzy earlier always lead to a slightly trickier playstyle that was rewarding when done right.

With all the amazing updates coming in July, this one just hurts and really sours a lot of them. Please Kabam, update his text in his description and keep him the way he has been for over a year and call it a pro player bug that you actually ended up liking. It will make more folks happy and show more willingness to work with and listen to your player base. It's not a bug that elevates him over every single champ in the game. Save yourself the time of having to buff him again in a year when he rarely ever gets used.

unknown

This content has been removed.

Bugmat78

Am I mad for thinking that Kabam should give out rank 4-3 rank down gems for 6* moleman specifically? I’ll preface that it doesn’t affect me personally, I have a rank 3 Moleman I use occasionally but never in serious content.

Leaving a bug up for over a year and then suddenly fixing doesn’t seem like a fair move to me. Not everyone goes on the forum, not everyone knows Moleman is bugged, Kabam are sometimes not super clear in their wording in game and I think after a year and four months it’s not unreasonable to assume it’s a broken description rather than a bug.

There’s no harm to the game economy giving out these rank down tickets, the change just neuters the utility of a champ that I’m sure a fair few players have ranked up to R4. The disappointment someone could feel after having rank 4d their Moleman as their first R4 *yesterday* after getting EoP and side quest R4 materials would be astounding with how rare the materials are right now.

I don’t know if Kabam have ever publicly said it’s a bug and may be fixed. If they have, then I may retract my statement. I’ve never seen Kabam comment on it and I’ve used the forum search function on all the mods that tend to comment on stuff like this. Never found anything related to Moleman.

There’s an argument for Moleman specific RTDs in general, but at minimum a rank 4 rank down ticket. Those resources are far too rare.

Maybe people should have double checked before ranking a champion, but really, this is a game and we play it to have fun. It would be a fair and kind thing for Kabam to do to offer rank down tickets here for a champion that has been bugged and left alone for a year and a 4 months. That implies a certain level of “everything is ok”. I am not one to ask for rank down tickets, I’m not even asking for them for me. I think it’s the right thing to do.
Reliance. That’s what makes a case like this different.

Where is it announced that Moleman was on the slab? Here? How many players are demented enough to regularly read forums? Was it on a banner at the top of the page, or tucked into a comment (and let’s be honest, a comment that likely got shuttled into the forums backwaters)? Was there an ingame message? Was it on YouTube?

It’s easier for players who are plugged in to keep abreast of a lot of the issues going on in-game, but that’s a pretty small minority. This has all the markings of the Drax “frame rate adjustment” years ago. Just apologize for leaving a bug in game for a year and a half and give players an option to shift resources spent elsewhere. It shouldn’t be hard.

Dr. Zola

Edit: Apparently, there was a thread discussing this from April….moved to Bugs and not addressed.

Agreed - most players don't use the forums (or watch youtubers based on their views tbf) and it's clear that of those who do a significant number still didn't realize he was bugged

pseudosane

I dont really care about moleman that much, but Kabam never confirmed it was a bug, and that, i would argue, led us to believe it was intentional and here to stay. I never really use moleman, but this change does leave a bad taste.

GroundedWisdom

There's no expiration date on a bug. If it's not intended, then it's subject to fixing whenever.

SirGamesBond

I already knew this was a bug after his buff.
It was bound to get fixed or get a text update.
I r3d him knowing everything and do not regret ranking him. I was using him before his buff when people called him noodle, those were fun times lol.

The disgraceful thing about this fix is the Dead Silence from kabam,
The bug was brought to attention right from the beginning and not a single official response was made on the topic.

One statement from kabam would've changed this whole molegod fiasco right from the start. The word spreads like a virus in the community. But there was no word to spread, so nobody cared to discuss about it.

Strongly agree with bittersteel to get r4-r3 rankdowns for the people who may have taken their Moleman to r4, just after eop rewards dropped.
No rdts for any r3s or lower ranks and rarities.

unknown

This content has been removed.

AverageDesi

It’s literally the 2nd line in his abilities. While frenzy is NOT active and below 10 mm he gains true accuracy. This is a pretty embarrassing moment for the community but very expected
It was changd was it not?
No, it wasn't. This bug happened after the buff went live and has been acknowledged by Kabam for a long time.

Where

DrZola

There's no expiration date on a bug. If it's not intended, then it's subject to fixing whenever.

Sure. And if the team leaves it in place for a year and half, fails to respond to players asking about it and doesn’t explicitly call it out in easy to find locations, there’s also reliance that deserves redress.

Dr. Zola

GroundedWisdom

There's no expiration date on a bug. If it's not intended, then it's subject to fixing whenever.
Sure. And if the team leaves it in place for a year and half, fails to respond to players asking about it and doesn’t explicitly call it out in easy to find locations, there’s also reliance that deserves redress.

Dr. Zola

So because they didn't fix it immediately, they changed the fact that it was a bug?

Amms90

This one is simple.
Whether it’s a bug or not does not matter.

The only sensible solution is to change the description rather than change the ability.

That will not upset anybody.

He may not be as intended but neither is he game breaking.

Just change the description in the game and everyone’s happy.

Exactly what I'm thinking. Makes no sense to ruin the mole now.

Burrito2525

I have molegod at r4 sig 200, I’d actually consider a rank down ticket, i understand he doesn’t gain his true accuracy above 10 frenzy, but a very integral play style was when fighting evade champs to stay below 10 monster mass before going into frenzy to keep true strike… its not clear that it goes away WHILE active IF you pass 10 monster mass the way written. It’s a huge change to the way i would need to play him and his effectiveness. No doubt hes still a beast but it really neuters his effectiveness on evade/auto champs. It certainly would have influenced my r4 decision

MoShizzle

Why is Moleman True Accuracy being removed while in Frenzy mode? That takes away alot of his usefulness against sustaining critical hits against evade & autoblock champs! Especially his sp2 which often ends most fights!

Polygon

Dear Lord,

Thank goodness I didn’t r4 him. I feel for those that did. Definitely warrants rank down tickets as he’s practically going to be useless now. He already lost the shrug when in frenzy, but now this too? Even if it was a bug his utility is sacrificed almost entirely for damage now. Honestly they shouldve just kept him as is, he’s no way shape or form broken compared to other skill champs

Wfpkstevezilla

After 2 years it's too long. Change the description. The entire community knowledge on this champ is built on his current functionality. This is a pointless change and just as I was getting back into the game and considering a little drop on July 4th, I am just as ready to stop playing again. Stop punishing players for your long overdue bug fixes, Kabam. Let it rest.

unknown

This content has been removed.

unknown

This content has been removed.

GroundedWisdom

His True Accuracy has always fallen off at some point. Before the buff even. People were aware. They got a year and a half of use out of the bug. We can't fault them for fixing something that wasn't intentional.

Colinwhitworth69

Mole god having his godhood stripped away from him.
From a frequent on my team to another benchwarmer, at least he'll have Domino to keep him company

At least you're not overreacting.

Domino is awesome, btw.

TheLegend27

Should just change it back IMO. Not like he was some crazy broken strong champ. Frenzy + true accuracy is basically the only reason I have him at R3. Kinda ridiculous things like this are left in the game for so long before being "fixed".

unknown

This content has been removed.

GroundedWisdom

His True Accuracy has always fallen off at some point. Before the buff even. People were aware. They got a year and a half of use out of the bug. We can't fault them for fixing something that wasn't intentional.
bruh, you have no idea how he works. "at some point" lol.

Bruh. It's called wording.

Skiddy212

Disappointing but if its in his kit then so be it.

Should kabam have talked about this earlier? Correct. Should their be rank down tickets? I don't know. He was my second rank 3 and I wouldn't use the rank down ticket if i got it. Now if i rank 4'd him that might be a different story.

A bug in the game for over a year and a half is unacceptable though, especially if it wasn't adddressed or it was a long time ago, people forgot an continued to rank him during that period of time. Communication shouldve been better. Alas, kabam jax was not with us then an i will say forum communication has improved.

Interesting to see how good mole man remains now.

unknown

This content has been removed.

DrZola

There's no expiration date on a bug. If it's not intended, then it's subject to fixing whenever.
Sure. And if the team leaves it in place for a year and half, fails to respond to players asking about it and doesn’t explicitly call it out in easy to find locations, there’s also reliance that deserves redress.

Dr. Zola
So because they didn't fix it immediately, they changed the fact that it was a bug?

Strawmanning. I trust you can see there’s a fair gap between “immediately” and “a year and a half—with no readily findable comment.”

Dr. Zola

GroundedWisdom

There's no expiration date on a bug. If it's not intended, then it's subject to fixing whenever.
Sure. And if the team leaves it in place for a year and half, fails to respond to players asking about it and doesn’t explicitly call it out in easy to find locations, there’s also reliance that deserves redress.

Dr. Zola
So because they didn't fix it immediately, they changed the fact that it was a bug?
Strawmanning. I trust you can see there’s a fair gap between “immediately” and “a year and a half—with no readily findable comment.”

Dr. Zola

That's where I disagree. A bug is a bug, day 1 after, or 20 years after.