Where Does EDuke32 Store Config and Mods?
EDuke32 Duke3D configs, logs, autoload mods and saves per OS.
Last updated
EDuke32 keeps configs and logs per OS roots. Windows stays in the game dir while Linux and macOS use XDG config. Autoload folders collect mods automatically.
Game data like group files may live in config on Linux. Logs sit beside configs with per-platform names. Flags tune every path at launch.
Where EDuke32 stores this, by platform
<game-dir>\eduke32.cfg
Game dir configs with logs beside and autoload for mods. Saves in the game dir. Flags override config and content paths.
~/.config/eduke32/eduke32.cfg
XDG configs with autoload beneath and legacy dot fallback. Game data may sit in config. Log beside configs.
~/.config/eduke32/eduke32.cfg
Same XDG style configs with autoload. Log under Library Logs. Legacy data fallback matches Linux.
Frequently asked questions
How do I back up EDuke32?
Copy the config file plus autoload folder with the game closed. Saves sit in the game dir on Windows. Restoring means putting both back before launch.
How do custom cfgs and mods work?
A config flag points at any file. Autoload can be disabled per run. Extra game dir flag layers more content. Keep mods in autoload for automatic pickup.
Notice an outdated path? Let us know.