Joined: Wed May 17, 2006 10:12 pm
Posts: 465
Location: Mead, Wa
|
Hi folks,
You've been doing a fantastic job with the ticket submissions. We're to the point now where most of the tickets that need logs have them attached. That makes the process as smooth as it can be, and it really makes a difference. I would like to pass along a few comments and requests from the Tech Team, and we'll also cover some of the questions I've seen here in the forums.
The first item is a note to please exit the game and make sure the process is no longer running before zipping up your logs (Thanks for bringing this up, Modi  ). This is very important because some of the log entries buffer up in memory and are periodically flushed to file. If they don't exit first, important information may not yet have been written to the file on disk at the time you zip up your logs if the game is still running. This is also good to keep in mind if you're alt+F4 happy. When exiting the game to zip up your logs, it's always best to exit with the 'X' button on the Taskbar.
The next item is a request directly from the Tech Team, and it goes hand in hand with the previous item. Simply put, please exit the game as soon as you see the bug you are going to report. This ensures that the bug will be in the most recent session, and it will almost always save the person that is looking at your logs a great deal of time. The sooner the bug can be found in the logs, the sooner it can be fixed. It can sometimes take quite a while to backtrack through a game session in the logs looking for what the fixer needs to see, especially if there's a lot of gameplay between when you saw the bug and when you left the game. Marathon game session logs with eleven bugs from three different Ages can make it quite difficult for the fixer to find what you're reporting. The time it takes you to exit, zip up logs and return to game is time well spent, and is a worthy investment in the quality of your logs.
Lastly, If you're not going to log the bug right away (which we would prefer that you do), exit the game, zip up your logs and name them something relevant so that you'll know which set of logs go with which bug you're reporting. Unfortunately, we've gotten Developer feedback on a few bugs saying "This bug is supposed to be in (insert Age here), but the logs only contain (insert something other than that Age here)."
Thanks for your time,
Gregbert
|
|
Login
FAQ
Search
