Jsan: Created page with "{{DISPLAYTITLE:{{FULLPAGENAME}}}} {{HeaderTemplate |welcome=Data Modding Guide }} This guide covers how to create data mods for Elemental: Reforged. Data mods let you add new units, spells, items, improvements, and more -- or modify and remove existing ones -- using XML files. {{SectionTemplate |h=h1 |title=Getting Started |content= ===Mod Folder Location=== All mods l..."

2026-04-07T18:32:15Z

Created page with "{{DISPLAYTITLE:<span style="position: absolute; clip: rect(1px 1px 1px 1px); clip: rect(1px, 1px, 1px, 1px);">{{FULLPAGENAME}}</span>}} {{HeaderTemplate |welcome=Data Modding Guide }} This guide covers how to create data mods for Elemental: Reforged. Data mods let you add new units, spells, items, improvements, and more -- or modify and remove existing ones -- using XML files. {{SectionTemplate |h=h1 |title=Getting Started |content= ===Mod Folder Location=== All mods l..."

New page

{{DISPLAYTITLE:<span style="position: absolute; clip: rect(1px 1px 1px 1px); clip: rect(1px, 1px, 1px, 1px);">{{FULLPAGENAME}}</span>}}
{{HeaderTemplate
|welcome=Data Modding Guide
}}
This guide covers how to create data mods for Elemental: Reforged. Data mods let you add new units, spells, items, improvements, and more -- or modify and remove existing ones -- using XML files.

{{SectionTemplate
|h=h1
|title=Getting Started
|content=
===Mod Folder Location===

All mods live under your Documents folder:

<pre>Documents\My Games\ElementalReforged\Mods\</pre>

The game automatically creates a <code>User</code> subfolder for local mods. You can also create your own named folder.

===Mod Folder Structure===

<pre>
Mods/
YourModName/
Data/
GameCore/ <-- Most game definitions go here
Core Stamps/ <-- Terrain stamps
Effects/ <-- Particle/visual effects
Scenarios/ <-- Scenario definitions
Animations/ <-- Custom animations
Core Tiles/ <-- Tile designs (recursive)
Core World/ <-- World data (recursive)
CutScenes/ <-- Cutscene definitions
</pre>

Place your XML files in the appropriate subdirectory. The game scans these paths when mods are enabled and merges them with the base game data.

===Enabling Your Mod===

# Launch the game
# From the main menu, open the '''Mod Manager'''
# Enable the '''User''' folder (or your custom mod folder)
# Adjust '''load order''' if you have multiple mods (later mods override earlier ones)
# Restart or start a new game
}}

{{SectionTemplate
|h=h1
|title=XML File Format
|content=
All game data is defined in XML files. Here's the basic structure:

<pre>
<?xml version='1.0' encoding='utf-8'?>
<RootElement>

<DataType InternalName="MyDefinition">
<Property1>value</Property1>
<Property2>value</Property2>
</DataType>

</RootElement>
</pre>

'''Key rules:'''

* Every definition needs an <code>InternalName</code> attribute -- this is its unique identifier
* The root element name varies by file but doesn't affect parsing
* Text values for player-visible strings should use localization keys (e.g., <code>TXT_MY_MOD_UNIT_NAME</code>), but you can use plain text for testing
* Boolean values are <code>0</code> (false) or <code>1</code> (true)
* Colors are comma-separated: <code>R,G,B</code> or <code>R,G,B,A</code> (0-255)
}}

