Here's a simple guide to help our bug submissions understand why a bug might be flagged to something other than Assigned.

• New - of course, this is your new bug and it hasn't been looked at yet
  
  Already Fixed - obsolete, will be removing this one eventually. Replaced by "Fixed in Dev" by request
  
  Fixed in Dev - Since our server/content teams work on private servers, our work is not available to players until an admin (namely, me) updates TessEQ2 with the latest binaries and content data. When a dev finishes fixing a bug >in development<, this is the status they set. You should not re-test bugs marked as Fixed in Dev, unless you have access to the development environment
  
  Fixed - Bug is fixed, and is live for you to test
  
  Server Specific - Bug does not exist on official EQ2Emulator server, so we cannot fix it ourselves
  
  Invalid - Bug was submitted with insufficient or invalid data to reproduce, and will be closed
  
  Duplicate - Bug has already been submitted by someone else. Search the Bug Tracker before submitting new bugs!
  
  Not Implemented - Feature not yet supported by EQ2Emulator, and is therefore not a bug. Search the Project Status before submitting new bugs! This is probably the most annoying but for us developers, next to duplicates.
  
  Not a Bug - Could be that your bug works as designed due to current EQ2Emulator limitations (like spawning cliffdiver hawks for you to kill rather than giving you molerats to summon them) and content will eventually be fixed. Not a Bug is generally a work-around for now.
  
  By Design - This is not a bug because that is the expected behavior based on EQ2 Live
  
  Deleted - Your bug has been removed from Bug Tracker due to one of the above reasons

A side-note about submitting bugs:
Every single bug submitted is appreciated, because it means you as a player took the time to open the /bug window and write it up. For this effort, the devs and I are extremely appreciative. However, you will slow us down and waste your own time submitting a bug that is already in the database, or for a feature that is not yet implemented.

Do yourself (and us) the favor, keep a browser window open to our Bug Tracker and Project Status modules, and simply search either for your alleged bug before you spend the time in that form. It takes you a lot longer to send the bug than for me to flag it Deleted

Thanks again for the continued bug reports!