Test / Build Launcher

🚀 Testing and Building Your Launcher

Once your launcher project is open and ready, you can use two important desktop tools:

• Test Launcher for quickly running a local test build
• Build Launcher for exporting a production-ready launcher package

🧪 Part 1: How to Use Test Launcher

What Test Launcher does

Test Launcher creates a temporary local build of your launcher and immediately runs it for testing. This is useful when you want to check your latest project setup without creating a full production export.

When to use it

• After changing layout, visuals, or behaviour
• When checking launcher flow before exporting
• When you want a fast local run without manually building to a folder

How to launch a test build

1. Open your launcher project in the desktop editor
2. Open the main menu
3. Click Test Launcher
4. Wait while the test environment is prepared
5. Your test launcher should then open automatically

What happens behind the scenes

When you run Test Launcher, the desktop app prepares a test copy of the launcher, fetches the required launcher license, then starts the launcher in test mode automatically.

Important things to know

• You do not need to choose an output folder for testing
• The test build is created automatically for you
• Testing is intended for quick checks, not final distribution

If Test Launcher does not run

Run through this checklist:

• Make sure your project is open in the editor
• Make sure you are logged in and your desktop session is active
• Check your internet connection, since the launcher data still needs to be prepared correctly
• Wait a few seconds and try again if you already tested very recently

Common Test Launcher questions

Why is Test Launcher disabled?

This usually means no launcher project is currently loaded in the editor.

Why does nothing seem to happen?

Give it a moment. The desktop app may still be preparing the local test environment and launcher files in the background.

Why am I told to wait before testing again?

This is normal. Test launching is intentionally throttled to prevent repeated rapid launches.

📦 Part 2: How to Use Build Launcher

What Build Launcher does

Build Launcher creates a production export of your launcher into a folder you choose. This export includes the launcher executable and its matching launcher license file.

When to use it

• When you want a proper exported launcher folder
• Before packaging your launcher into an installer
• When preparing files for release, upload, or distribution

How to build your launcher

1. Open your launcher project in the desktop editor
2. Open the main menu
3. Click Build Launcher
4. Choose an output folder
5. Click Start Build
6. Wait for the build process to complete

What the build window does

The build window lets you choose the export destination and then shows live progress while the build runs.

You will see progress stages such as:

• Preparing the export directory
• Verifying the runtime version
• Downloading the latest engine files if needed
• Generating the secure launcher license

What gets exported

After a successful build, your output folder will contain the launcher files needed for distribution.

• launcher.exe
• launcher.lic

[warning]Do not remove or rename the launcher license file unless you know exactly what you are doing. It is part of the exported launcher package.

After the build completes

When the build succeeds, you will see a completion message and can open the export folder directly from the desktop app.

Best practice for Build Launcher

• Export to a fresh folder each time
• Run a quick test before distributing the build
• Keep older build folders if you want simple versioned backups
• Use the exported folder as the source for your installer workflow

If Build Launcher fails

Check the following:

• You selected a valid output folder
• Your internet connection is stable
• You are logged in and your session is still active
• You have not attempted another build too quickly after the last one

[warning]Build Launcher has a cooldown between builds. If you try again too quickly, you may be asked to wait before starting another build.

Common Build Launcher questions

Why is Build Launcher disabled?

This usually means no launcher project is currently loaded.

Why do I need to choose an output folder?

The production build is exported to a folder on your machine so you can review it, package it, or distribute it.

Why should I use an empty output folder?

This helps avoid confusion with leftover files from earlier exports and makes the build results easier to manage.

Can I build repeatedly into the same folder?

Yes, but using a fresh folder is usually cleaner and safer, especially when comparing builds or preparing release packages.

💡 Recommended Workflow

1. Make your changes in the editor
2. Use Test Launcher to quickly check your launcher locally
3. Make any final adjustments
4. Use Build Launcher to export the production-ready launcher files
5. Use those exported files for packaging, installer creation, or release

🛠️ Troubleshooting

The menu items are greyed out

Make sure a launcher project is open first. These actions only become available when the editor has an active project loaded.

The build or test process seems stuck

Wait a moment, especially if your internet connection is slow or if the desktop app needs to prepare updated launcher files.

I got an error message during build or test

Read the message shown by the desktop app carefully. In many cases, it will point to a connection issue, a folder problem, or a short cooldown before you can run the action again.

My exported launcher is not where I expected

Open the output folder you selected during the build process. That is where the launcher export is written.