{{SectionTemplate
|h=h1
|title=Core Data Types
|content=
Here are the most commonly modded data types and the XML tags they use:

===Units===

<pre>
<UnitTypes>
<UnitType InternalName="MyCustomUnit">
<DisplayName>My Custom Unit</DisplayName>
<Description>A powerful warrior.</Description>
<Class>Adventurer</Class>
<Allegiance>Empire</Allegiance>
<CreatureType>Champion</CreatureType>
<RaceType>Race_Type_Men</RaceType>
<Gender>Male</Gender>
<IsChampion>1</IsChampion>
<Unique>0</Unique>
<CanBeDesigned>0</CanBeDesigned>
<SpawnRating>1</SpawnRating>


<LevelMilestone InternalName="L1">
<Level>1</Level>
<UnitStat_HitPoints>30</UnitStat_HitPoints>
<UnitStat_Accuracy>85</UnitStat_Accuracy>
<UnitStat_CombatSpeed>24</UnitStat_CombatSpeed>
</LevelMilestone>


<AutoCreateEquipment>IronSword</AutoCreateEquipment>
<Equipment>F_Male_Head_01</Equipment>


<SelectedAbilityBonusOption>Fire1</SelectedAbilityBonusOption>


<ModelPath>Gfx\HKB\Units\F_Male_Mesh_01.hkb</ModelPath>
<SkeletonPath>Gfx\HKB\Units\K_Male_Skeleton_01.hkb</SkeletonPath>
<AnimationPack>MaleSovereignAnimationPack</AnimationPack>
<BattleAnimationBehavior>Melee</BattleAnimationBehavior>
<Color_Skin>180,140,110,255</Color_Skin>
<Color_Clothing1>60,40,30,255</Color_Clothing1>
<SoundPack>SoundPack_Generic_Male</SoundPack>
</UnitType>
</UnitTypes>
</pre>

===Spells===

<pre>
<Spells>
<SpellDef InternalName="MyFireball">
<DisplayName>Fireball</DisplayName>
<Description>Hurls a ball of fire at the target.</Description>
<Image>T_Fireball_Painting.png</Image>
<IconFG>T_Fireball_Icon.png</IconFG>
<SpellType>Tactical</SpellType>
<SpellClass>Offensive</SpellClass>
<SpellSubClass>Damage</SpellSubClass>
<SpellTargetType>EnemyUnit</SpellTargetType>
<SpellBookSortCategory>Attack</SpellBookSortCategory>


<Prereq>
<Type>AbilityBonusOption</Type>
<Attribute>FireAdept1</Attribute>
</Prereq>


<SpellResourceCost>
<Resource>Mana</Resource>
<Amount>12</Amount>
</SpellResourceCost>


<GameModifier>
<ModType>Unit</ModType>
<Attribute>AdjustUnitStat</Attribute>
<StrVal>CurHealth</StrVal>
<Value>-15</Value>
</GameModifier>


<SpellDefEffect>
<EffectName>T_Fireball_Particle</EffectName>
<EffectScale>1.0</EffectScale>
<SnapToTerrain>1</SnapToTerrain>
</SpellDefEffect>

<HitSoundFX>Spell_Fire_01</HitSoundFX>
</SpellDef>
</Spells>
</pre>

===Improvements (City Buildings)===

<pre>
<ImprovementTypes>
<ImprovementType InternalName="MyLibrary">
<DisplayName>Grand Library</DisplayName>
<Description>A center of learning.</Description>
<RequiresCity>1</RequiresCity>
<RequiresForceUnlock>1</RequiresForceUnlock>
<LaborToBuild>0</LaborToBuild>


<RequiredImprovement>Conclave</RequiredImprovement>


<BarredTerrain>River</BarredTerrain>
<BarredTerrain>SwampTerrain</BarredTerrain>
<PreferredTerrain>City</PreferredTerrain>


<GameModifier>
<ModType>Player</ModType>
<Attribute>AbilityBonus</Attribute>
<StrVal>A_Research</StrVal>
<Value>15</Value>
<Provides>+15 Research</Provides>
</GameModifier>


<AIData AIPersonality="AI_General">
<AIPriority>14</AIPriority>
<AITag>Study</AITag>
</AIData>

<ArtDef>Art_Academy</ArtDef>
</ImprovementType>
</ImprovementTypes>
</pre>

===Resources===

<pre>
<ResourceTypes>
<ResourceType InternalName="MyResource">
<DisplayName>Moonstone</DisplayName>
<Description>A rare crystalline mineral.</Description>
<Type>Material</Type>
<Icon>Gfx//Icons//Res_Icon_Moonstone.png</Icon>
<Worth>5</Worth>
<Global>0</Global>
<Rarity>0.3</Rarity>
<Shared>0</Shared>
<TradedByCaravans>1</TradedByCaravans>
<ShownInGlobalDisplay>1</ShownInGlobalDisplay>
<IconColor>180,200,255</IconColor>
<ModelColor>180,200,255</ModelColor>
</ResourceType>
</ResourceTypes>
</pre>

===Terrain Types===

<pre>
<TerrainTypes>
<TerrainType InternalName="MyTerrain">
<DisplayName>Crystalline Wastes</DisplayName>
<MaxHeight>60</MaxHeight>
<MinHeight>50</MinHeight>
<MovementCost>12</MovementCost>
<Category>Land</Category>
<IsBaseTerrain>0</IsBaseTerrain>
<IsTerrainFeature>1</IsTerrainFeature>
<PassableByLandUnits>1</PassableByLandUnits>
<PassableByWaterUnits>0</PassableByWaterUnits>
<PassableByAirUnits>1</PassableByAirUnits>
<Indestructable>0</Indestructable>


<GameModifier InternalName="CrystalYield">
<ModType>Resource</ModType>
<Attribute>TileYieldMaterial</Attribute>
<Value>2</Value>
<PerTurn>1</PerTurn>
</GameModifier>
</TerrainType>
</TerrainTypes>
</pre>
}}

