Ashes of the Singularity gives you access to a powerful strategy game engine to create your own scenarios, objects and worlds. The designers have had a lot of fun creating scenarios for the game, and you will have access to the same features they had to create your own.
There is a lot to do in Ashes. But it was also built from the ground up to be mod friendly. Modders have access to the gameplay elements to change and tweak as they desire. This document will introduce some of what is possible, and we will make a map and a mod to take advantage of this.
This is not always going to be a managed and curated editor with limited options. You can mod the game the same way the developers make changes to the game. Editors are nice because they typically keep you from doing “bad” things. But they also keep you from doing incredibly good things. An editor only allows you to do the things the developer set up for you to change. With direct access to the files you can do things the developer never expected. Sometimes that turns out horribly (okay, a lot of the time that turns out horribly), but sometimes it turns out brilliantly. We believe power trumps ease of use.
- 1 The Map Editor
- 2 Moddable Game Files (added in Escalation 2.2)
- 3 Scripting – Creating Scenarios
- 4 Position Coordinates
- 5 Trigger Examples
- 6 Creating New Units (Work-in-progress)
- 6.1 The Anatomy of a Unit
- 6.2 The AssetGroup File
- 6.3 The MeshDesc File
- 6.4 The Palette File
- 6.5 The TimelineSet File
- 6.6 Design Guidelines for the 3D Model
- 6.7 Texture Authoring Guidelines and Best Practices
- 6.8 Required Textures and How to Convert Them To DDS Format
- 6.9 The FBX File
- 6.10 Baking the Normals
- 6.11 Baking the Asset into the Game
- 6.12 Troubleshooting
- 6.13 When To Create Additional LODs
The Map Editor
(see the full Map Editor article for more)Map Editor add the “-modding” (without the quotes) to the Launch Options for the game (in Steam, right-click the game, go to Properties, click Set Launch Options in the General tab). That will add a Map Editor button to the main menu of the game. From there you can decide if you want to modify an existing map, or create a new one. If you create a new one the menu to the right is presented.
For your first map I’d select a smaller map size. You probably assume that you will run out of space quickly on small maps, you would be wrong. Ashes small maps are what other games would call huge. The large ones are ridiculous and will take a lot of time to design. Practice on some small ones first.
Moddable Game Files (added in Escalation 2.2)
Just as with the Map Editor, to enable the game modifications add the “-modding” (without the quotes) to the Launch Options for the game (in Steam, right-click the game, go to Properties, click Set Launch Options in the General tab). That will add a Modifications button to the main menu of the game. You will not be able to play multiplayer if you are using Mods.
The game supports modding the directories Modders would be most interested in. These are:
- GameCore- The home of the most critical files, definitions for all the games units, buildings, weapons, orbital abilties, etc. This directory isn't additive, you make changes by replacing the file you want to change with a new one. For example, if you want to modify the hit poitns on the Zeus your mod will need to include a new UnitTemplates.csv file with the hit point value for the Zeus changed.
- Maps- For adding new maps with the mod.
- Scenario- For adding new scenarios with the mod. It is possible to modify existing scenarios with mods (by using the same name as that scenario file) but adding new scnearios with new names will be more common.
- UI- So a modder can add new art refered to by the Scenario file.
- UIText- For adding or changing existing text. Files placed here are additive (they don't need to replace an existing file). If you want to change a text string from the base game just include that string in your new text file and it will overwrite it.
To create a mod add a directory in your My Games/Ashes of the Singularity - Escalation/Mods/ directory with the name of the mod you would like to use.
In the above example the name of the Mod is BalanceMod. There is an index.ashesmod file that is a text file that contains the details about the mod. When you start the game it will create a generic one for you but the format is as follows:
Description=This is a Balance mod that also includes the Weehawken Scenario.
This is purely informational, its what is displayed by the mod on the mod screen.
To use a mod go into the Modification screen from the main menu. You will see all of your Mods here and you can enable or disable them, and change the order they load in. This can also be changed by editing the My Games/Ashes of the Singularity - Escalation/Mods.ini file.
Notable Files for Modding
The following files are simple to mod and can effect major changes to gameplay.
All files are found in the Ashes \Assets\ directory.
- \GameCore\BuildingTemplates.csv - Controls build time, cost, armor, HP, and more for all buildings.
- \GameCore\UnitTemplates.csv - Controls build time, cost, armor, HP, and more for all units.
- \GameCore\ModuleTemplates\WeaponModuleTemplates.csv - Controls rate of fire, range, targeting priority, damage, and everything else for all weapons.
There are a lot of files, with a lot of fields that can be tweaked and changed. For this demo we are going to mess with my favorite file, UnitTemplates.csv.
In this screenshot I’ve opened UnitTemplates.csv with Excel, because it makes it easier for me to work with, but Excel isn’t required. Notepad could be used to modify the file. If you use Excel remember to save it as a csv file.
There are a lot of fields that can be modified. In this screenshot we can see:
- Max HPs
- Max Energy
- Energy Per Second
- Heal Rate
- Max Shields
- Shield Regen Rate
- Radar Radius
- Cost Metal
- Cost Data
- Cost Energy
- Cost Logistics
- Construction Time
Some of these fields aren’t named the same as they are in game. Names change during the course of development, and we didn’t want to go back and change all these definitions to match each time they do. Because of that you may have to experiment a bit to see how things match. For example, PHC_T1_Light is the Brute, and Cost Data is actually the Radioactive cost of the unit. You can check out the translation tables in ..\Ashes of the Singularity\Assets\UIText\ directory to see how raw assets relate to in game assets.
Using this file alone, and just the things in this screenshot (there are many more fields in UnitTemplates.csv) we can dramatically alter the balance and design of the game. Let’s use the above to create a new game variant I call the Swarm Mod.
I love the scale of Ashes, I love large battles. So this mod is going to make even larger battles possible and we are going to get into them fast. To do that I’m going to make the following changes:
I’ve reduce the Metal, Radioactives, Logistics and Construction time costs by 90%. I’ve reduce the Logistics costs of T1 units to 0 (so you can have as many as you want). With these changes factories should produce 10 units in the time it took to produce 1 before. As long as you can keep feeding the (dramatically reduced) resource costs, units should come out of factories in an endless stream, like a tower defense game on steroids.
There are a lot of ways to tweak this concept. I could have kept the Metal and Radioactive costs the same and then the player would be strongly incented to claim and upgrade regions to keep his factories fed. I could have just halved the costs rather than dropping them by 90%. I could have increased the resource gathering rates of upgraded metal and radioactive mines rather than lowering costs to incent players to invest in their regions.
But for this we are going crazy. Everything gets very cheap. Massive armies can be built from the start of the game. Those poor creeps won’t know what hit them. And be prepared to be sieged by thousands of units.
This is 5 minutes into the game. I only have 2 factories putting out an endless stream of Brutes. I make an army out of them and in the time it takes to do that there are a bunch more waiting to be added. So I find that it works just as well to set the rally point of the factory to where I want to attack, so that my river of death flows out to destroy it.
The AI has adapted to the new lower costs and is meeting my endless streams with its own. Unlike me it has opted to go with some cheaply produced dreadnoughts. The game lasts for 45 minutes, and there is a battle waging between my endless armies and his at this chokepoint for nearly all of it. It isn’t until I win more minor battles on some of outskirt regions (to take the resources which even at 90% off still become critical) and I send a strike force around to take out his factories that I cause his production chain to falter and begin to break through.
I had to adjust away from my typical Artemis (long range missile ships) to Nemesis (which are really good against enemy dreadnoughts) to be able to begin killing them faster than he could produce them. I also needed to invest heavily in anti-air Apollos to counter the AI’s strike fleets of aircraft that nearly cost me the game.
Once the lines were broken I turned the biggest Ashes armada I had ever controlled against his Nexus. There were a lot of dreadnoughts fighting their way up that hill, and the explosions, missile trails and laser blasts cut through and won me the game.
Overall it is amazing how much game play can change with these changes. If I were to do it again I might keep the reduced cost overall, but maybe just 50% off rather than 90%. I liked the larger armies, but it was a crazy experience more like fighting a fire than playing chess.
If you decide to modify the csv files with a text editor (Notepad++ is my text editor of choice) you can do everything I was doing in Excel, it just isn’t formatted into columns to be easy to read. Instead it is raw text like the following:
Modifying the files this way works, you just need to count the amount of fields, remembering that commas separate the fields (CSV stands for Comma Separated Values) to get to the right values.
Adding a new Map to a Mod
It is also possible to add a custom map to a Mod. The in-game map editor will always create a map in the default \Assets\Maps\<mapname> directory. To include that map in your mod, once created you'll need to move the entire map directory into your <ModName>\Maps directory. Once the map is in the mod directory and the game is restarted, the Map Editor will be able to edit the map directly from the mod directory.
Current Limitations (Ashes 2.2)
The Ashes developers are working to expand Modding support, however there are a few significant limtations to the existing modification support.
The following files from the Ashes \Assets\ directory are currently NOT modifiable.
- \Units\: Contains the models and textures for all the units in the game.
- \Buildings\: Contains the models and textures for all the buildings in the game.
- \Formation\FlockerTemplates.csv: Controls the Max Acceleration, Max Velocity, and other movement related parameters.
- \Physics\RigidBodyTemplates.csv: Controls the physics collision dimensions and mass.
If your Ashes instalation with Mods gets into a state where the game fails to load. It is possible to still load the game via safe mode. Safe mode will not load any mods, but will still present the user interface for enabling and disabling mods. You can open the interface, disable the offending Mod, and restart Ashes in the normal mode.
To start safe mode, select the option from the launch menu in steam, or add "-safe" to the command line arguments.
Scripting – Creating Scenarios
Scripting allows you a huge amount of control over what exactly happens on the map you are creating. You can restrict what buildings and units the players can use, set up Triggers to lock or unlock them, spawn units or buildings for the players or their enemies. You can send units to attack specific targets and send dialog popups to the player. Everything you need to make your own custom Scenarios.
All of this is stored in XML, not code. So you don’t need any special programming tools or experience to use it. The best advice for seeing what is possible is to look through the \Assets\Campaign\ and \Scenario\ directories and see what the xml files are doing. Some examples are also included below.
There are three main elements in Ashes scripting: missions, players and triggers. Missions are the definition or the scenario. Players defines the players that are going to be used in the scenario. Triggers are where all the magic happens. Triggers have a lot of elements and options.
Note that all triggers and arguments are case-sensitive.
First, you set up all the menu-related items (what icons/art to use in the Ascendancy Wars screen, etc) and global settings like enabling/disabling creeps and hiding terrain, using a <Mission> tag.
To do much of anything, you'll need to define players next. This is done with individual <Player> tags that enable or disable their AI, sets faction, team, and color, etc.
You'll likely refer to these players later in the script by number, where 0 is the first player defined, 1 is the next, and so on.
Triggers are what control anything you want to happen while the scenario is being played, from spawning starting base to calling waves of attacking enemies or giving players objectives. There are several types of triggers which activate off of different events.
These are the types of triggers you can use in a script, and any specific arguments they support.
- Area - Fires when the human player moves a unit into the area.
- Build - Fires when a human player builds structures or units.
- Destruction - Fires when something specific dies.
- Difficulty - Fires at the beginning of a scenario if the given difficulty was chosen
- NamedCreate - Fires when a specific unit or building is spawned via a script.
- Research - Fires when a player researches a Quantum Upgrade
- Timer - Fires after a delay.
- Var - Fires if a variable meets given criteria
- ZoneCapture - Fires when a region is captured.
These are the commands you can put within a trigger to create gameplay effects.
See the main Commands entry for details.
- ActivateTrigger - Activate another trigger (also can be used to activate the trigger it is called from, making a repeating trigger).
- AreaIndicator - This places a visible indicator on the map to help the player know where they should go to.
- AttackAttackMove - Order an army to move to a specific area, engaging enemies along the way.
- AttackUnit - Order an army to attack a specific script-spawned unit
- Camera - Move the player's view to a specific area.
- CaptureNearestNext - Order an army to capture the nearest neutral or enemy-controlled region
- CaptureNearest - Order an army to clear its order queue and capture the nearest neutral or enemy-controlled region (note: ordered unit will stop moving if region is captured before it gets there)
- ChangeAIDifficulty - Change an AI player's difficulty setting
- ChangeAIPersonality - Change an AI player's personality
- DestroyBuilding - Destroys a specific script-spawned building.
- DestroyUnit - Destroys a specific script-spawned unit.
- Dialog - This creates a popup that can convey information or story to the player. Use with <Entry> tags.
- Entry - The actual text that will be displayed. Use only within <Dialog> tags.
- EndMission - Use to force a win or loss of the scenario.
- GrantStuff - Give a player free resources
- GrantTech - Give a player a free Quantum Upgrade
- HidePanel - Hide UI panels
- LetterBox - disable commands and go to a cinematic, letterbox view
- MoveUnit - Move an army to a location without stopping to fight
- Objective - Use this to set objective notifications for the player (so they know what to do).
- Restrict - To block the player from being able to access objects in the game.
- Reveal - Reveal the fog of war over a location
- SpawnBuilding - Places a building on the map.
- SpawnUnit - Places a unit on the map.
- Var - Set or modify a variable. Tip: Set any variable you want to use to 0 in the initial setup trigger to avoid unpredictable results. All values must be integers.
The UI for Ashes is defined in XML, it is as moddable as the rest of the game. But we just want to make one small change, we want the game to show us the coordinates. Fortunately there is already a field for that in the UI, it’s just marked hidden. You will find the following toward the end of AshesGameView.xml:
To have the coordinates be displayed in game, change this to Hidden=”0”. 0 typically means False and 1 means True so by setting it to 0 we are setting it to “Not Hidden”. You may also want to reduce the FontSize, 20 tends to be fairly large but that is up to you.
This will help you get the exact coordinates when you are playing with your map to figure out where you want to place resources, starting locations for player, where you want events or trigger or where you want to spawn new units.
A single trigger can do any combination of the above options. It can popup some text, spawn some units, set an objective give the player some resources and unlock some new building options. It is up to you how you want to combine and use them. Let’s take a look at some examples.
Send an army to attack
The above trigger is inactive, meaning it needs another trigger to call it before it will activate. Once it does it will spawn 16 units into an army and send them to attack the defined map position. This is a relatively simple trigger, but a common one. With this alone you can create scenarios that spawn waves to attack the player, grant reinforcements to the player or create surprise ambushes.
Reward the player for capturing an area
The above trigger occurs when the player captures the region at the specified position. Notice that the trigger starts inactive, so it would need to be enabled by an earlier trigger before it could occur.
This trigger does the following:
- Checks the Cap_C_Obj objective in the player’s objective list.
- It disables the Cap_B_Ind Area Indicator by setting it’s duration to 0.
- It pops up some dialog for the player.
- It enables the player’s ability to build Metal Extractors.
- It spawns a free Engineer for the player.
- It moves the camera to look at the captured region.
- It adds a new objective for the player (Mex_Built_Obj).
- It gives the player 500 Metal.
- It makes the Cap_C_Trigger trigger active.
This is a great example of the kind of combinations that can be done with the trigger system. This is a reward to the player for capturing the region. But it could as easily have triggered an escalation for the enemy forces.
Creating New Units (Work-in-progress)
With Escalation 2.4, modders are able to introduce their own custom units into the game as mods.
Adding a new unit to Ashes can be a complicated process, so to make it easier for modders to follow along with this guide, we have provided a sample mod of a custom unit called the "Little Boy". The Little Boy <ref name="Little Boy">Little Boy - https://en.wikipedia.org/wiki/Little_Boy</ref>, named after the first atomic bomb deployed during World War II, is a Tier 1 unit that shoots nuclear warheads from its single turret.
Download the tools required to build a unit mod from here: http://downloads.ashesofthesingularity.com/AshesModdingTools.zip
Download the "LittleBoy" sample mod from here: http://downloads.ashesofthesingularity.com/AshesSampleMod.zip
The Anatomy of a Unit
In order for a unit to appear in-game, a series of data (used to configure the visual aspect of the unit) and texture files must exist in the mod's folder structure. These files are:
- Textures (these are .dds files in various formats)
- Ambient Occlusion
- World Space Normals
- Material Masks
- Team Color Masks
The AssetGroup File
The MeshDesc File
The Palette File
The TimelineSet File
Design Guidelines for the 3D Model
- Unit of Measurement: Centimeters (as a point of reference, the Nemesis is 56.75 cm long)
- Ideal Triangle/Quad counts:
- T1 Units:
- T2 Units: 5,000 - 15,000 tris / 2,500 - 7,500 quads
- T3 Units: 40,000 - 60,000 tris / 20,000 - 30,000 quads
- T4 Units: 40,000 - 60,000 tris / 20,000 - 30,000 quads
- All models must be exported as a .FBX file with the triangulation option enabled. If the geometry is not triangulated, an error will be occur during the baking process.
- Each mesh should have its own UV sets.
- In general, every unique mesh should have it's own "palette" (which is represented as a record in an asset's .Palette file) and set of textures. Though, there are some cases where multiple meshes should share the same palette and texture files (i.e. a unit that has multiple guns that are identical).
- Each mesh is required to have a 2nd UV set. This 2nd UV set is used to map a faction specific overlay texture to the model. This overlay texture provides additional details to units (i.e hull patterns). More information about this 2nd UV set will be provided in later sections of this guide. Best practice is to have the 2nd UV set be a copy of the primary UV set. Whenever making changes to the UVs, be sure to reflect the changes in the 2nd UV set (this will likely involve deleting the existing 2nd UV set and recreating it as a copy of the 1st).
- Every model must have a top-level mesh called "Root". All other meshes (i.e. guns, turrets, arms, etc.) must be child meshes beneath this parent "Root" mesh.
Texture Authoring Guidelines and Best Practices
- Author your textures in 4K resolution (3840 x 2160) and scale them down from there when getting them into the game.
- It is advised to NOT use 4K textures for your units in-game as they will likely have a negative impact on the performace of the game due to the large amount of VRAM needed.
- Export your textures from whatever authoring software you are using (i.e. Maya, Substance Designer, etc.) in 3-channel (RGB, no alpha) .tif format.
- Ashes: Escalation expects all textures used in-game to be in .DDS format, but it is a good idea to maintain a "source" copy of your textures in .tif format as they're much easier to iterate on than .dds files. When you're ready to get your textures into the game, you should follow the process described in the following Required Textures and How to Convert Them To DDS Format section for how to generate the .dds version of your textures.
- The best size for your textures covering the main body portion of your new unit (most likely the "Root" mesh) is 2K.
- Of course, there is nothing to stop you from scaling textures down even further if they looks good enough in-game at a smaller size. But, 2K is a good starting point, and at the same time it is definitely a size you don't want to surpass.
- The textures for all the other parts of your unit that are small, like turrets, should be at least 1/2 the size of the main body textures. So, if your main body textures are 2K, your turrets should be no larger than 1K.
- If the turrets are small enough, it is a good idea to experiment with smaller sized textures, like 512 and 256.
- Be sure your textures are sized in increments of the power of 2 so that MIPs can be properly generated during the DDS conversion process.
Required Textures and How to Convert Them To DDS Format
The following textures are required to be defined in the unit's Palette file, and must have the provided DDS format:
- Ambient Occlusion - BC4_UNORM (ex. Root_AO.dds in the LittleBoy mod)
- Diffuse - BC7_UNORM (ex. Root_Color.dds in the LittleBoy mod)
- Curvature - BC5_UNORM (ex. Root_Curvature.dds in the LittleBoy mod)
- World Space Normals - R10G10B10A2_UNORM (ex. Root_Normals.dds in the LittleBoy mod)
- Team Color Masks - BC4_UNORM (ex. Root_TeamColor_MaskArray.dds in the LittleBoy mod)
- Material Masks - BC4_UNORM (ex. Root_Material_MaskArray.dds in the LittleBoy mod)
As a best practice, it is recommended that you export your textures from whatever graphics authoring tool you are using (i.e. Photoshop, Substance Designer, etc.) as .tif files WITHOUT the alpha channel. TIF files make a good medium for iterating on textures, as opposed to trying to make edits to the texture in DDS format (which can be difficult to do, depending on the format).
The Team Color Masks Texture
When setting up a Skirmish or a multiplayer game, the player gets to select up to 3 colors to represent their team. It is the purpose of the Team Color Mask texture to control how those 3 colors are shown on the unit in-game. A combination of these 4 separate masks make up the Team Color Masks texture:
- TC1 - The primary team color mask. Anywhere there is white in this mask, team color #1 will show up.
- TC2 - The secondary team color mask. Anywhere there is white in this mask, team color #2 will show up.
- TC3 - The trim team color mask. Anywhere there is white in this mask, team color #3 will show up.
- Decal - The decal mask. Anywhere that this mask is white, the Diffuse texture is used directly as the color. This mask is will appear on top of TC1, TC2 and TC3 and is the way you would include markings (or "decals") and any other area on your unit that should remain the same color, regardless of the team colors picked by the player.
Using the OxTextureTool.exe tool, these 4 masks are combined into a single DDS file representing the TeamColorMasks texture. Within the package of files for the LittleBoy mode you will find the \SourceArt\maps\MakeTeamColorMask.bat script file. Open up this file to see the process for converting the TC1, TC2, TC3 and Decal mask files into the correct DDS format and then how to merge those 4 DDS files into a single "mask array" texture file. Here are the steps (you can follow allong in the MakeTeamColorMask.bat file):
- (Lines 1-9) Run the texconv.exe tool against each set of TC1, TC2, TC3 and Decal mask files created for each of your palettes (reference the \Units\PHC\LittleBoy\LittleBoy.Palette file for which Palettes have been defined for the LittleBoy mod)
- (Lines 12 & 13) Run the oxtexturetool.exe tool against each set of converted TC1, TC2, TC3 and Decal files output by the texconv.exe tool. Note that the -o argument passed to the oxtexturetool command is the name of the output mask array file you want generated.
It's important to note that the file names used in the \SourceArt\maps\MakeTeamColorMask.bat script file of the LittleBoy mod are specific to the LittleBoy unit, and that you may name these source files however you like.
The Team Color Masks texture is set in the unit's Palette file via the "TeamColorMasks" column. Whatever you provide as the file name that the OxTextureTool.exe tool outputs (via the -o argument) must match what you provide for "TeamColorMasks" column in your unit's Palette file. What you provide for the "teamColorMasks" column in your unit's Palette file must be a path to the file, relative to the root mods directory.
[provide Tools package that contains OxTextureTool, TexConv, EasyBake and some .bat script files]
The Material Masks Texture
The FBX File
The models for all buildings and units in Ashes: Escalation were authored in either Maya or 3dsMax. Of course, this does not mean that other tools like Blender or Modo can't be used. Be aware though that there are minor differences in the ways that each of these 3D modeling tools export FBX files and that their output can be inconsistent between what each tool outputs. This can have the effect of introducing flaws into your model when bringing them into the game.
Baking the Normals
Baking the Asset into the Game
Fatal Error: Assert Fail: pMesh->GetPolygonSize(0) == Model::eNumIndiciesPerPoly File
Models are required to have triangulated polygons.
When running the Texconv, OXTextureTool or EasyBake tools, if you are prompted with an error dialog saying MSVCP140D.dll or VCRUNTIME140D.dll or VCOMP140D.dll is missing:
You will need to install the Visual C++ Redistributable for Visual Studio 2015: https://www.microsoft.com/en-US/download/details.aspx?id=48145
When To Create Additional LODs