Duvo Doctor
Latest Luduvo build: 47 36 known issues, checked against build 45 on 28 Sep 2026 View changelog →

Where your logs live

On Windows it's one folder. On Linux and macOS nobody has pinned it down yet, so this page says what's known and what isn't.

  • client.log is replaced every time Luduvo starts. Grab it straight after the game fails, before you try again. source
  • crash.log only arrived in build 44, on Windows. It's often empty, which just means nothing crashed that time. source 1source 2
  • For client problems, client.log and crash.log matter most. For Studio problems, studio.log and crash.log. source
  • Deleting client.log is harmless. Luduvo writes a new one next time. source

Windows

  1. The easiest way: use the Start menu

    Open the Start menu, type Luduvo, right-click it and choose Open file location. If that opens a folder of shortcuts, right-click the Luduvo shortcut and choose Open file location again. Your logs are in the folder that opens.

    Source: matt's tip, matt on avoiding Win + R

  2. Your logs: client.log, crash.log, launcher.log, app.log, studio.log and state.json

    %LocalAppData%\Luduvo\

    Or open File Explorer, click the address bar at the top, type the path above and press Enter.

    Source: matt's debug guide, File list

  3. Older zip installs from launch week and the alpha

    Next to the extracted Luduvo folder, for example Downloads\windows-x86_64\Luduvo\

    Open the folder you unzipped Luduvo into.

    Source: Nikhil on zip installs

  4. Your graphics settings: Settings.cfg

    %APPDATA%\Luduvo\Client\Settings.cfg

    Open File Explorer, click the address bar at the top, type %APPDATA%\Luduvo\Client and press Enter. Open Settings.cfg with Notepad.

    Source: Where Settings.cfg lives

Linux not documented

  1. The easiest way: run Luduvo from a terminal and copy what it prints

    luduvo --singleplayer

    Open a terminal, run the command, and when it fails, copy everything it printed. You can paste it straight into the Doctor.

    Source: Terminal output from a Fedora player

  2. Downloaded content

    ~/.local/share/Luduvo/Client/content

    Confirmed by several logs.

    Source: Linux log showing the path, Another

  3. Log files, probably somewhere under here unconfirmed

    ~/.local/share/Luduvo/

    Nobody has confirmed where Linux writes client.log, and some players say it doesn't write one at all.

    Source: Can't find it on Linux, No new logs on Linux

macOS not documented

  1. The game and Studio programs

    <your download>/Luduvo/bundle/usr/bin/

    LuduvoGame and LuduvoEditor live here. Running them from Terminal shows their output.

    Source: Mac error with the path, tunics on the Mac bundle

  2. Downloaded content, maybe unconfirmed

    ~/Library/Application Support/Luduvo/Client/content

    One error message showed /Library/Application Support/Luduvo. It may really be in your home folder's Library.

    Source: The error message

  3. Log files unconfirmed

    One Mac player could only find studio.log. crash.log was only announced for Windows.

    Source: Only studio.log found, crash.log is Windows only

Thanks to matt, whose Windows debug guide this page builds on. Last checked 28 Sep 2026.