[New Users] Please note that all new users need to be approved before posting. This process can take up to 24 hours. Thank you for your patience.
Check out the v.255 - The Dark Ride: Ride or DIe Patch Notes
here!
Kanna's Vanquisher's Charm
Bug type: Functionality
Brief bug summary: When using Vanquisher's Charm as a Kanna, it did less damage after the Heroes of Maple patch went live for no reason.
More details: There is one account of a Kanna going from 35-40 mils vs hellux to 25-30 mils vs hellux, I personally went from 7-8 mil crits to 6 mil crits.
Character name: Misaku4
Character level: 217
Character job: Kanna
World name: Windia
Date and time of the incident: Right after the Heroes of Maple patch on June 22nd went live. And every time using the move afterwards.
I didn't want to submit a bug report at first since it had been present in a thread on the old forms, but with this receiving zero recognition or attempts to fix it I am submitting a bug report about this again. Feel free to take it down if you guys have started working on fixing it; if not, then please make fixing the glitch by next week's maintenance a priority. Kannas have had to wait for far too long to get this fixed.
Comments
First reported in this thread discussing multiple Kanna bugs that appeared in the same patch.
Later it got its own bug report thread: http://maplestory.nexon.net/community#/showthread.php?1542599-SKILL-Kanna-damage-output-is-lower
(Note that those threads mention that damage on all skills is lower, not just Vanquisher's Charm. They hint at a problem with Kanna's damage formula, but as far as I know no-one has figured out what, exactly, changed with it.)
That's an unrealistic request. They don't fix bugs in under a week unless it's a very easy fix (typo) or a gamebreaking bug.
I'd be happy if they fix Kanna's damage at the next Game Update (patch), which we expect to be October 19th.
Well, for 2 months investigation and they still have no solution.
so, I assume they dont even want to fix it at all.
It's been almost 5 months since this bug has been in place, yet we haven't gotten any update on this getting fixed or even looked at.
This has honestly gotten to the point of stupidity.