{{SectionTemplate
|h=h1
|title=The GameModifier System
|content=
GameModifiers are the backbone of effects in Elemental. They're used everywhere: spells, items, improvements, terrain, abilities, and more. A single definition can contain multiple GameModifier blocks.

===Basic Structure===

<pre>
<GameModifier InternalName="OptionalName">
<ModType>Unit</ModType>
<Attribute>AdjustUnitStat</Attribute>
<StrVal>CurHealth</StrVal>
<Value>10</Value>
<Provides>+10 HP</Provides>
</GameModifier>
</pre>

===ModType Values===

<table class="wikitable">
<tr><th>ModType</th><th>Applies to</th></tr>
<tr><td><code>Unit</code></td><td>Individual units (stats, abilities)</td></tr>
<tr><td><code>Player</code></td><td>Player-wide bonuses (research, gold income)</td></tr>
<tr><td><code>Resource</code></td><td>Resource yields and production</td></tr>
<tr><td><code>Map</code></td><td>Terrain and tile effects</td></tr>
</table>

===Common Attributes===

<table class="wikitable">
<tr><th>XML Tag</th><th>Description</th></tr>
<tr><td><code>ModType</code></td><td>What the modifier targets</td></tr>
<tr><td><code>Attribute</code></td><td>The specific attribute to modify</td></tr>
<tr><td><code>Value</code></td><td>Numeric value of the effect</td></tr>
<tr><td><code>StrVal</code> / <code>StrVal2</code></td><td>String parameters (e.g., stat name, unit class)</td></tr>
<tr><td><code>Provides</code></td><td>Player-visible description of the effect</td></tr>
<tr><td><code>Duration</code></td><td>How many turns the effect lasts</td></tr>
<tr><td><code>DurationOnTile</code></td><td>Duration while on a specific tile</td></tr>
<tr><td><code>Radius</code></td><td>Area of effect radius</td></tr>
<tr><td><code>Multiplier</code></td><td>Multiplicative factor (default: 1.0)</td></tr>
<tr><td><code>BonusValue</code></td><td>Additional bonus amount</td></tr>
<tr><td><code>MinValue</code> / <code>MaxValue</code></td><td>Random range (if both set, value is randomized between them)</td></tr>
</table>

===Conditional Modifiers===

<table class="wikitable">
<tr><th>XML Tag</th><th>Description</th></tr>
<tr><td><code>PerTurn</code></td><td>Apply every turn (boolean)</td></tr>
<tr><td><code>PerLevel</code></td><td>Scale with unit level (boolean)</td></tr>
<tr><td><code>PerStamina</code></td><td>Scale with stamina (boolean)</td></tr>
<tr><td><code>Cumulative</code></td><td>Stacks with itself (boolean)</td></tr>
<tr><td><code>vsDamaged</code></td><td>Only applies vs damaged targets</td></tr>
<tr><td><code>vsLower</code></td><td>Only applies vs lower-stat targets</td></tr>
<tr><td><code>vsHigher</code></td><td>Only applies vs higher-stat targets</td></tr>
<tr><td><code>vsOtherAllegiance</code></td><td>Only applies vs different allegiance</td></tr>
<tr><td><code>WhenUnderPercentHitPoints</code></td><td>Activates when HP below threshold (0-100)</td></tr>
<tr><td><code>WhenUnderArmySize</code></td><td>Activates when army size is under N</td></tr>
<tr><td><code>WhenOverArmySize</code></td><td>Activates when army size is over N</td></tr>
</table>

===Application Timing===

<table class="wikitable">
<tr><th>XML Tag</th><th>Description</th></tr>
<tr><td><code>xActions</code></td><td>Apply at battle start</td></tr>
<tr><td><code>ApplyAtBattleEnd</code></td><td>Apply when battle ends</td></tr>
<tr><td><code>ApplyDuringConstruction</code></td><td>Apply while building is under construction</td></tr>
<tr><td><code>ApplyFromTileAtTacticalTurnStart</code></td><td>Apply from tile at each tactical turn</td></tr>
<tr><td><code>RemoveWhenTargetLeavesTile</code></td><td>Remove effect when unit leaves the tile</td></tr>
<tr><td><code>IsPreHitSpellModifier</code></td><td>Apply before hit resolution</td></tr>
<tr><td><code>ApplyIfSpellTargetKilled</code></td><td>Apply only if the spell kills the target</td></tr>
</table>

===Targeting===

<table class="wikitable">
<tr><th>XML Tag</th><th>Description</th></tr>
<tr><td><code>AffectedUnits</code></td><td>Filter which units are affected</td></tr>
<tr><td><code>UnitClass</code></td><td>Filter by unit class</td></tr>
<tr><td><code>TerrainType</code></td><td>Filter by terrain type</td></tr>
<tr><td><code>ApplyToCaster</code></td><td>Apply to the caster instead of the target</td></tr>
<tr><td><code>ApplyToPlayer</code></td><td>Apply to the player instead of a unit</td></tr>
<tr><td><code>ApplyToTile</code></td><td>Apply to the tile instead of a unit</td></tr>
<tr><td><code>ApplyToSpellRadiusCenterOnly</code></td><td>Only affect center tile of AoE</td></tr>
</table>
}}

