creatorkit_ruben

---

🔨 Migration Steps

1. Extract Creator Kit to a folder of your choice.

2. Extract QA_HoldingCells and open the .uproject file with the marketplace engine.

3. Right-click the folder with your assets → Migrate.

   

💡

You can also migrate a single asset/level. Unreal Engine will automatically include its dependencies.

1. In the migration window, make sure only your asset folder is selected → click OK.

   

💡

To keep dependencies correct, all assets must:

• Be inside a single folder under /Content
• Have no external dependencies or external plugins

1. Navigate to your Creator Kit Lite > Content folder → click Select Folder.

   

2. Open Creator Kit Lite’s .uproject file. Your QA_HoldingCells folder should now appear in the Content Browser.

---

📦 Generating the Package

1. Go to Content > Pakmaster.

2. Right-click WUT_CreatePAK → Run Editor Utility Widget.

   

💡

This is a temporary widget. A more streamlined UI will replace it in the future.


1. Fill in the configuration:

• Name → must match the folder name (no spaces or symbols)
• Path → select the QA_HoldingCells folder
• Type → Map
• Scene Path → choose a map inside QA_HoldingCells/Maps (e.g. QA_Holding_Cells_A)

💡

Matching the Name with the folder name ensures local testing works correctly.

1. Click Generate and wait. Processing time ranges from a few minutes to over an hour depending on map size. Progress will appear in the notification area.

   

2. When finished, check the output in:

   CreatorKit/Paks/Map/{package-name}

   This folder contains Editor, Client, and Server files.

   

---

🔍 Testing the Package

1. Launch a packaged build of the game (e.g. from Steam).

2. Click Create World (top right).

   

3. Once loaded, press N (Build Mode) → File > Load Package.

   

4. Select configFile.json from your generated package:

   CreatorKit/Paks/Map/QA_HoldingCells/configFile.json

   

5. Your assets should now appear, ready to drag into the World.

   

---

➕ Preparing for Publishing

The "Testing Package" step is only for testing that your package functions properly inside HELIX.

To actually publish a world that uses your newly created package, you must:

1. Publish your package to the Vault using the Creator Hub.

2. Once published, create or edit your world project.

3. Add the published Vault package as a dependency to your world.

   

   

4. Only then can you publish your world, ensuring players can access the required package.

🛠️ Editing Maps in Build Mode

• To edit a packaged map in-game:
  • Select the level reference in the Outliner.
  • Click Deference Level in the Properties Panel.
  • Save it as a Dynamic Map.

---

🗺️ Creating Map + Addon Packages

💡

Why do this? Splitting content into Map + Addon lets you publish your assets as a reusable asset pack (Addon). Other creators can use your Addon to build their own maps, while your Map package stays small and only references those assets. This is the standard workflow if you want your assets to be shared, reused, or extended by the community.

You can split assets into two packs:

• Addon (assets)
• Map (uses those assets)

Steps:

1. Create a new folder Map_QA_HoldingCells.

   

2. Move your map file there → Update Redirectors.

   

   

3. Package the Map first (type = Map).

   

   • Map package will be small (just references).

4. Then package the Addon (type = Asset Pack).

   

5. Upload Addon first to Creator Hub, then upload Map and mark the Addon as its dependency.