Play and share what you find
Tell us what you expected, what happened, and how to reproduce it. Include the version, device, language and orientation. Only share sanitized screenshots and logs.
An open project
You do not have to write code to help improve invade.io. GitHub is our meeting point: focused proposals, reproducible reports, and changes we can review together.
Tell us what you expected, what happened, and how to reproduce it. Include the version, device, language and orientation. Only share sanitized screenshots and logs.
Review translations, long text, contrast and controls. Reports from real devices are especially valuable for checking accessibility and ergonomics.
Contribute a fix, a regression test, or a clearer guide. A small, complete change is a great place to start.
Your first contribution
Browse the issues or open a proposal before changing major behavior. Ideas are not commitments to future releases.
Fork and branch from dev. Contribution PRs target dev; main is reserved for the release process.
Follow the development guide. Add a test for new logic or fixes and check affected languages and layouts.
Describe the motivation, result, and checks performed. For visual changes, include before/after images and the limits of device verification.
The project uses GDScript and the standard Godot 4.7.2 editor. Run it without credentials, publishing tools, or a server. The guide’s launch command disables telemetry for that run.
First-party code and assets are Apache-2.0. Keep attribution and third-party notices when redistributing. Report vulnerabilities privately, never in a public issue.
Use GitHub Issues for ordinary bugs. You can also get in touch by email. Do not include personal backups or private logs in public reports.
alegandro2507@gmail.com