Builds and artifacts
What each Forge target produces, what a build can and cannot reach, the limits on balaurengine.org, and how long downloads are kept.
On this page
A build is one commit of one project, exported once per target. Each target runs on its own, in its own container, and produces exactly one file.
Targets
| Target | You download | Signed with |
|---|---|---|
linux-x64 |
the executable, or a .zip of it and what sits beside it |
— |
linux-arm64 |
the executable, or a .zip of it and what sits beside it |
— |
macos-universal |
a universal executable, for Intel and Apple silicon, or a .zip of it and what sits beside it |
macOS, then notarised |
windows-x64 |
the .exe, or a .zip of it and what sits beside it |
Windows |
windows-arm64 |
the .exe, or a .zip of it and what sits beside it |
Windows |
ios |
an archive of the app, packaged for the App Store | iOS |
android |
an .apk, an App Bundle (.aab), or both — see Build settings |
Android |
web |
a .zip with index.html, the wasm and the export pack — upload it as is |
— |
Every target is exported on Linux, macOS and iOS included: an export fuses your scripts, scenes and assets onto a prebuilt engine for that platform, so no compiler for it has to run.
Build settings
A project's admins set what its builds do on its tabs. The same fields are
on the API as PATCH /api/v1/forge/projects/:id.
- Repository → Default branch. The branch a manual build uses, picked from the repository's branches.
- Repository → Link another repository. One from your GitHub, one by URL, or, for a linked project, the copy on Forge as its own. Linking a project kept on Forge replaces its repository there; push its branches to the new one first.
- Engine → Version. Picked from a list.
latestfollows the engine's newest release. Pin a version such as0.4.1and the same commit builds the same bits next month.nightlyfollows the nightly build. - Targets. The platforms every build exports. Android is two tiles:
Android APK installs on a device; itch.io and sideloading take it.
Android AAB is what Google Play takes. Both is the default: one build
makes two artifacts, each signed with your Android key, each with its own
Publish button. The App Bundle shows on the build as
android (aab). - Settings → Name. The project's URL:
/projects/<username>/<name>, and/git/<username>/<name>.gitfor a project kept on Forge. Lowercase letters and digits joined by-or_, unique among your projects. Renaming moves both. - Settings → Public. Anyone, signed in or not, sees its dashboard, plays its web build and can import it. Only members clone, build and push.
- Settings → Delete. Type the project's name. Its builds, credentials and repository on this site go. This month's builds still count toward your free builds.
[export] in the game's project.toml is used as committed.
What a build can reach
- Your repository, one commit deep, read-only. Forge clones the pushed commit — or the head of the branch you asked for — and nothing else.
- No network. A build cannot download a package, fetch an asset or call an API. Everything the export needs has to be in the repository.
- Submodules and Git LFS, fetched before the build. Submodules are checked
out one commit deep, recursively, and LFS files are pulled, in submodules
too — so assets kept in LFS arrive as assets. Submodules have to be reachable
over
https: from GitHub through the same App access as the project, or public. A submodule pointing at a local path orfile://is refused.
Dependencies
A build copies the dependencies project.lock names before the sandbox starts.
- Each
[[dependency]]lands indeps/<alias>/at its lockedrev, from the project kept on Forge. - A sha256 that differs from the lock's fails the build, naming the dependency.
- So does a tree with a symlink or a submodule, or a project your account may not read.
- Nothing in a dependency runs, and the build still has no network.
Reading a build's page
Each target's card shows its status, and once it succeeds:
- cached — the engine template for this target and version was already on the builder, which is most of why a warm build takes seconds.
- signed or unsigned — and when unsigned, what signing would need, with a link to set it up.
- the file's size, and Download.
- a Publish to … button for each store you have set up that takes this target. See Stores.
Under the cards is the build's Output: the clone, then the export, line by line as it happens. A failed target's reason is on its card; the lines above it in the output say why. Troubleshooting has the common ones.
A build is queued until a builder picks it up, running while any target
is, and succeeded or failed once all of them have finished — failed if
any one did.
Limits on balaurengine.org
| Builds at once | 3 per account; a push over it waits for a slot, Build now and the API are refused until one finishes |
| Builds a month | 20 per account without Pro, per calendar month in UTC, pushes included; Pro has no limit and goes first in the queue |
| Projects | 20 per account |
| Time per target | 45 minutes, then the target fails as timed out |
| Per target | 4 CPUs, 8 GB of memory, 16 GB of scratch space |
| Downloads kept | 30 days, then deleted with the build's files |
A target that fails is not retried: a red export is almost always the project, and running it again would fail the same way on your time.
Deleting your account deletes everything Forge keeps for it: every build's downloads, every hosted game, and every signing credential and store key. The account goes at once; the files follow within minutes.
The same commit, the same file
Exports are reproducible: the same commit, target and engine version produce the same bytes before signing, whichever builder ran them. The digest on a GitHub check is therefore something you can check a download against.