Godot Data Export Guard

Catch raw CSV export failures before release

Your game works in the editor. You export it, and a CSV-backed feature stops working. Godot normally imports .csv as translation data; if your GDScript reads the raw file with FileAccess, the original file may be absent from the export.

Godot Data Export Guard checks literal FileAccess data paths before release. It runs locally, never uploads your project, and never rewrites project files.

What the full kit checks

• Missing files referenced through literal res:// paths
• Risky CSV import settings and UTF-8 problems
• Raw files missing from a fresh Godot export ZIP
• Exported bytes that differ from the current source
• Unrelated ZIP files that should not be treated as Godot export packs

Included in the paid download

• guard.py — dependency-free Python CLI with text and JSON output plus CI exit codes
• Broken and fixed Godot 4 sample projects
• A repeatable release checklist
• An integration test covering actual exports and runtime behavior

Try the free demo below first. It scans the focused source-side CSV risk. The paid kit adds fresh export-pack verification, byte comparison, runnable samples, integration tests, and the release workflow.

Requirements

Python 3.9+. Godot 4 is required only for automatic fresh-export verification. Tested with Godot 4.7.2 on macOS; other platforms and Godot versions are not yet verified.

Important limit

The checker sees literal FileAccess res:// paths, not paths assembled at runtime or every Godot resource API. A clean report is not a guarantee. Always run the exported game before publishing.

One-time download. No telemetry, subscription, or account inside the tool. Code is MIT licensed.

Support and free source edition: GitHub repository.

AI disclosure: code and documentation were created with AI assistance, then tested with automated integration tests and real Godot exports. Graphics are original programmatic assets.