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 @sleimon You're delusional if you think he's better than Nick Fury, Shang Chi, Falcon, KP, Black Cat, Hit Monkey, Masacre, or even Aegon. I honestly never ranked my 6* Moleman because I knew he'd get fixed eventually but calling him a top 3 skill after this nerf is just straight up crazy. He loses all of his utility in exchange for damage, now. This makes him redundant in war where you need both in order to do a majority of fights.
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
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.
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 @sleimon You're delusional if you think he's better than Nick Fury, Shang Chi, Falcon, KP, Black Cat, Hit Monkey, Masacre, or even Aegon. I honestly never ranked my 6* Moleman because I knew he'd get fixed eventually but calling him a top 3 skill after this nerf is just straight up crazy. He loses all of his utility in exchange for damage, now. This makes him redundant in war where you need both in order to do a majority of fights. I don’t know if I’d still call him top 3, I agree that Shang and Fury are better than MM, but the rest I have to disagree with
If a new player comes in, reads the description of Moleman, and also plays Moleman, why is everyone just assuming that they should know that Moleman is bugged and the description is correct? Are we suggesting that the descriptions are infallible, because we know that's not true. Look at the updates. Even this update also includes an update to Nightcrawlers SP3 description, and Archangels description on poison during blocked hits. V33.3 includes this - Fixed error in Joe Fixit’s description where it stated he gained a Card on the first hit of a combo instead of the lastI strongly believe that it is incorrect to just assume players would know it's a bug with gameplay and not description. They may understand that the Champion does not work the way the description reads, but it's impossible to know what was intended from only what's currently in the game. @IKON we had the same thought at the same time it seems! Great minds think alike
If a new player comes in, reads the description of Moleman, and also plays Moleman, why is everyone just assuming that they should know that Moleman is bugged and the description is correct? Are we suggesting that the descriptions are infallible, because we know that's not true. Look at the updates. Even this update also includes an update to Nightcrawlers SP3 description, and Archangels description on poison during blocked hits. V33.3 includes this - Fixed error in Joe Fixit’s description where it stated he gained a Card on the first hit of a combo instead of the lastI strongly believe that it is incorrect to just assume players would know it's a bug with gameplay and not description. They may understand that the Champion does not work the way the description reads, but it's impossible to know what was intended from only what's currently in the game.
Knowingly attempt to exploit known bugs and you end up paying the price once said bug is fixed. What a shocker. I'm sure you'll point me to where Kabam confirmed this was a bug. Or I'm sure you can explain why we can assume all descriptions are correct when they get fixed monthly because there are mistakes, and because there are nodes that don't act according to their descriptions. I'm sure.
Knowingly attempt to exploit known bugs and you end up paying the price once said bug is fixed. What a shocker.
@GinjabredMonsta do you think it's ok that Kabam leave a bug unannounced for a year and 4 months, allow some to believe he is functioning in the game normally? It's not like this was a secret, the community has asked or discussed the bug hundreds of times on the forum. Kabam had every opportunity to drop by and confirm it was a bug. The description is mostly clear. I was pretty sure it was a bug, lots of others were too, but not everyone. If you just look at the amount of descriptions Kabam include in game that don't quite accurately represent what happens, like Surging Vengeance for example. Or like the way increased ability accuracy interacts with Apoc's shrug off counter, or Angela's debuff reduction interacts with increased debuff duration. Or hell, the update this month "Nightcrawler: Removed the mention of “Disorient” in the Special 3 description". Or here "Fixed error in Joe Fixit’s description where it stated he gained a Card on the first hit of a combo instead of the last" or here "Fixed description of ”A Present For You: Villain” node to indicate 200% instead of 2%" "Doctor Doom informed Dragon Man that he cannot borrow his SP1 Description". And that's only since January... Kabam gets descriptions wrong all the time. Kabam also have many vague descriptions in the game left to fix. How are we supposed to know which are vague and work properly, or which are bugs, when Kabam leave it for a year and 4 months without commenting on it? Why is it up to us to confirm and spread awareness that Moleman is bugged and be careful if you rank him? "The opponent uses specials in consecutive order from 1-3, restarting after SP3" This is surging vengeance. Now, we know because we've played it, that this means if they get pushed past SP2 before using SP1 then they hold to SP3 and use it immediately. The AI won't just go to SP3 and stay there because it's out of order. But why? That isn't explained in the description. Consecutive is 1, 2, 3. If you cut out 1 and 2, they can't use 3. It is logical to assume that the AI would either 1) use their Sp2 without their SP1 or 2) not use their SP3 at all because it's not following the order. In fact, the function of this node is entirely illogical because it has it both ways. The AI won't use it's SP2 because it's out of order, but it uses it's SP3 even though it is out of order. It is a bad and vague description. "While Frenzy is not active and Moleman is below 10 Monster mass, his heightened senses allow him to predict opponent movements granting him True Accuracy". This is the only line in his abilities pertaining to True Accuracy (TA). Taken alone, this is pretty cut and dry. If Frenzy is not active, or Moleman is above 10 MM, he won't get TA. However, take this with the above context that 1) this has never been confirmed as a bug by Kabam 2) it's been over 1 year and 4 months of business as usual and 3) Kabam have a history of vague descriptions, it is entirely logical to assume that maybe there's a mistake here. And yeah, I feel personally that I knew it was a bug. But I'm one of the more active members here, I interact a lot with the forum, Mods and other members of the community on Line and on the forums. We are the minority and in this case not representative of the wider community. Most people don't keep a close eye on the goings on of the game. Some may dip in and dip out, see that Kabam haven't said anything about the moleman bug and carry on. Some may not visit the forum, and assume that after a year and 4 months of business as normal that implies a level of "everything is ok here". It is a bug, and it should be fixed, but that doesn't address what the right thing to do is. Usually, I don't think bugs warrant RDTs. I don't think there's been a single issue that has needed RDTs in the last 5 years except Hood buff 1.0 off the top of my head. But with what I've explained above, with the amount of time gone where the bug is here, the lack of communication from kabam having never confirmed it was a buff and leaving us to wonder if everything is ok, and the fact that many descriptions are iffy in the game - I think it's a pretty clear case for RDTs. Had one or two of those factors been different, maybe I'd think alternatively, but they aren't. And after all of this, just think about the scale of the impact if Kabam did decide to do a pro player move in this scenario. A bug that seems to be accepted and left alone leads people to invest valuable resources into champions, maybe a $100 awakening gem, maybe a 15k unit champion selector. Maybe their first R4 champion ever. That champion's utility is all but removed. How does it negatively harm the game if Kabam issue moleman specific RDTs? If they caveat this with the statement that "this is an incredibly rare and unique situation and do not expect RDTs for any other bugs in the future being fixed, it's only due to the circumstances we find ourselves in." What is the harm? And why would this be anything other than the right thing to do, and make players happy, enjoy the game more and be more likely to play, spend and engage. Not to mention the wonders it would do for trust in Kabam.What do you think the downsides and the upsides are to either granting or denying RDTs here?
Knowingly attempt to exploit known bugs and you end up paying the price once said bug is fixed. What a shocker. I'm sure you'll point me to where Kabam confirmed this was a bug.
Knowingly attempt to exploit known bugs and you end up paying the price once said bug is fixed. What a shocker. Or I'm sure you can explain why we can assume all descriptions are correct when they get fixed monthly because there are mistakes, and because there are nodes that don't act according to their descriptions. I'm sure.
The Moleman Nerf is ridiculous after the amount of time that has passed. The justification for Kabam to send out rank down tickets is already justified. The state of the game is broken and I would say the time or motivation to play this game anymore is on fumes. Reading these forums to stay informed is also ridiculous at this point. The IOUs to address the game issues to include Moleman’s kit not performing as designed well over a year says a lot.For the R4 and R3 Moleman holders - or a beginner with a R5 - should absolutely be offered rank down tickets. It’s embarrassing in my opinion. Where was the urgency to fix this over a year ago? @Kabam Miike come on man - curious to hear if this was something done without the consideration of you and the team on the potential impact to players who opted to invest in a known problem the development team failed to address timely. 365 days is a long time. It was longer than that to see the first published fix from Kabam. Look forward to hear back from someone at Kabam. #RANKDOWNTICKETS
Knowingly attempt to exploit known bugs and you end up paying the price once said bug is fixed. What a shocker. I'm sure you'll point me to where Kabam confirmed this was a bug. Or I'm sure you can explain why we can assume all descriptions are correct when they get fixed monthly because there are mistakes, and because there are nodes that don't act according to their descriptions. I'm sure. Descriptions get fixed monthly, you say. How many months ago was moleman reworked? Wonder how that flew under the radar for so long despite having been mentioned repeatedly by players. Maybe the issue wasn't with the ability description? Just throwing out a possibility.Champion description is what a champion is advertised as, and is what players first see, assuming they actually take the time to read abilities, and therefore is what should be assumed as correct, rather than picking and choosing whichever side happens to be most convenient to you. If an ability description is incorrect, it usually does get fixed quickly after having been discovered, and I'd imagine is also infinitely easier to fix than the alternative, so they really had no reason to hold off for that long if the issue really was ability text.This is really just a repeat of the Doom/Wasp vs stun immunity bugfix. Now, try to remember how many rank-down tickets were handed out then, and that'll give you a good idea of how many will be given out this time around. Right, so no pointing to where Kabam said it was a bug. And your explanation of why we should take descriptions as accurate is “Kabam usually fix it”. Surging vengeance has been in the game for years. Night crawler’s sp3 description has been changed today after 5 years. So that explanation doesn’t hold. How come that hasn’t been fixed? So I’ll ask again:When did Kabam confirm it was a bug? And why should we assume all descriptions are accurate when some get changed after 5 years, and some aren’t changed at all, while Kabam haven’t addressed Moleman’s bug ever?
Knowingly attempt to exploit known bugs and you end up paying the price once said bug is fixed. What a shocker. I'm sure you'll point me to where Kabam confirmed this was a bug. Or I'm sure you can explain why we can assume all descriptions are correct when they get fixed monthly because there are mistakes, and because there are nodes that don't act according to their descriptions. I'm sure. Descriptions get fixed monthly, you say. How many months ago was moleman reworked? Wonder how that flew under the radar for so long despite having been mentioned repeatedly by players. Maybe the issue wasn't with the ability description? Just throwing out a possibility.Champion description is what a champion is advertised as, and is what players first see, assuming they actually take the time to read abilities, and therefore is what should be assumed as correct, rather than picking and choosing whichever side happens to be most convenient to you. If an ability description is incorrect, it usually does get fixed quickly after having been discovered, and I'd imagine is also infinitely easier to fix than the alternative, so they really had no reason to hold off for that long if the issue really was ability text.This is really just a repeat of the Doom/Wasp vs stun immunity bugfix. Now, try to remember how many rank-down tickets were handed out then, and that'll give you a good idea of how many will be given out this time around.
I don't see a need for this nerf, it's nowhere near the Ghost, Quake and Hercules that are broken champions.I used 140 characteristic stones on it, I also had the Nick Fury dup as an option for the R4 era, but I chose the Mole Man.My 6* R4, Apocalypse went up yesterday to R4.
Knowingly attempt to exploit known bugs and you end up paying the price once said bug is fixed. What a shocker. I'm sure you'll point me to where Kabam confirmed this was a bug. Or I'm sure you can explain why we can assume all descriptions are correct when they get fixed monthly because there are mistakes, and because there are nodes that don't act according to their descriptions. I'm sure. Descriptions get fixed monthly, you say. How many months ago was moleman reworked? Wonder how that flew under the radar for so long despite having been mentioned repeatedly by players. Maybe the issue wasn't with the ability description? Just throwing out a possibility.Champion description is what a champion is advertised as, and is what players first see, assuming they actually take the time to read abilities, and therefore is what should be assumed as correct, rather than picking and choosing whichever side happens to be most convenient to you. If an ability description is incorrect, it usually does get fixed quickly after having been discovered, and I'd imagine is also infinitely easier to fix than the alternative, so they really had no reason to hold off for that long if the issue really was ability text.This is really just a repeat of the Doom/Wasp vs stun immunity bugfix. Now, try to remember how many rank-down tickets were handed out then, and that'll give you a good idea of how many will be given out this time around. Right, so no pointing to where Kabam said it was a bug. And your explanation of why we should take descriptions as accurate is “Kabam usually fix it”. Surging vengeance has been in the game for years. Night crawler’s sp3 description has been changed today after 5 years. So that explanation doesn’t hold. How come that hasn’t been fixed? So I’ll ask again:When did Kabam confirm it was a bug? And why should we assume all descriptions are accurate when some get changed after 5 years, and some aren’t changed at all, while Kabam haven’t addressed Moleman’s bug ever? Surging Vengeance and Nightcrawler are cases of improving clarity, not fixing bugs. Nothing is malfunctioning with either of those abilities, whether in text or gameplay. Moleman's description is very clear and leaves no room for confusion, so there's really no comparison there. You’re saying that with the hindsight that Kabam confirmed it was a bug. Before yesterday there was a possibility that Kabam would announce “Moleman’s ability description is being fixed to say “when below 10 MM and not in frenzy MM gains a TA passive, this TA stays while in frenzy”. That goes against your reading of the situation, which is fine, but as Kabam never confirmed it either way, you cannot say that it’s clear because there’s a chance it was not right. If it was updated, then it would accurately reflect what happens in game. Forget for a moment that Moleman’s TA was a bug. What’s the difference between surging vengeance description being fixed to accurately reflect what happens in game, and Moleman’s description being updated to reflect what happens in game?
Knowingly attempt to exploit known bugs and you end up paying the price once said bug is fixed. What a shocker. I'm sure you'll point me to where Kabam confirmed this was a bug. Or I'm sure you can explain why we can assume all descriptions are correct when they get fixed monthly because there are mistakes, and because there are nodes that don't act according to their descriptions. I'm sure. Descriptions get fixed monthly, you say. How many months ago was moleman reworked? Wonder how that flew under the radar for so long despite having been mentioned repeatedly by players. Maybe the issue wasn't with the ability description? Just throwing out a possibility.Champion description is what a champion is advertised as, and is what players first see, assuming they actually take the time to read abilities, and therefore is what should be assumed as correct, rather than picking and choosing whichever side happens to be most convenient to you. If an ability description is incorrect, it usually does get fixed quickly after having been discovered, and I'd imagine is also infinitely easier to fix than the alternative, so they really had no reason to hold off for that long if the issue really was ability text.This is really just a repeat of the Doom/Wasp vs stun immunity bugfix. Now, try to remember how many rank-down tickets were handed out then, and that'll give you a good idea of how many will be given out this time around. Right, so no pointing to where Kabam said it was a bug. And your explanation of why we should take descriptions as accurate is “Kabam usually fix it”. Surging vengeance has been in the game for years. Night crawler’s sp3 description has been changed today after 5 years. So that explanation doesn’t hold. How come that hasn’t been fixed? So I’ll ask again:When did Kabam confirm it was a bug? And why should we assume all descriptions are accurate when some get changed after 5 years, and some aren’t changed at all, while Kabam haven’t addressed Moleman’s bug ever? Surging Vengeance and Nightcrawler are cases of improving clarity, not fixing bugs. Nothing is malfunctioning with either of those abilities, whether in text or gameplay. Moleman's description is very clear and leaves no room for confusion, so there's really no comparison there.
I have no issues with Kabam fixing a bug so that Moleman works as intended. If they would have responded to the many threads from players asking if this was working as intended the pending change would feel very different. All they had to say is something like "we are looking into this and we may have to make a change at some point if we determine that he is not working as intended." Players did their due diligence by bringing the matter to Kabam for clarification. Because Kabam failed on their end to communicate with the players they have created the current situation and they ought to take some responsibility for it. If the way that Moleman is working is gamebreaking, they should apologize and explain why this change is necessary for the stability of the game. If it is not gamebreaking they should acknowledge that they should have communicated when players brought up the issue ages ago, and that they will leave him as he is and change the description accordingly.Given Moleman's description, Kabam can justifiably make this change. But when dealing with real people who are also your customers, the fact that you can do something doesn't necessarily mean that you should do it. By not responding to the players when asked if this was intended they have made this much worse than it needed to be.