{{SectionTemplate
|h=h1
|title=The Calculate System (Variable Expressions)
|content=
For dynamic values that depend on game state (unit stats, shard counts, etc.), use <code>Calculate</code> blocks inside a GameModifier:

<pre>
<GameModifier>
<ModType>Unit</ModType>
<Attribute>CurHealth</Attribute>

<Calculate InternalName="ShardBonus" ValueOwner="CastingUnit">
<Expression><![CDATA[[UnitOwner_GetNumLifeShards] * 2]]></Expression>
</Calculate>

<Calculate InternalName="BaseHeal" ValueOwner="CastingUnit">
<Expression><![CDATA[[ShardBonus] + 8]]></Expression>
</Calculate>

<Calculate InternalName="Value">
<Expression><![CDATA[[BaseHeal]]]></Expression>
</Calculate>
</GameModifier>
</pre>

===How It Works===

* Each <code>Calculate</code> block has an <code>InternalName</code> and an <code><Expression></code>
* Variables are referenced with square brackets: <code>[VariableName]</code>
* Variables can reference other Calculate blocks by InternalName, or properties from the ValueOwner
* The system links calculators together: child calculators feed into parent calculators
* The final result must be in a calculator named <code>Value</code>
* Use <code>ValueForFormattedDescription</code> for the value shown in UI descriptions

===Supported Operators===

<table class="wikitable">
<tr><th>Operator</th><th>Description</th></tr>
<tr><td><code>+</code></td><td>Addition</td></tr>
<tr><td><code>-</code></td><td>Subtraction</td></tr>
<tr><td><code>*</code></td><td>Multiplication</td></tr>
<tr><td><code>/</code></td><td>Division</td></tr>
<tr><td><code>%</code></td><td>Modulo</td></tr>
<tr><td><code>^</code></td><td>Exponentiation</td></tr>
<tr><td><code><</code></td><td>Less than (returns 0 or 1)</td></tr>
<tr><td><code>></code></td><td>Greater than (returns 0 or 1)</td></tr>
</table>

===Calculate Tags===

<table class="wikitable">
<tr><th>Tag</th><th>Description</th></tr>
<tr><td><code>Expression</code></td><td>The math expression (wrap in <code><![CDATA[...]]></code> for safety)</td></tr>
<tr><td><code>Min</code></td><td>Minimum value the result can be</td></tr>
<tr><td><code>Max</code></td><td>Maximum value the result can be</td></tr>
<tr><td><code>ValueOwner</code></td><td>Where to look up variable values (<code>CastingUnit</code>, <code>TargetUnit</code>, etc.)</td></tr>
</table>

===Common Variable Names===

Variables available depend on the <code>ValueOwner</code>. Common ones include:

* <code>[UnitOwner_GetNumLifeShards]</code>, <code>[UnitOwner_GetNumFireShards]</code>, etc.
* <code>[UnitStat_HitPoints]</code>, <code>[UnitStat_Accuracy]</code>, <code>[UnitStat_CombatSpeed]</code>
* <code>[Unit_GetHPCurrent]</code>, <code>[Unit_GetLevel]</code>
* <code>[A_Diplomacy]</code>, <code>[TradeIncome]</code> (for treaty calculations)
* Any float property exposed by the ValueOwner's <code>GetFloatProperty()</code> method
}}

