📦 Building and Distribution

Build Configurations

Build configurations determine how your game is compiled. Each serves a different purpose—from debugging to final release.

Configuration Types

When to Use Each

• Development: Day-to-day testing, QA builds, playtesting
  • Console commands work (~key)
  • Logging enabled for debugging
  • Good performance but larger size
• Shipping: Final release, store distribution
  • Console disabled (cheat prevention)
  • All debug code stripped
  • Smallest size, best performance

Figure: Development for testing, Shipping for release.

Setting Build Configuration

1. Go to Project Settings → Project → Packaging
2. Find Build Configuration
3. Select Shipping for final builds
4. Or select in the Package menu when packaging

The Packaging Process

Packaging converts your project into a standalone executable. The process cooks content, compiles code, and creates the final distributable.

How to Package

1. Go to Platforms menu in the toolbar
2. Select your target platform (e.g., Windows)
3. Click Package Project
4. Choose an output folder (outside your project directory)
5. Wait for the process to complete

What Happens During Packaging

Figure: The packaging pipeline transforms your project into a distributable game.

Output Structure

After packaging, your output folder contains:

WindowsNoEditor/
├── Engine/
│   └── ... (engine content)
├── YourGame/
│   ├── Binaries/
│   │   └── Win64/
│   │       └── YourGame.exe
│   ├── Content/
│   │   └── Paks/
│   │       └── YourGame-WindowsNoEditor.pak
│   └── ... (config, etc.)
└── YourGame.exe (shortcut/launcher)

Platform Requirements

Troubleshooting

Packaging can fail for various reasons. Here's how to diagnose and fix common issues.

Reading the Output Log

When packaging fails:

1. Check Window → Developer Tools → Output Log
2. Scroll to find Error: lines (in red)
3. Note the first error—later errors may be cascading
4. Search the error message online for solutions

Common Errors and Solutions

Pre-Packaging Checklist

Before packaging, verify:

• ☑ Game Default Map is set
• ☑ All Blueprints compile without errors
• ☑ No missing asset references (check Message Log)
• ☑ Game plays correctly in Standalone mode
• ☑ Sufficient disk space (2-3x project size)
• ☑ All required plugins are enabled
• ☑ Project Settings configured (Lesson 10.1)

Figure: Start with the Output Log to diagnose packaging failures.

Testing the Packaged Game

After packaging succeeds:

1. Navigate to your output folder
2. Find and run the .exe file
3. Test all major features:
   • Game starts and loads correctly
   • All levels accessible
   • Gameplay functions work
   • Audio plays correctly
   • UI displays properly
   • Save/load works (if implemented)
4. Test on a different computer if possible

Distribution Options

Once packaged, you have several options for distributing your game to players.

Distribution Methods

Creating a ZIP Distribution

Simplest method for sharing:

1. Navigate to your packaged game folder
2. Select all contents
3. Right-click → Send to → Compressed (zipped) folder
4. Rename to YourGame_v1.0_Windows.zip
5. Upload to hosting service

Creating an Installer

For professional distribution, use installer tools:

• Inno Setup: Free, powerful, scripted installer
• NSIS: Free, highly customizable
• InstallShield: Commercial, feature-rich

Installers provide:

• Desktop and Start Menu shortcuts
• Uninstaller entry in Add/Remove Programs
• File association (optional)
• Prerequisite installation (DirectX, VC++ runtime)

Prerequisites

Your game may require players to have:

• Visual C++ Redistributable: Usually required
  • Include in installer or provide download link
  • Found in Engine/Extras/Redist folder
• DirectX: Usually already installed on Windows
• .NET Framework: If using certain plugins

Figure: Multiple paths from packaged game to players.

Hands-On: Packaging Your Game

Let's package your game for Windows. You'll verify settings, run the packaging process, troubleshoot any issues, and test the final build.

Part 1: Pre-Packaging Verification

Step 1: Verify Project Settings

1. Open Edit → Project Settings
2. Go to Project → Maps & Modes
3. Confirm Game Default Map is set to your main level
4. Confirm Default GameMode is correct (or set per-level)

Step 2: Check for Errors

1. Open Window → Developer Tools → Message Log
2. Look for warnings or errors
3. Fix any Blueprint compile errors
4. Address any missing asset warnings

Step 3: Test in Standalone

1. Click dropdown next to Play button
2. Select Standalone Game
3. Verify:
   • Game starts correctly
   • Correct level loads
   • Player spawns properly
   • Basic gameplay works
4. Close the standalone game

Figure: Complete this checklist before packaging.

Part 2: Configure Packaging Settings

Step 4: Set Build Configuration

1. Go to Project Settings → Project → Packaging
2. Set Build Configuration to Shipping
3. Enable Full Rebuild (for first/final build)

Step 5: Configure Compression

1. Still in Packaging settings
2. Ensure Create compressed cooked packages is enabled
3. This reduces final package size

