Skip to content

The Owing — build of main

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 31 Aug 05:27

This is the rolling build of main, not a version. It is replaced by the next
push, it is whatever is being worked on today, and half-finished work is expected
in it. For the build that was decided to be worth publishing, take the
latest release; every
version ever cut is on the
downloads page.

Saves carry their own version and are migrated forward, so an existing character
survives the upgrade.

platform file first run
Linux TheOwing-linux-x86_64.zip chmod +x TheOwing.x86_64 && ./TheOwing.x86_64
Windows TheOwing-windows-x86_64.zip unsigned — SmartScreen warns once: More infoRun anyway
macOS TheOwing-macos-universal.zip unsigned — xattr -dr com.apple.quarantine "The Owing.app" before opening
Android TheOwing-android.apk adb install, or copy it over and allow unknown sources

The APK needs Android 7.0 or newer — that is Godot 4.7's own floor, not a
choice — and carries both 32-bit (armeabi-v7a) and 64-bit (arm64-v8a) ARM,
so any phone from 7.0 up can install it. It asks for OpenGL ES 3.0 and treats
Vulkan as optional, falling back on devices that have none.

There is no iOS build. It is written and commented out in
.github/workflows/ci.yml, because it never got past xcodebuild; the
reasoning is in D147.

Nothing here is code-signed, and nothing here will be: that needs a paid
developer identity per platform. Two consequences worth knowing before you
download rather than after:

  • Neither mobile build has been run on real hardware. Text size at phone
    DPI is the most likely thing to be wrong.

Which build is this? Every build stamps its own commit: the title screen shows
it in the bottom corner and Settings spells it out, as
v<version>+<date>.<commit>. Quote that in a bug report — the asset filenames are
the same in every release, so a downloaded copy cannot otherwise say which one it
came from.

On NixOS the Linux binary needs steam-run, or a patchelf --set-interpreter — see
BUILD.md.

  • The APK is signed with the project's own key, so it installs over an earlier
    build.
    It is still self-signed: installable, not trusted, and not a Play Store
    build. The first build after the key was introduced needed one uninstall; this is
    not that build.

Built from c8ad1b39d7b3a95160f9fc90da2b1b489c874202.