{{SectionTemplate
|h=h1
|title=Overriding Existing Definitions
|content=
===The IfExists Attribute===

When your mod defines something with the same <code>InternalName</code> as a base game definition, you can control what happens using the <code>IfExists</code> attribute:

<pre>
<UnitType InternalName="Champion_Craul" IfExists="ClearIfExists">

</UnitType>
</pre>

<table class="wikitable">
<tr><th>IfExists Value</th><th>Behavior</th></tr>
<tr><td><code>Update</code></td><td>Merge your values on top of the existing definition (partial override)</td></tr>
<tr><td><code>ClearIfExists</code></td><td>Wipe the existing definition completely, then read your new values (full replacement)</td></tr>
<tr><td><code>ClearChildren</code></td><td>Clear child collections (e.g., level milestones) but keep parent data</td></tr>
<tr><td><code>Ignore</code></td><td>Skip this definition if it already exists</td></tr>
<tr><td><code>Duplicate</code></td><td>Always create a new entry (no duplicate check)</td></tr>
</table>

If you don't specify <code>IfExists</code>, each data type has a default behavior. Most types default to <code>Update</code>, meaning your values merge on top.

===Practical Examples===

'''Buff an existing unit's HP:'''

<pre>

<UnitType InternalName="Champion_Craul">
<LevelMilestone InternalName="L1">
<UnitStat_HitPoints>50</UnitStat_HitPoints>
</LevelMilestone>
</UnitType>
</pre>

'''Completely replace a spell:'''

<pre>
<SpellDef InternalName="Aid" IfExists="ClearIfExists">

<DisplayName>Greater Aid</DisplayName>

</SpellDef>
</pre>
}}

