Even though it was myself being told to BUG and not ISSUE... still... it is something!

...but that wasn't a bug report. It was an issue. No one is complaining about the lack of issues being responded to/knowing when issues resolve.

Off-subject, I've never seen that message before, and I have artie pipes. Are you lighting them?

You don't need to light an arti pipe, they're always lit. :/

Yeah, but if you do light them they "go out" and it messes up your terrible nexus system. I had to pull the whole thing out and start over. It's fine though.

I have send bug reports that related to myself and received responses on those, more general ones do not get a response though.

Yea I lit them... which I reported in the report. I was asking specifically if the action of lighting an artie pipe is supposed to make them display a "gone out" message, as someone could, on some systems force you to light a pipe and possibly remove balance if you have those things tirggers (like my lua one, which was fixed)

yeah its futile to use the bug command, the only way they truly are looked at is through issue. Since they always look at issues.

No, it's NOT futile, and they do (sometimes) get to bugs right away... it's just hit-or-miss, and seems more like a lot of misses due to the no-response thing.

If there is something urgently wrong, and we really need to know about it immediately, then an ISSUE is the best way to contact us.

But if your issue is really a bug dressed up in issue-pyjamas, it really doesn't make the slightest bit of difference. In fact, it means that someone in the administration has to remove it from the issue list, and add it to the bug list. Yes, you'll get a message of receipt (asking you to BUG in future), but it doesn't mean that the bug will be dealt with more swiftly.

Yeah, when you get no response to a bug, it seems futile, and when you see a response and a fix within 2 days from issuing the same bug, it just tends to make you believe that issuing is the better route.

Ex. Bards in pits, it basically had to put off my offense for at least a month. Meaning I had to unenemy all bards, which gave my enemies a great advantage, using a bard to lead, that way no one sprung into any of my traps. It was bugged numerous times by numerous people, and for at least one month it was never fixed. I would test it one time a week to see if it was fixed. I had people all telling me it was bug abuse near the end, but by being so fed up with not being able to have a good trapping strategy, half the time I really didn't care. I can't call something bug abuse when there has been a month of bugs being reported and nothing done about them. /rant

QFT.

Speaking as a coder, I can legitimately say that unless it is a major bug, issuing will not result in the bug being fixed any faster. When we get an issue that is a bug, an Administrator will contact the issuer and let them know that it should be bugged in the future, and convert the issue into a bug.

The bug then goes into the queue with all the other "new" bugs to be classified and assigned a priority, at which point they are fixed based roughly on that priority (a hard bug to track down may take longer to fix). When a bug goes into that queue, it goes at the very end of it, so the time spent in transit from issue to bug actually just delays it being fixed by that much rather than speeding up the process.

I hear players talk about the inconsistency of bug fixing turnaround times, and this is based on 4 things:
1. The priority/importance of the bug.
2. The difficulty and time involved in tracking down the bug.
3. Multiple bug reports. Something you may have just recently bugged may have been bugged by someone else previously, and so be further in the queue or priority list.
4. Coding time available to fix bugs. If I'm working on a big coding project, I'll have less time available to fix bugs and so they'll be fixed at a slower rate (unless they are major bugs).

I know Fain and Morgy have to respond in that way, its part of the job.

But, the whole bards stuck in pit things was a very big issue. Beside making trackers "bug abusers" for using pits of any kind (if we left all our bards enemies, enemied), bards could be potentially stuck in a pit unless they wasted 10p for hyperactive (i think that was what they could do to get out).
Now, taking well over a month to fix something so serious in nature, in which it was abused by other orgs (by having bards lead raids, knowing they could claim and issue for bug abuse if they were not unenemied to trackers), or to have trackers ignore the plead of bards and going to town on them, or by bards who were not high enough in acrobatics being stuck in a pit forever.

It makes it more noticed it just seems when it is made an issue, and not just a brushed aside bug.


I still ya both though.

Sure, if a bug is serious enough you can and should issue. I'm certainly not disputing that. But the notion that issuing a bug will have the effect of it being resolved faster is generally wrong (and often the opposite).

In the case of the pit bug, well issue nor bug didn't make it get fixed any quicker, sadly though