I believe that this was indeed a simple miscommunication. When the bug first arrived on Test, it did not seem that critical to have resolved immediately on Test since players could not actually reach Leader status, so I did not make a giant fuss about it (my mistake). It was just a normal bug that I expected would get fixed before going Live (like everyone else on Test I'm sure). Unfortunately, our bug description did not entail "every time someone zones" and simply said "on login". The coder fixed an issue, but it did not fix everything. Since Palladius was out of the office and I wasn't paying attention to all the issues going on ( not really my job [bad excuse?] ), it was never re-tested before the update hit Live.
From what I hear, Palladius will begin making/replying to posts with bug statuses. If done well, this method should be able to better track things before they go out the door.
Personally, I like all 3 methods. If the /bug report is 100% reproducible by us (your detailed steps are much appreciated!), then it should definately be "known" by the end of the day. If you post here, then as soon as the right people see it, it will become "known" very quickly. If you inform Palladius or I directly, and we can reproduce it, then it will become "known" quite efficiently.
The main issues are that I am not around all the time (I'm not on Test Server at this moment), so telling me directly may be interfered with for this reason. /bug reports are not always reliable, since, as you pointed out, they are 1-way and there is not a real method in place for us to inform you that your /bug report has been successfully noted (ie. the bug you found was successfully reproduced). And posting here has some kind of delay factor, since most of us do not sit around and read the forums all day long (except Blackguard! jk). :smileytongue:
While posting this, I think I've decided that the *safest* method would be to post here, then send a mail or /tell to Palladius (or me, if Palladius isn't around) with the name of the thread, and of course /bug it (include a link to the thread if one has been made). While this opinion may be unpopular to many, in my eyes it is the safest thing to do with large issues that CANNOT get to Live.
I think this method is already very Close to being in-use, except at the moment it is more of an improv'd version and not yet a refined method of generating issues.
oh, and btw, i slapped blackguard already for apologizing that the issue was not "caught" on Test. As ambiguous as it sounds, it most obviously was Noticed and Reported on Test (more than 1 post here on the forum detailing the issue should most definately be considered "caught"). it just was not "captured" ... or something like that...?
Sorry for my long post. With any luck I've encouraged one or two testers to make more posts here on the forums to document issues (or tell Palladius or I to make a post about it). Now we just need to find the best spot here on the forum to accumulate and consolidate all the issues so we know exactly where to look and post. But I'll leave that job up to Palladius! :smileyhappy:
Thanks Test!
You guys rock!
-nate
Message Edited by NatesQA on 05-27-2005 12:33 PM