{{SectionTemplate
|h=h1
|title=Removing Definitions (RemoveDef)
|content=
The Smart Modding system lets you surgically remove base game content. Place a <code><RemoveDef></code> block in any XML file in your mod:

===Remove All Definitions of a Type===

<pre>
<RemoveDef>
<RemoveAllCoreDefsOfType>UnitType</RemoveAllCoreDefsOfType>
</RemoveDef>
</pre>

This removes every core UnitType, letting your mod provide all units from scratch.

===Remove Specific Definitions by Name===

<pre>
<RemoveDef>
<UnitType InternalName="Champion_Craul"/>
<SpellDef InternalName="Aid"/>
<ImprovementType InternalName="Academy"/>
</RemoveDef>
</pre>

===Skip Parsing Entire Files===

<pre>
<RemoveDef>
<SkipParsingFile>CoreUnitProps.xml</SkipParsingFile>
<SkipParsingFile>CoreMonsters.xml</SkipParsingFile>
</RemoveDef>
</pre>

This prevents the game from loading those files at all, so your mod can provide complete replacements.

===Combining Approaches===

You can combine these in a single RemoveDef block:

<pre>
<RemoveDef>

<RemoveAllCoreDefsOfType>RaceConfig</RemoveAllCoreDefsOfType>


<SpellDef InternalName="Aid"/>


<SkipParsingFile>CoreMonsters.xml</SkipParsingFile>
</RemoveDef>
</pre>

'''Important:''' RemoveDef only affects '''core''' definitions. It won't remove definitions added by other mods loaded before yours. Load order matters.
}}

{{SectionTemplate
|h=h1
|title=Load Order
|content=
When multiple mods are enabled, the game loads them in the order shown in the Mod Manager. This matters because:

# '''Later mods win.''' If two mods define the same <code>InternalName</code>, the later one's values take precedence (in <code>Update</code> mode, the later mod's values overwrite the earlier mod's for any overlapping fields).
# '''RemoveDef applies to core only.''' RemoveDef blocks remove base game definitions during the counting phase, before any mod definitions are parsed.
# '''Recommended practice:''' If your mod depends on another mod, document that it should be loaded after the dependency.
}}

{{SectionTemplate
|h=h1
|title=AI Data
|content=
Most data types support an <code><AIData></code> block that tells the AI how to evaluate and use the definition:

<pre>
<AIData AIPersonality="AI_General">
<AIPriority>15</AIPriority>
<AITag>Study</AITag>


<ValueCalcWrapper>
<ValueType>IsTargetWorthy</ValueType>
<Calculate InternalName="Calc" ValueOwner="TargetUnit">
<Expression><![CDATA[[Unit_GetHPCurrent]]]></Expression>
</Calculate>
<Calculate InternalName="Value">
<Expression><![CDATA[[Calc] < 30]]></Expression>
</Calculate>
</ValueCalcWrapper>
</AIData>
</pre>

Higher <code>AIPriority</code> values make the AI favor that option more. The <code>ValueCalcWrapper</code> provides dynamic evaluation for context-sensitive decisions.
}}

