3.0 Known Issues Post Doesn't Mention Dark Knight's Darkside MP Drain Issues

[Hanz]

It's something to do with the way mp and dots/hp ticks are calculated. One is server side and one is player side. What's happening is your mp is refreshing twice instead of just the once causing the pm to drain (one refresh) then build up to what it should be (2nd refresh) the problem comes likes many of you have rightly said when you think you have enough mp to dark arts and then that 1st refresh comes in and removes enough mp to stop the ability firing off. Completely throwing you off your game. Or when you do run low of pm and it ticks off dark side. The mp mechanic is exactly as it should be but instead of 2 refreshes there should be only the last one. Give them time, they will fix it. They acknowledged it, but nothing comes instantly. It's still in my eyes a great class, that just needs a little more tlc.

[Syfer22]

This bug hasn't been affecting me much at all. I guess if it ever gets acknowledged/fixed, I'll be godlike at MP management and never run out, LOL

[Zhexos]

Greetings,

We’ve been investigating the reports that a larger amount of MP was being consumed while under the effect of Dark Side when receiving effects such as Regen. As a result, we found that there was a bug with the display; however, the amount of MP consumption is correct.

The cause of this bug was that the process that syncs the information with the HUD was left out of the process for reducing MP from Dark Side, and the timing of HUD refresh was different when tick-type buffs were present and not present.

Currently if you are using Dark Side, HUD information is only being synced while recovering naturally. This means that the tick timing generated on the server-side that reduces MP by 265 due to the effect of Dark Side is not seen on the client-side, and what is seen on the client-side is only the +138 MP being recovered naturally. Due to this, the MP amount consumed is equal, but the way it appears is different. (It’s the same as when a bard is using a song. It falls, rises, falls…)

The display while receiving regen effects and such is accurate, so we are working to fix it in this way.
This fix is planned for Patch 3.05.

[NocX7]

Are you also going to fix the Dark Side aura graphical effects? The aura is missing the black flames as shown on the jobs skill trailer.

2 reports have been moved to the accepted bugs forums since the 23rd of June and it would be nice to have confirmation that this is also being worked on.

[Jamez82]

Thanks for the heads up. I've grown pretty accustomed to working around it but having it fixed will be awesome.

[Odstarva]

Are you also going to fix the Dark Side aura graphical effects? The aura is missing the black flames as shown on the jobs skill trailer.

2 reports have been moved to the accepted bugs forums since the 23rd of June and it would be nice to have confirmation that this is also being worked on.

Why has this not been confirmed yet!? Just give us a yes or a no! Please!

[MrSmiley]

Why has this not been confirmed yet!? Just give us a yes or a no! Please!

its in accepted bugs, I would assume that means there is plans to fix it, though lack of official word is a little odd yes.

[dark494]

its in accepted bugs, I would assume that means there is plans to fix it, though lack of official word is a little odd yes.

Actually posts are automatically moved to the accepted bugs forum as long as they have the proper template. I've made numerous bug reports that have gone completely ignored, or were merely patched/fixed at a random time without announcement and that bug report has sat and collected dust in the accepted bugs forum ever since.

[Nyalia]

Actually posts are automatically moved to the accepted bugs forum as long as they have the proper template. I've made numerous bug reports that have gone completely ignored, or were merely patched/fixed at a random time without announcement and that bug report has sat and collected dust in the accepted bugs forum ever since.

You clearly don't work in software development. There really is no reason for them to tell us what bugs they are or aren't fixing, or their timetables for such. Even if a fix is in the works, it might be internally complex to fix and not worth the time compared to higher-priority issues.

If SE works anything at all like my company, they likely have some supervisor, specialist, or development representative glance at the bugs reported on the forum that passed the initial "is this reported correctly" check (which is probably done by a forum moderator). The person looking at the issue might know the code in question at all, and even if they are a programmer/developer, the bug isn't necessarily in the area of the code they work with. The reviewer might have a reaction like, "Yup, that's definitely a bug," or "Nope, definitely working as designed," but there are other possible reactions too. "Sounds like a bug but I don't have the time to reproduce it right now to verify it's not just the submitter's computer going crazy," "I think that might be a bug, but I'm not sure and would have to ask around to see if it's actually a bug or not," or "Huh, that's weird. Someone will have to follow those steps later and see what happens!" When someone has to look at the code in any sort of depth, we would consider the bug "accepted." That doesn't mean it's accepted that the issue is definitely a bug and will be fixed. It means it might be, and someone has to look at it to make sure. It could turn out to actually work they way they intended it to, or to be a low-priority cosmetic issue that no one has the time to look into without taking time away from content updates. "Accepted" bugs likely go onto a list somewhere, possibly with a priority for how urgent it is that a development programmer examine it, and when someone has the time, they look at a few bugs on that list.

Software development isn't magic. Developers only have a finite amount of time. No one is going to work twelve-hour days to resolve some cosmetic bug in their software (okay, some coders will, but they're crazy!). Please don't be hostile to coders just because an issue you reported wasn't prioritized above everything else in their lives, or that they didn't track the bug back down the chain of contact (which might go something like moderator->reviewer->supervisor->specialist->developer->coder) to figure out who reported it to tell them personally about the resolution.

[dark494]

You clearly don't work in software development. *snip*

I've been a software developer for over 10 years. We have scrum items, tasks and stories, that get updated regularly to track and communicate all work progress to all parties at all times. Action items investigated and repro'd by the PM team is escalated up to devs as work items, and all parties are notified of such. There are "accepted bugs" that were filed years ago. Many of them were actual bugs that did eventually get addressed or investigated. Still there are plenty that are current bugs still, and are not ever addressed. But yet they remained forgotten in that forum. Did you even notice that SE has additional forums for:

- Unable to Verify
- Confirmed/Planning to Address
- Fixed
- Working as Intended

These board are very infrequently utilized, if at all. There are hundreds and hundreds of "accepted bugs" that just stale in that forum because nobody on their team is responsible enough to update them appropriately. It's sloppy and lazy, and a ticking time-bomb of an auditing nightmare.

Edit: And if you read their official sticky on their process flow for bug reporting, you would know that:

- Once reports with sufficient information have been checked, they will be moved to the Accepted Bugs forum.

- Bug reports moved to Accepted Bugs will be investigated and confirmed.

- As a result of investigating and testing, reports determined to be bugs will be moved to the Confirmed/Planning to Address forum and those determined to be a normal feature of the game will be moved to the Working as Intended forum.

- Once reports in the Confirmed/Planning to Address form have been fixed, they will be moved to the Fixed.

A process they clearly do not adhere to. So my original point, you went off tangentially on, still stands. Posts are automatically moved to the accepted bugs forum as long as they have the proper template. That does not mean they've acknowledged anything about the report, or plan to do anything about it.