Support

Everything — settings and level progress — lives in a single file called settings.conf. There are no separate save files.

GNU/Linux	~/.config/moonflick/ (or $XDG_CONFIG_HOME/moonflick/)
macOS	~/Library/Application Support/moonflick/
Windows	%APPDATA%\moonflick\

Screenshots taken with Print Screen land in a screenshots/ folder inside the same directory.

The game does not write a log file — everything is printed to the terminal (stderr). To capture a log, run the game from a terminal and redirect it:

moonflick 2> moonflick-log.txt

For more detail, set the environment variable MOONFLICK_LOG_LEVEL=debug first (levels: trace, debug, info, warn, error). The most useful lines appear right at startup:

• moonflick v0.0.1 starting — your version,
• SDL video backend: … — the display system,
• GPU device created: driver=… device=… — renderer and GPU.

On Windows, open a terminal in the game's install folder and start moonflick.exe the same way.

MOONFLICK has no crash reporter yet. If it crashes, the terminal output is the whole story — capture it as described above. A line beginning with ALWAYS_ASSERT failed: is exactly what we need to see, along with what you were doing when it happened.

The version is shown in the window title bar — for example moonflick v0.0.1. (There is no in-game version screen yet.)

The renderer picks a GPU backend automatically: Vulkan first, then Direct3D 12 on Windows, Metal on macOS. The startup log line GPU device created: driver=… device=… names what was chosen. Two things worth trying:

• Update your GPU drivers — most rendering issues end here.
• Force a specific backend with the SDL_GPU_DRIVER environment variable (vulkan or direct3d12).

If the device in that log line is Microsoft Basic Render Driver, the game is running on software rendering — common over remote desktop and in virtual machines, and slow by nature.

Gamepads are supported through SDL3. Keys and buttons can be rebound on the Input settings screen, and stick feel (dead-zone, sensitivity, response curve) on the Gamepad screen. If input is behaving strangely, use the Reset to defaults row on those screens — Graphics and Audio have one too.

Because progress lives inside settings.conf (see above), make a copy of that file before editing anything — and know that deleting it resets your settings and your level progress together.

Purchases, refunds, and Steam account problems are handled by Steam, not by us — we cannot process refunds. Start at help.steampowered.com. For everything about the game itself, use the form below.