Versions & review notes
During this guide's October 17 source review, v1.0.17 was the newest upstream source tag checked, while GitHub's latest-Release endpoint still resolved to v1.0.1. These are different signals, not interchangeable download recommendations. A community build also has its own build number and input requirements.
Source tag, release and package are different
| Label | What it identifies | What it does not prove |
|---|---|---|
| Git tag / commit | A source snapshot | That a ready-to-install binary exists |
| GitHub Release | A published release entry and its assets | That it matches the newest source tag |
| Clean shell | Open-source packaging input | That it contains a playable game |
| Community build number | One community workflow's output | That it is an upstream official package |
| Prepared-input manifest | A specific set of build inputs and checksums | That all future source revisions remain compatible |
Avoid a “latest IPA” button which silently chooses one of these on the user's behalf. Read the release body and the asset name, then follow the installation guide for that exact route.
October 17, 2026: first guide edition
This edition covers device and RAM requirements, the supplementary texture pack, Xcode and Windows routes, community Actions builds, native Mac setup, resource import, controls, backup paths and known errors.
It separates two unrelated compatibility choices: chip-dependent texture support and OS-dependent Metal API builds. It also distinguishes locally built Mac apps that depend on a workspace from community standalone packages.
For Android, the review includes community source development and a developer's gameplay notebook. No stable consumer APK or independent phone benchmark is claimed by this site.
How to update without losing your bearings
- Back up your entire current
savefolder before changing an app package. - Record the build you are leaving and the build you intend to install.
- Read changes affecting executable rewriting, shaders and prepared inputs. Regenerate version-sensitive inputs when instructed.
- Confirm the correct OS target and whether your device still needs pack metadata.
- Refresh or replace the package using its own instructions. Do not delete the app as a routine signing step without a backup.
See save-file precautions and troubleshooting if the new package cannot see resources or existing progress.
Where to verify newer changes
Use upstream tags, Releases and the exact workflow or fork you are using. The dates on this guide describe a source review, not an automated promise that the project has not changed since.
Frequently Asked Questions
Which number should I check before installing?
Record the source tag or commit, the package's own build number, its iOS/macOS compatibility target and its required input manifest. One latest label does not establish all four.
Is this a live project-status feed?
No. This first edition is a dated documentation review. Follow the original repository for changes made after that date; a new tag or fork commit is not automatically reflected here.