invade.io documentation
Source reference: version 0.5.0, commit 05eec6f. This is not a statement of the version currently on Google Play.
Project home · Contributing · Google Play
Welcome to the reference for playing, developing, and maintaining invade.io. Choose a path below; you do not need mobile build tools or store credentials to start contributing.
Read these same guides with navigation and search on the
project website, or browse the
visual game tour. The website is built
from these canonical Markdown files, not a separately edited copy. Pages deploys
from main; this checkout can contain changes not published yet.
Play and understand
Section titled “Play and understand”| Guide | What you will find |
|---|---|
| Gameplay | Controls, game modes, continent rules, progression, settings, and backups |
| Platform integration | Android/iOS behavior, test-build installation, and device limitations |
| Privacy policy | The public policy for the distributed application |
Develop and contribute
Section titled “Develop and contribute”- Set up the project and run it without telemetry.
- Read the architecture overview to locate the relevant system.
- Use the testing guide to choose checks for your change.
- Follow CONTRIBUTING.md to open a focused PR against
dev. - Want to publish your own version? Read Make your own version.
Translations, UI review, physical-device reports, and documentation are useful contributions alongside code. The development guide includes localization and asset-generation workflows.
Build and maintain
Section titled “Build and maintain”| Guide | Scope |
|---|---|
| Releases | CI, artifact types, versioning, signing boundaries, and release recovery |
| Google Play publishing | Updating the existing Android application and configuring local exports |
| Play Store refresh | Localized copy, screenshot provenance, packaging, and Console review |
| Trailer | Rendering the Play Store trailer from the real game |
| Telemetry | Privacy settings, event schema, providers, and Debug/Release behavior |
| Security policy | Private reports, credentials, and maintainer review requirements |
| Website and documentation publishing | Astro/Starlight setup, content sources, web checks, and Pages deployment |
Project status
Section titled “Project status”Documentation describes the current checkout, not a guarantee about the version installed from a store. Check project.godot for the source version and GitHub releases for published build artifacts. A GitHub release is not automatic store submission.
| Area | Current scope |
|---|---|
| Android | Available on Google Play; Debug APKs use a separate app identifier |
| iOS | CI produces unsigned IPAs for SideStore testing, not App Store or TestFlight releases |
| Desktop | Linux/macOS development; desktop use is not a promise of a packaged desktop release |
| Game modes | Offline, single-player campaign, invasions, expeditions, and daily challenges |
| Progress | Local saves and manual JSON backups; no account or cloud synchronization |
| Online competition | No multiplayer, live PvP, or online leaderboard |
| Accessibility | Configurable presentation and alternate battle controls; mobile screen-reader support is not established |
The store material was fully recaptured on November 9 for source version 0.5.0; earlier captures were prepared against 0.3.1 and carried into 0.3.2. On October 30 the public policy described enabled telemetry defaults, while the Google Play listing still contained older descriptions and opt-in/no-collection wording. This source also defaults telemetry to enabled. These are dated public-page observations, not a live status feed or verification of the shipped binary. Before publishing, match the build, listing, policy, and Data safety declarations using the store update checklist.
Keeping these guides accurate
Section titled “Keeping these guides accurate”- Keep setup in Development, commands in Testing, gameplay rules in Gameplay, and signing policy in Releases.
- Write first-party guide prose in English. Localized game/store text and historical release payloads remain in their intended languages.
- Link to the source of a rule rather than copying constants into several guides.
- When changing behavior, update the affected guide and screenshots if necessary. Do not regenerate the store gallery for a text-only documentation change.
- After editing guides, validate the generated site with the website checks.
- Keep unsupported features distinct from implemented ones. An idea is not a release commitment, and an automated test is not physical-device certification.