Compo Game Loader Tutorial: Load, Test, and Share Games in Minutes

What Compo Game Loader is

Compo Game Loader is a lightweight tool designed for game jam participants and indie developers to quickly load, test, and distribute small game builds. It focuses on fast iteration, simple configuration, and easy sharing so you can spend less time on setup and more time on gameplay and feedback.

Quick setup (2 minutes)

Download the latest Compo Game Loader build for your platform from the official release page.
Unzip the package into a dedicated folder for your jam.
Place your game build(s) inside the folder — a single executable or an index.html + assets directory for web builds.
Open the loader executable; it will scan the folder and list available games automatically.

Loading games

Desktop builds: The loader detects executables (.exe/.app/.x86/.x86_64) and shows a play button. Click to launch in a new process and monitor logs in the loader window.
Web builds: For projects using index.html, the loader launches a lightweight local server and opens the default browser at the correct localhost URL.
Multiple builds: The loader supports labeling or tagging builds (e.g., v1.0, prototype) — rename folders with tags or use the loader’s metadata panel if available.

Testing workflows

Rapid playtest: Launch, play for a short loop, and close — repeat instantly without manual server setup.
Console and logs: Use the loader’s log viewer to inspect game stdout/stderr and catch crashes or errors immediately.
Input mapping: If your game supports gamepads, verify input detection in the loader’s device panel before playtesting.
Simulate constraints: Adjust the loader’s CPU or resolution settings if provided to test low-end performance quickly.
Automated test runs: For builds with a test harness, configure the loader to run tests on launch and output pass/fail summaries.

Debugging tips

Crash reproduction: Re-run the game from the loader to collect fresh logs; note the exact sequence of steps that led to the crash.
Asset issues: Confirm relative paths; the loader’s working directory should be the game folder. If missing assets appear, check case-sensitivity for web builds (important on Linux).
Browser caching: Use the loader’s cache-busting option or open the dev tools and disable cache when testing web builds.
Dependency errors: Ensure runtime libraries (e.g., Visual C++ redistributables) are installed; the loader may surface helpful error messages.

Packaging and sharing

Create a zip: After finalizing a build, use the loader’s “Export” or “Package” feature (if present) to produce a compressed archive ready for upload.
One-click sharing: Many versions offer a share link via temporary hosting or integrated upload to popular hosting services — use these to distribute quick playtests to teammates.
Metadata and screenshots: Add a simple README and a screenshot in the build folder so recipients know controls and context immediately.
Versioning: Keep incremental builds named clearly (e.g., mygame-v1.2.zip) and maintain a changelog file for testers.

Best practices for jams

Keep builds small: Aim for a single executable or a compact web folder under a few tens of MB to speed transfers.
Automate exports: Hook your build script to produce a loader-ready folder automatically after each successful build.
Communicate controls: Include a short controls.txt or README to avoid testers asking basic questions.
Use tags: Mark builds as “stable,” “playtest,” or “prototype” so teammates know which to try first.

Quick checklist before sharing

Game launches from the loader without errors
Controls documented (README or screenshot)
Logs are clean or include known issues in changelog
Build compressed and versioned clearly

Final note

Compo Game Loader removes friction from the playtest loop: place your build in the folder, launch, test, fix, and share — repeat. Following the steps above will get you from development to feedback in minutes.

Compo Game Loader Tutorial: Load, Test, and Share Games in Minutes