new stuck location

[Pittminion]

(Standard): You are at: r1 lx192 ly32 i2049 cInside ox-449.99 oy199.30 oz-177.29 h50.6
(Standard): Q:0x70005808

Bam, griel nightforge's side.

[ArkoHighStar]

(Standard): You are at: r1 lx192 ly32 i2049 cInside ox-449.99 oy199.30 oz-177.29 h50.6
(Standard): Q:0x70005808

Bam, griel nightforge's side.

did you report as a bug, bec ause it might not get seen here

[Keeper]

stuck-spot coordinates

Okie dokie, I've added this to my bug queue. Next time please use the bug report feature. Thanks.

[Missing_Minds]

Okie dokie, I've added this to my bug queue. Next time please use the bug report feature. Thanks.

I know there have to be many many many spots.. but you know, if you actually forced Q to list each spot that is getting fixed, you'd probably have less duplicates coming in after the fact.

[Keeper]

I know there have to be many many many spots.. but you know, if you actually forced Q to list each spot that is getting fixed, you'd probably have less duplicates coming in after the fact.

I’ll pass. . . I prefer to apply my mean streak to the creation of traps and jump puzzles.

[Ustice]

Giving us access view/comment access to the bug tracker would help.

[Keeper]

Giving us access view/comment access to the bug tracker would help.

Um, no. That's a working tool for us. If we had to clean up our comments there for public consumption, our job would be pointlessly harder.

[DrAwkward]

Um, no. That's a working tool for us. If we had to clean up our comments there for public consumption, our job would be pointlessly harder.

Bug reporting a very complicated process.

1) User A encounters bug. Files bug report full of swearing and devoid of punctuation.
2) User A calms down a little and starts forum thread.
3) Quarion closes thread, for any number of good reasons.
4) User B reads thread, because it got on Dev Trackers when it was closed.
5) User B encounters bug, recalls thread and slaps forehead.
6) User B opens a clear and concise bug report.

If they opened up the bug tracker for all to see, they'd need to (as Keeper mentioned) edit out what the Devs thought of User A's bug report. Thats not even counting having to hide arcance confidential code snippets.
They'd also have to be able to hide bug reports of exploits.

These are the reasons (that I can think of) for us to want insight into your tracker:
1) See progress on items of importance to us.
(maybe with voting -- not that it matters, but it makes us feel better)
2) Help nail down bugs for you to squash.
3) Avoid pitfalls
4) Not open a bug you already knew about.
5) Clearly interpret the mad ramblings of an irate 10 year old into an identafiable bug.
(this costs extra, but we will)

Not unreasonable, but probably not feasable with your existing Tracker. Ah well.

[Keeper]

If they opened up the bug tracker for all to see, they'd need to (as Keeper mentioned) edit out what the Devs thought of User A's bug report. Thats not even counting having to hide arcance confidential code snippets.
They'd also have to be able to hide bug reports of exploits.

Not only is our bug tracker a giant database full of stuff that would be uninteresting and baffling to the vast majority of players, but we use it to track bugs in content that has not yet been released to the public. So, no, there is no chance that our bug database will ever be open for everyone to look at. We’re quite happy sorting through duplicate bugs.

[Dane_McArdy]

Not only is our bug tracker a giant database full of stuff that would be uninteresting and baffling to the vast majority of players, but we use it to track bugs in content that has not yet been released to the public. So, no, there is no chance that our bug database will ever be open for everyone to look at. We’re quite happy sorting through duplicate bugs.

You know that's only going to make people want to see it even more!

[Griphon]

Um, no. That's a working tool for us. If we had to clean up our comments there for public consumption, our job would be pointlessly harder.

HAHAHA...

I read this and thought of all the little snide comments and such that I make at my own work about our client companies, and how I'd be fired if they'd got into the 'wrong' hands.

I can only imagine some of the comments in this thing.

[Cahira]

Um, no. That's a working tool for us. If we had to clean up our comments there for public consumption, our job would be pointlessly harder.

At a job that I used to have (I left for a better--read: non-software--job), I was one of the few people in my section who could close bug reports...so people would bring them to me so that I would close them with their comments. I closed a bug report for another engineer once with his comments (as best I can remember them):

"This is not fixed. I merely put a Band-aid on the actual problem. This will need to actually be fixed by someone someday. I pity that person. It will probably be me. I pity me."

This "solution" actually made it past QA and is in the database for any customer to see...so long as they know how to find it or its number.

Then again...there was an engineer whose job it was (about 20 years ago) to go through the code that another engineer (who'd left for a different job) had written and remove the expletives and other 4-letter words. That story always made me giggle.

Yeah...weird stuff makes it into code and bug reports and closures.

[Angelus_dead]

We’re quite happy sorting through duplicate bugs.

That's not the issue.

The real issue is the bugs that go unreported because players assume someone else has already explained it to the devs.

To address that problem, the public-website list of known bugs should be better updated. Quite a lot of recent and old bugs which I've seen or seen mentioned are simply not listed. And in addition to real bugs, it should include unexpected behavior that some players assume are bugs.