We are currently experiencing issues with email delivery; this is being resolved as quickly as possible.

stationeers.de Mod workshop · Dominik1199
DE Sign in
  1. Home
  2. Wiki
  3. Getting started
  4. Reporting Bugs

Getting started

Reporting Bugs

Which log files there are, where they are stored and what belongs in a ticket so that a bug is found quickly.

Last changed: Oct 7, 2026

A ticket saying "doesn't work" and nothing else is about as helpful as a gas sensor in a vacuum. With the details below I find most bugs in minutes instead of days.

The log files

FileWhereWhat's in it
Player.log%USERPROFILE%\AppData\LocalLow\Rocketwerkz\rocketstation\the game's log, including errors from mods
Player-prev.logsame folderthe same from the previous start
LogOutput.log<game folder>\BepInEx\BepInEx and LaunchPad: which mods were loaded, in which version, and what went wrong along the way

You can type %USERPROFILE% into the Explorer address bar exactly like that, Windows fills in your user folder. On Steam the game folder is C:\Program Files (x86)\Steam\steamapps\common\Stationeers by default.

Warning

The logs are overwritten on the next game start. Player.log moves to Player-prev.log once, and on the start after that it is gone. Quit the game right after the bug and copy the files somewhere else.

Also helpful:

  • In the game console (F3), slp logs opens LaunchPad's mod log window. Right-clicking there copies the messages.
  • The status commands of my mods show the state of all devices at a glance: strom status, dampf status, schmelzofen status, bma status. Just copy the output into the ticket.

What belongs in a good ticket

  1. Game version. It is in <game folder>\rocketstation_Data\StreamingAssets\version.ini in the UPDATEVERSION line, for example 0.2.6428.27798.
  2. Mod and mod version. Shown in LaunchPad's mod list and on the Workshop page.
  3. BepInEx and LaunchPad version. At the top of LogOutput.log (BepInEx 5.4.23.5, Loading [StationeersLaunchPad 1.0.0]).
  4. Single player or multiplayer? And if multiplayer: were you the host, another player, or is a dedicated server running?
  5. Other mods. The easiest way is to attach the file Documents\My Games\Stationeers\profiles\my mods.xml.
  6. Steps to reproduce. What did you build, connect, press? In which order?
  7. Expected and actual. What should have happened, what did happen?
  8. Logs. Player.log and LogOutput.log from the start in which the bug occurred.
  9. Screenshot of the device, the display, the error message.
  10. Settings, if changed: the mod's BepInEx\config\<ModID>.cfg file, e.g. dominik1199.stromtechnik.cfg.
  11. Save, if the bug can't be reproduced any other way: the .save file from Documents\My Games\Stationeers\saves\<world name>\.

Example

Mod: Power Engineering 1.0.0
Game: 0.2.6428.27798, BepInEx 5.4.23.5, LaunchPad 1.0.0
Mode: multiplayer, I am the host, one other player
Other mods: Barren Stacks, World Map (my mods.xml attached)

Steps:
1. Built a Gas Generator 25 kW on a frame, connected fuel and exhaust pipe at the back
2. Output 1 with heavy cable to a network with 3 Wall Heaters
3. Pressed START, main switch EIN (on)

Expected: engine runs, output 1 delivers power
Actual: display shows "EXHAUST BLOCKED – empty exhaust pipe", LED Störung (fault) red
Attached: Player.log, LogOutput.log, screenshot of the display

Before you write a ticket

  • Is the mod in the active mod pack?
  • Is the same mod running twice, once locally and once from the Workshop?
  • In multiplayer, does everyone have the same version? See Multiplayer.
  • Is the answer already in the mod's guide under "Troubleshooting"?

One bug, one ticket

Two problems with two mods are two tickets. That way nothing gets mixed up and each one can be closed on its own. Requests for new features don't belong in a ticket, but in the Mod wishes section.

Found a mistake? Let us know. Support
Esc
↑ ↓ selectEnter open/ opens search anywhere