{{SectionTemplate
|h=h1
|title=Reference: Moddable Data Types
|content=
Here are the major data types you can define in XML. Use the corresponding tag name as your XML element:

<table class="wikitable">
<tr><th>XML Tag</th><th>Description</th><th>Example File</th></tr>
<tr><td><code>UnitType</code></td><td>Units, champions, monsters</td><td>CoreUnits.xml</td></tr>
<tr><td><code>SpellDef</code></td><td>Spell definitions</td><td>CoreSpells.xml</td></tr>
<tr><td><code>ImprovementType</code></td><td>City buildings and improvements</td><td>CoreImprovements.xml</td></tr>
<tr><td><code>ResourceType</code></td><td>Resources (gold, mana, materials)</td><td>CoreResources.xml</td></tr>
<tr><td><code>TerrainType</code></td><td>Terrain types and features</td><td>TerrainTypes.xml</td></tr>
<tr><td><code>GameItemType</code></td><td>Equipment and items</td><td>CoreItems.xml</td></tr>
<tr><td><code>RaceConfig</code></td><td>Faction configurations</td><td>CoreRaceConfigs.xml</td></tr>
<tr><td><code>RaceType</code></td><td>Race type definitions</td><td>CoreRaceTypes.xml</td></tr>
<tr><td><code>TechDef</code></td><td>Technology definitions</td><td>CoreTechs.xml</td></tr>
<tr><td><code>TechTree</code></td><td>Technology tree layout</td><td>TechTree_Amarian.xml</td></tr>
<tr><td><code>QuestDef</code></td><td>Quest definitions</td><td>CoreQuests.xml</td></tr>
<tr><td><code>QuestLocation</code></td><td>Quest locations on the map</td><td>CoreQuestLocations.xml</td></tr>
<tr><td><code>AbilityBonus</code></td><td>Ability/trait definitions</td><td>CoreAbilities.xml</td></tr>
<tr><td><code>RecipeType</code></td><td>Crafting recipes</td><td>CoreRecipes.xml</td></tr>
<tr><td><code>DungeonType</code></td><td>Dungeon definitions</td><td>(in GameCore)</td></tr>
<tr><td><code>GoodieHut</code></td><td>Goodie hut encounters</td><td>CoreGoodieHuts.xml</td></tr>
<tr><td><code>GameTrigger</code></td><td>Event triggers</td><td>CoreGameEvents.xml</td></tr>
<tr><td><code>FlavorText</code></td><td>Random flavor text</td><td>CoreFlavorText.xml</td></tr>
<tr><td><code>NamePool</code></td><td>Name generation pools</td><td>CoreNamePools.xml</td></tr>
<tr><td><code>FactionConfig</code></td><td>Faction setup and colors</td><td>CoreRaceConfigs.xml</td></tr>
<tr><td><code>DifficultyLevel</code></td><td>Difficulty settings</td><td>CoreDifficultyLevels.xml</td></tr>
<tr><td><code>Treaty</code></td><td>Diplomacy treaty types</td><td>Treaties.xml</td></tr>
<tr><td><code>MapSettings</code></td><td>Map generation settings</td><td>CoreMaps.xml</td></tr>
<tr><td><code>RandomEvent</code></td><td>Random event definitions</td><td>CoreRandomEvents.xml</td></tr>
<tr><td><code>UnitStatType</code></td><td>Unit stat definitions</td><td>CoreUnitStats.xml</td></tr>
<tr><td><code>UnitQualityType</code></td><td>Unit quality tiers</td><td>CoreUnitQualityTypes.xml</td></tr>
<tr><td><code>MusicLayerGroup</code></td><td>Music definitions</td><td>CoreLayeredMusic.xml</td></tr>
<tr><td><code>SoundPack</code></td><td>Sound effect packs</td><td>UnitSoundPacks.xml</td></tr>
</table>

'''Tip:''' The best way to learn any data type's available fields is to look at the corresponding core XML file in <code>Elemental-LH/Game/data/GameCore/</code>.
}}

{{SectionTemplate
|h=h1
|title=Tips and Best Practices
|content=
* '''Start small.''' Override one unit or one spell to make sure your mod folder is set up correctly before building something large.
* '''Use''' <code>Update</code> '''mode''' (the default) for small tweaks. Only use <code>ClearIfExists</code> when you need to completely replace a definition.
* '''Keep your InternalNames unique''' for new content. Prefix them with your mod name to avoid conflicts: <code>MyMod_FireGolem</code> instead of <code>FireGolem</code>.
* '''Test with the Spawn Object tool''' in-game (Ctrl+Alt+S or tilde key) to quickly spawn and inspect your modded objects.
* '''Back up your mod folder''' before making large changes.
* '''Check load order''' if your changes aren't appearing -- your mod might be loading before another mod that overrides the same definitions.
* '''Localization keys''' (e.g., <code>TXT_MY_MOD_UNIT_NAME</code>) can be defined in localization XML files, but plain text strings work fine for testing and small mods.
}}

[[Category:Modding]]

Data Modding Guide - Revision history