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

But Surging Vengeance doesn't misrepresent anything. Using a sp3 after sp1 is still in order. 3 always comes after 1. Again, the only thing that would change with updating SV's text is eliminating confusion as to how the ability functions, because the current text simply isn't clear enough. In your hypothetical, Moleman's text literally states something that the champion does not do. There is no confusion or clarification, it simply is a different ability than stated.

The issue with SV and NC are that their text can easily be misinterpreted. There is literally no way to interpret Moleman's text in a way that his gameplay is correctly represented.

Ryker

Moleman was my first rank 4 after completing the story mode.

This is basically a nerf reverting him back to having to decide between utility or damage.

I would expect rank down tickets so that I can rank up a different skill champ.

BigBlueOx

Or the text doesn’t accurately describe how he plays in game…

solopolo

But they are in alphabetical order. It isn't the entire alphabet, but that wasn't specified, which is precisely the issue with SV; lack of specification. Again, this comes down to interpretation. This isn't the case with Moleman. There is no way to understand "optional" in "While Frenzy is not active".

solopolo

The difference is that you've completely changed the way that Moleman's ability functions, both in text and gameplay. You've now created a lingering effect that only checks its condition upon initial activation rather than a continuous one that is only active under the conditions of Frenzy not being active AND Moleman being below 10 Monster Mass, and as a result the line you've added at the end is completely unnecessary because the True Accuracy wouldn't fall off upon activating Frenzy regardless.

Savage123456789

My question is this bug has not been around for a few days or week. It's been over a year. So, they had time to see the effect this bug had on the contest. Does that mean they saw it was game breaking based on the data they collected? Or was the bug a result of something else that they finally fixed which inadvertently fixed moleman as well, forcing them to post that change in the patch notes?. Why change the champion now when he was better before?

Graves_3

When frenzy is not active and moleman is under 10 monster mass, he gains TA.
Since it doesn’t explicitly state that he loses TA when frenzy activates, I can also interpret this as ‘when frenzy is not active and moleman is under 10 MM, he gains TA. When frenzy is activated, his TA stays active regardless of how many MM he has’
I know that’s not what’s in the game but dont you think people who assumed this as true are not wrong? Since that’s how he functioned in game. It could have very well been an omission in description on the part of kabam since they never said otherwise.

BigManOnCampus

Can we get a moment of silence for the late great "MoleGod" , he will be sorely missed 😭

solopolo

All you've managed to accomplish with thes posts is prove that you're in no position to nitpick kabam's wording, and you don't even realize it.

Allow me to break this down for you.

Surging Vengeance's issue is not about nitpicking definitions of any specific word, it's simply that the node doesn't mention what happens once the defender reaches 3 bars of power before using their sp2. It is missing information which results in confusion as to how the ability functions. The only change that needs to happen here is to add said missing information to the node description.

In order to fix Moleman there are 2 potential scenarios.

EITHER they change how the ability functions in order to fit the description, meaning the ability itself was not functioning as intended, and the description is accurate.

OR they alter the wording in order to match how the champion functions in game, meaning the issue was actually with the champion's text.

You've done neither. Instead you threw out both abilities and created an entirely new ability that's even better than both because you don't understand how to properly word an ability.

Regardless, your hypothetical has no place here. You're trying to create an entirely new scenario in which your point still fails to hold any ground and requires you to twist facts even further. Bottom line is, Moleman's issue has nothing to do with clarity like the other abilities you've mentioned so far, and can't be compared to any of them.

Whether Surging Vengeance's issue is an issue of incorrect wording by definition, or simply an oversight by Kabam, it is not at all an issue with the functionality of the node.

The_Chump

EITHER they change how the ability functions in order to fit the description, meaning the ability itself was not functioning as intended, and the description is accurate.

OR they alter the wording in order to match how the champion functions in game, meaning the issue was actually with the champion's text.

So you are admitting that the "bug" could have been with the functionality or that the issue coulda actually been w the champion's text, meaning the functionality coulda been correct.

All this says to me is that it really couldnt be clear to anyone if the champ was working as intended or bugged.

solopolo

Are you aware of what the word "clarity" means?

Nightcrawler is a case of clarity due to the fact that the "disorient" in his ability text does not refer to an existing game mechanic with the same name.

Surging Vengeance is a case of clarity due to the fact it's missing information in the node's description.

Moleman's ability is NOT a case of clarity due to the fact that his text literally contradicts what his abilities do in game.

solopolo

except for the fact that if the issue were with the ability text, as I said multiple times already, it would've already been fixed a long time ago considering the issue was brought up well over a year ago, and they have to reason to leave that to sit when tweaking an ability's description is much easier than having to go and alter game mechanics.

