|
|
Technical Support Questions about game technical support to the users of the community |
|
Thread Tools | Display Modes |
01-19-2008, 07:53 AM | #1 | ||
Duke
Join Date: Nov 2006
Location: 0x00CAFE
Posts: 3,366
|
How to write a correct error report
How to write a correct error report:
NOTE: This is taken from the Spanish forum (Thanks Arlick, Sunos and Adrianpf!) as a way to help users to post "qualified" error reports so we can solve them faster. This is, by no means, official or mandatory. It's an adapted version! The Spanish one is a LOT more agressive. PM me if you find any error... Threads should follow the next four compulsory sections, leaving the user the choice to complete the last one (Others) at will. It should be well "delimited" (meaning that you should respect the sections) and well explained: try to be as precise as you can, don't miss any detail. Posts should be as short, comprehensible and concise, but as it was previously stated try NOT to miss any detail you may think it was related to the problem. Avoid "leet talk" or abbreviations... It takes away valuable time that could be used to solve your problem! Say thanks! Users often do almost the impossible to solve your problems, but sometimes some tech. aspect is beyond our comprehension and we don't know the answer to it. You should understand that most of us aren't Engineers or that we don't have a PhD. on IT. If we ask you questions about any technological aspect it is because we need it. Try to follow our advices. Oh, and by the way, ONCE THE PROBLEM IS SOLVED YOU SHOULD INFORM IT. That's the only way we have to know if the solutions we tried were a complete failure or a huge success. It's the way we can help other people the next time! It will save us time, too. We also would like you to say thanks. We're not part of NGD neither advanced A.I. bots or the ultimate NPC's, there's somebody behind the screen. Here's the template you could use: Quote:
Useful Tools: The "Sunos' line" tool: This is JUST for Linux users. Past this on a console to get a file in the desktop with all the information we need: Quote:
Credits to Sunos. Dxdiag: Press the windows key + r to open the "Run" window. Then write "Dxdiag" and execute it. Save the information to a text file with the button "save information" and attach the file. I guess I don't need to explain it. :P Credits to Adrian on this one...
__________________
I don't have a solution, but I admire the problem. |
||
|
|