An open project

There’s more than one way to conquer.

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.

01

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.

02

Make it clearer for more people

Review translations, long text, contrast and controls. Reports from real devices are especially valuable for checking accessibility and ergonomics.

03

Make the project better

Contribute a fix, a regression test, or a clearer guide. A small, complete change is a great place to start.

Your first contribution

From a first look to your first PR.

  1. Find a focused change

    Browse the issues or open a proposal before changing major behavior. Ideas are not commitments to future releases.

  2. Start from dev

    Fork and branch from dev. Contribution PRs target dev; main is reserved for the release process.

  3. Run and verify

    Follow the development guide. Add a test for new logic or fixes and check affected languages and layouts.

  4. Explain your contribution

    Describe the motivation, result, and checks performed. For visual changes, include before/after images and the limits of device verification.

Godot. Git. A little curiosity.

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.

Open also means responsible.

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.

Need help as a player?

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