Step 6: Verify Maps to Include

1. Check List of maps to include in a packaged build
2. Add any maps loaded dynamically by string name
3. Referenced maps are usually included automatically

Part 3: Package the Game

Step 7: Save Everything

1. Press Ctrl+Shift+S to Save All
2. Ensure all levels and assets are saved
3. Close any open asset editors

Step 8: Start Packaging

1. Go to Platforms → Windows → Package Project
2. Choose an output folder:
   • Outside your project folder
   • On a drive with plenty of space
   • Example: D:\Builds\MyGame
3. Click Select Folder
4. Packaging begins

Step 9: Monitor Progress

1. Watch the progress in the bottom-right corner
2. Or open Window → Developer Tools → Output Log
3. Look for any red error messages
4. Wait for "Packaging Successful" message
5. This may take 15-60+ minutes for first build

Part 4: Handle Errors (If Any)

If Packaging Fails:

1. Open Output Log and scroll up
2. Find the first Error: line
3. Common fixes:
   • Missing map: Set Game Default Map
   • Blueprint error: Open and fix the Blueprint
   • Asset error: Fix or remove the asset
   • Disk space: Free up space or use different drive
4. Fix the issue and try packaging again

Part 5: Test the Packaged Game

Step 10: Locate the Executable

1. Navigate to your output folder
2. Find Windows or WindowsNoEditor folder
3. Locate YourGame.exe

Step 11: Run the Game

1. Double-click the .exe to launch
2. Game should start in fullscreen
3. Press Alt+Enter to toggle windowed if needed

Step 12: Test Thoroughly

1. Test these areas:
   • Main menu (if you have one)
   • All playable levels
   • Core gameplay mechanics
   • Audio (music, sound effects)
   • UI elements
   • Save/load functionality
   • Exit properly

Step 13: Test on Another Computer (Recommended)

1. Copy the entire packaged folder to another PC
2. Or create a ZIP and transfer
3. Run on a machine without Unreal Engine installed
4. This catches missing dependencies

Part 6: Prepare for Distribution

Step 14: Create Distribution Package

1. Navigate to your packaged game folder
2. Select all contents
3. Right-click → Send to → Compressed (zipped) folder
4. Name it descriptively: YourGame_v1.0_Windows.zip

Step 15: Include README (Optional but Recommended)

1. Create a README.txt file containing:
   • Game title and version
   • Brief description
   • System requirements
   • How to run the game
   • Controls
   • Known issues (if any)
   • Contact/support info
   • Credits
2. Add to package before zipping

Troubleshooting

Bonus: Command Line Options

You can launch your packaged game with options:

• -windowed — Start in windowed mode
• -ResX=1920 -ResY=1080 — Set resolution
• -fullscreen — Force fullscreen
• -log — Enable logging (Development builds only)

Create a shortcut and add options to the Target field.

Summary

In this final lesson, you've learned to package your Unreal Engine 5 project into a standalone game and prepare it for distribution. This completes your journey from project creation to releasing a finished game.

Key Concepts

Build Configurations: Development builds include debugging tools and console access—use for testing. Shipping builds are optimized, secure, and smaller—use for release. Always test a Development build before creating your final Shipping build.

Packaging Process: Packaging cooks content (converts assets to platform format), compiles code, and creates the final executable and .pak files. First builds take longer; subsequent builds are faster. Monitor the Output Log for errors.

Troubleshooting: Most packaging failures come from missing Game Default Map, Blueprint compile errors, or corrupted assets. Check the Output Log for the first error, fix it, and try again. Test in Standalone mode before packaging.

Distribution: Package your game as a ZIP for simple sharing, create an installer for professional distribution, or upload to stores like Steam, Epic, or itch.io. Include prerequisites (VC++ Redistributable) and a README for best user experience.

Build Configuration Quick Reference

Packaging Checklist

Distribution Options

Best Practices

• Test before packaging: Standalone mode catches most issues
• Use Shipping for release: Development builds expose debug tools
• Check Output Log: First error is usually the root cause
• Test on other PCs: Catches missing dependencies
• Include prerequisites: VC++ Redistributable often needed
• Add a README: Helps users with controls and requirements
• Version your builds: Track what you've released
• Keep source project: Never delete your project after packaging

Figure: From configuration to distribution—your complete packaging workflow.

🎉 Course Complete!

Congratulations on completing Introduction to Unreal Engine 5! You've learned:

• Modules 1-3: Editor basics, viewport navigation, content management
• Modules 4-5: Level design, lighting, materials
• Module 6: Blueprint visual scripting
• Module 7: User interfaces with UMG
• Module 8: Audio implementation
• Module 9: Particle effects with Niagara
• Module 10: Packaging and distribution

You now have the foundation to create, polish, and share your own games with Unreal Engine 5!

Knowledge Check