STOBE Log Files

When STOBE is failing, the fastest fix is usually finding the right log first instead of guessing. This page keeps the useful STOBE, RE_Kenshi, and DwemerDistro log locations in one place.

Log Files

STOBE Mod Log

This is the first log to open for the STOBE mod itself.

Kenshi\mods\Stobe\Stobe.log

Use this when STOBE is not reacting in game, the hotkeys are failing, context capture looks wrong, or the mod is not talking to the backend correctly.

RE_Kenshi Log

This is the main loader-side log for the Kenshi runtime.

Kenshi\RE_Kenshi_log.txt

Use this when STOBE is not loading at all, `RE_Kenshi.exe` is failing to bring the plugin up, or the DLL integration looks broken before STOBE even starts normal runtime behavior.

STOBE Config Files

If the mod is loading but connecting to the wrong place or acting strangely after an update, also check the live STOBE config files:

Kenshi\mods\Stobe\Stobe.ini

Kenshi\mods\Stobe\StobeCustom.ini

`Stobe.ini` is the shipped baseline, while `StobeCustom.ini` keeps the user or runtime overrides that survive updates.

STOBE Server Logs

The current codebase exposes the main STOBE server logs through two real entry points:

  1. HerikaServer: Control Panel then the Server Logs tab.
  2. Distro Launcher: Debugging then Create Diagnostic File.

The HerikaServer side is embedding the STOBE distro debugger from the dashboard, and the launcher diagnostic export writes a summary file to:

Desktop\DwemerDistro-Diagnostics\diagnostics-YYYYMMDD-HHMMSS.txt

The STOBE log viewer code is currently reading from the HerikaServer log folder and surfaces these files:

  1. apache_error.log
  2. chim.log
  3. output_from_llm.log
  4. context_sent_to_llm.log
  5. output_to_plugin.log
  6. stt.log
  7. vision.log
  8. debugStream.log
  9. context_sent_to_llm_fast.log
  10. monitor.log
  11. service.log

In the launcher code, there are also direct live tail commands for Apache, XTTS, Chatterbox, PocketTTS, MeloTTS, Piper, localWhisper, and Parakeet logs. So if the launcher or server log views are not enough, the debugging tools are already wired to those service-specific logs too.