Author Topic: Read This First  (Read 6771 times)


  • Developer
  • *
  • Status:
    • View Profile
    • Avorion
on: March 19, 2013, 04:16:07 PM
You found a bug? Ouch. I'll fix that as soon as possible.

Before you post, you should do the following:
  • Check if the problem is not yet answered in the FAQ
  • Make sure in the forum that it has not been reported yet and that your version of the game is actually the latest version.
  • Is it really a bug?
  • Is it reproducable? Can you repeat the steps that led to the unwanted behaviour or crash?
  • Use a separate thread for each bug.

If all these factors are OK, you can post the bug on the board, including whether it was the server or the client that crashed.
A Server Crash looks like this:
  • Connection Closed: Some Error on your screen
  • AvorionServer has stopped working
A Client Crash looks like this:
  • Avorion just closes
  • Command windows pop up
  • Avorion has stopped working

Always include the following information in the report:
  • A clear description of what happened.
  • Step-by-step instructions on how to reproduce the bug.
  • Your client and server log. Follow the instructions below on where to find them on your system.
  • Your system specs:
    • Operating System
    • CPU
    • GPU (if multiple GPUs, then all of them)

How to find your logs:
On Windows, you will find them in your %appdata%\AvorionDemo\ folder. Type %appdata% in your windows explorer's address bar to get there.
On Linux, you will find them in your ~/.avoriondemo folder.

The logs for the client are called clientlog XXXX.txt and the logs for the server are in the AvorionDemo\galaxies\[your galaxy name here]\ folder. They're called server XXXX.txt. XXXX is the timestamp of when you started that server. Look at the timestap, take the one where your game crashed or where you had trouble, and post it.

How to add your logs if they are too big for the forum:
Please post the contents of the logs on Then add the link to your post.
Try to create a new pastepin paste for each log file.

The more information you post in here, the easier you make it for us to fix those bugs!

I know bugs and crashes are annoying, but we're doing our best to keep up with your reports. It might not always be possible to fix everything at once, but we're doing the very best we can.
« Last Edit: February 04, 2017, 11:50:09 PM by thedamngod »
#define TRUE FALSE // happy debugging suckers

If you need help, please post in the forum, don't PM me. If there's something that only I can help you with, contact me via mail.