Molegod

please kabam dont do this, i use r3-4 skill gem for my mole man, i rank up mole man for this true acc still active while frenzy mode. please man dont do this. or u need to give back the R3-4 skill gem back:(

The_Chump

Exactly whatI was saying. We really couldnt know which they would decide to go with.

Sw0rdMaster

Either way, kabam had over a year to say if this is bug and will be fixed or the description is incorrect.

Neither has happened and players are left to use the champ as is.

J0eySn0w

I just need my rank down ticket. I never ranked mine until someone pointed out how he counters evade and autoblock if I activate frenzy under 10 monster mass. KP has been my man all this time that I didn’t care to even bother about Moleman. And when I just took mine up less than 2weeks ago because the alliance went praising his true accuracy. I’m not saying they should or should not make the change, but it was in the game too long so some of us who just pull the champ recently to think it’s normal. So just give me my resources back, I will use it on someone else.

GroundedWisdom

"Just a heads up. Incase you're taking advantage of any unintended outcomes, we're planning on fixing them."
Somehow that doesn't go over well.

H700

Cull is still god, the bad thing is that he doesn't resist blows of any kind, he's made of paper

The_Chump

Except for the fact that if the issue was functionality Kabam would have announced or responded to the many posts regarding it, and mentioned that he will eventually be fixed, right? No. So we could assume they would just fix the description error, but not say anything for over a year about it being a bug.

Burrito2525

Listen to this guy or he’s gonna have to change his forum name…

Seriously though kabamm gods.. kabam jax..looking at you mr reasonable.. keep him as is or issue rank down tickets (even sig backs?) as an r4s200 moleman owner, I didn’t take the decision lightly to pour resources into him. At the very least r4 rank downs. I think r3s are easy enough to come by now and he’s a great champ but many would have left him at r3 if you neuter him.

solopolo

Not really? We're all very well aware of how unresponsive they are with gameplay-related issues, so the fact that anyone is surprised at any lack of communication is hilarious. Y'all are sitting here acting based on the least likely scenarios simply because it suits you best and then want to complain when the 90% comes. That's completely your fault and no one else's.

SpiderVenom

after 16 months kabam has decided to fix him
i forgot that this was even a bug
i feel betrayed

Idyslim

Please reconsider this change. We love molegod as is 🙏

Masterpuff

“Just a heads up. Incase you’ve been using that unspecified discrepancy between the description and the actual game for the last year and a half, we are going to fix it despite not commenting on the issue throughout the year and a half it existed.”

Funny, i dont know why that did smooth right over with the community.

solopolo

Thanks for twisting my point once again. You're doing a great job at it.

Not once did I say anyone besides Kabam is at fault for Kabam's unresponsiveness, but go ahead and interpret that as you will.

solopolo

At this point there is nothing to fix, unless you're saying you're capable of inventing a time machine to send them back to send us a message that Moleman is in fact bugged.

The change itself is 100% justified and should've been expected, but people decided to ignore that and blow their resources regardless.

And somehow you manage to turn this into me saying Kabam's unresponsiveness was justified. Please.

Chomps

LMAO. So we know this isn't a text error, because they would have quickly fixed it, but we shouldnt expect them to take the same amount of time, or less, to post/respond that this is a functional bug. Hahaha you're a funny guy/gal.

If you can assume that an error in text would be fixed in a timely manner, then the community could assume Kabam could take that time to address this as a bug.

J0eySn0w

What about the many people that were not aware of this nor even heard about it? Many made decisions based on what they experienced personally and from what others said without ever hearing a disclaimer that this is only temporal. I would think they should know that certain changes need to be addressed right away or it can take on a new life or meaning.

solopolo

I look forward to your response about how I twisted your words to make you seem bad when really, your points are just bad to begin with.

Unnecessary but alright I guess.

Giving out RDTs doesn't fix Kabam's mistake, if anything all it does it encourage players to continue abusing publicly known bugs, and the next time a long-time bug is fixed the exact same problem will occur once again, just like it did with AA, just like it did with Doom/Wasp. Both sides are to be held accountable. You ranked up a champion? You don't get a do-over. You knew what you were getting into.

As for what Kabam should actually do, is fix their lack of communication rather than any band-aid fixes players will want to suggest. At the end of the day, they just need to let us know what's going on. If you ask me, whether or not a bug is present and in line to get fixed should be a given, but as far as whether or not the bug could've been fixed earlier, we don't know, because a lot of thing could either 1. get in the way of fixing certain bugs, or 2. simply be higher priority fixes, and this does need to be communicated with players.

GroundedWisdom

What part of his description, pre-buff and post-buff, indicated that the interaction was intended?