LoreOwl

Pipeline options

What each option on the Builds tab does, and when to turn it on.

Every option is off by default, except Announce this build. LoreOwl hides the options that the project's engine cannot use.

OptionGodotUnityUnreal
Debug buildYesYesYes
Feedback formYes
AnalyticsYesYesYes
Obfuscate scriptsYes
Run project checksYes
Upload build artifactYesYesYes
Announce this buildYesYesYes

Debug build

Builds in the engine's debug mode. Error messages, assertions and the remote debugger stay in, so you can attach from the editor while someone plays. Debug builds run slower. Turn this off for builds that players get.

Feedback form

Godot only. Adds the LoreOwl feedback form to the build. Testers press Ctrl+F in the game, describe the problem and send it. Each report names the build it came from and shows under Playtest. See Playtest feedback.

Analytics

Adds the LoreOwl Analytics SDK to the build. Sessions and playtime are recorded without code. Your own events need one line of code. The project must be in an organization. See Analytics SDK.

Obfuscate scripts

Godot only. Runs GDMaim on your GDScript while the build is packaged. GDMaim renames variables and functions, so the shipped scripts are hard to read. LoreOwl uses your project's own GDMaim if it has one, and its bundled GDMaim 0.4.0 if not. Only the build copy changes.

Test an obfuscated build before you ship it. Code that looks up names as strings, for example with call("method_name"), can break after renaming.

Run project checks

Godot only. Checks every scene in a copy of the project before it is packaged. Errors stop the build. Warnings do not. See Project checks.

Upload build artifact

Uploads the finished build to your organization's own storage, so teammates can download it. Use Download or Copy download link on the build in History. Links last seven days.

To set up the storage, open Settings, then Builds, then Build storage:

  1. Enter the Bucket. Any S3-compatible storage works.
  2. Enter the Endpoint only for MinIO, Backblaze B2, Wasabi or a NAS. Leave it empty for AWS.
  3. Under More options, set the Region, a Folder and Path-style addressing if your storage needs them.
  4. Under This computer's key, enter the Access key ID and Secret access key. The key is saved on this computer only.
  5. Select Test this computer.

Without storage, the build still runs. There is nothing to download afterwards.

Announce this build

Posts the build and its release notes to the Slack and Discord channels your organization connected. With no channel connected, LoreOwl builds and posts nothing. See Notifications.

Storefront uploads on a trigger

The Builds tab builds and does not upload to stores. You upload a finished build from the Steam, itch.io or Epic Games Store section. See Store uploads.

A trigger has nobody to select a second button, so it can build and upload in one run. These three options are on the trigger.

Publish to itch.io

Uploads the build to your itch.io game with butler, on the build's channel. It needs an itch.io API key and a game. Owners only.

Upload to Steam

Uploads the build to Steamworks with steamcmd. The build does not reach players until it is live on a branch.

Upload to the Epic Games Store

Uploads the build with Epic's BuildPatch Tool. The build stays under Inactive Binaries unless the project has a sandbox set, in which case it goes live. Owners only.

On this page