> For the complete documentation index, see [llms.txt](https://dante-3.gitbook.io/dante-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dante-3.gitbook.io/dante-docs/modular-experience-system/getting-started/setup.md).
# Setup
## Automatic Setup
### Half Manual Setup
{% stepper %}
{% step %}
### Configure Asset Manager
Add the following entries to your `DefaultGame.ini` (or use `MES_ProjectSetupChecker`'s automatic configuration):
```ini
[/Script/Engine.AssetManagerSettings]
-PrimaryAssetTypesToScan=(PrimaryAssetType="ModularExperienceDefinition",AssetBaseClass="/Script/ModularExperienceSystem.ModularExperienceDefinition",bHasBlueprintClasses=True,bIsEditorOnly=False,Directories=((Path="/Game")),SpecificAssets=(),Rules=(Priority=-1,ChunkId=-1,bApplyRecursively=True,CookRule=Unknown))
+PrimaryAssetTypesToScan=(PrimaryAssetType="ModularExperienceDefinition",AssetBaseClass="/Script/ModularExperienceSystem.ModularExperienceDefinition",bHasBlueprintClasses=True,bIsEditorOnly=False,Directories=((Path="/Game")),SpecificAssets=(),Rules=(Priority=-1,ChunkId=-1,bApplyRecursively=True,CookRule=AlwaysCook))
-PrimaryAssetTypesToScan=(PrimaryAssetType="MES_UserFacingExperience",AssetBaseClass="/Script/ModularExperienceSystem.MES_UserFacingExperience",bHasBlueprintClasses=False,bIsEditorOnly=False,Directories=((Path="/Game")),SpecificAssets=(),Rules=(Priority=-1,ChunkId=-1,bApplyRecursively=True,CookRule=Unknown))
+PrimaryAssetTypesToScan=(PrimaryAssetType="MES_UserFacingExperience",AssetBaseClass="/Script/ModularExperienceSystem.MES_UserFacingExperience",bHasBlueprintClasses=False,bIsEditorOnly=False,Directories=((Path="/Game")),SpecificAssets=(),Rules=(Priority=-1,ChunkId=-1,bApplyRecursively=True,CookRule=AlwaysCook))
```
{% hint style="info" %}
When you first open the editor, `MES_ProjectSetupChecker` detects missing settings and offers an "Apply & Restart" button for automatic configuration.
{% endhint %}
{% endstep %}
{% step %}
### Set the WorldSettings Class
Add to your `DefaultEngine.ini`:
```ini
[/Script/Engine.Engine]
WorldSettingsClassName=/Script/ModularExperienceSystem.MES_WorldSettings
```
This enables the **Default Gameplay Experience** field in the World Settings panel of every map.
{% endstep %}
{% step %}
### Set the Asset Manager Class (Optional)
If you want custom asset loading and caching behavior:
```ini
[/Script/Engine.Engine]
AssetManagerClassName=/Script/ModularExperienceSystem.MES_AssetManager
```
{% endstep %}
{% step %}
### Create Your First Experience Definition
1. Right-click in the Content Browser → **Miscellaneous** → **Modular Experience Definition**
2. Name your Blueprint (e.g., `B_DefaultExperience`)
3. Open it and add actions to the **Actions** array:
* **Modular Game Feature Action** — customizable via Blueprint
* Or a C++ `UGameFeatureAction` subclass
{% hint style="info" %}
To create your first action in Blueprint, see the [Game Feature Actions](/dante-docs/modular-experience-system/modular-game-feature-actions.md) guide.
{% endhint %}
{% endstep %}
{% step %}
### Assign the Experience to a Map
#### Method A: WorldSettings (Recommended)
1. Open the **World Settings** panel in your map
2. Select your experience in the **Default Gameplay Experience** field
#### Method B: URL Options
Append to the URL during map travel:
```
/Game/Maps/MyMap?Experience=ModularExperienceDefinition:B_DefaultExperience
```
#### Method C: Developer Settings (Editor-Only)
Editor → Preferences → Project → **Modular Experience System** → **Experience Override**
This lets you test different experiences without modifying the map.
{% endstep %}
{% step %}
### Play
**Auto Setup** mode is enabled by default. This means:
* ✅ You **don't need** to write a custom GameMode — the subsystem auto-adds `UModularExperienceManagerComponent` to the GameState
* ✅ You **don't need** a custom GameState — `MES_` base classes or Auto Setup receiver registration is used
* ✅ The experience is auto-resolved in order: WorldSettings → URL → CommandLine
Press Play in PIE — the experience loads, actions activate, and the loading screen is handled automatically.
{% endstep %}
{% endstepper %}
### Manual Setup
If you want more control, set `bAutoSetup = false` and:
1. Derive from `AMES_GameMode` or `AMES_GameModeBase`
2. Derive from `AMES_GameState` and add `UModularExperienceManagerComponent`
3. Override `InitGameState()` and call `ChangeCurrentExperience()`
4. Derive other actors from the `AMES_` base classes
