Atlan Config File
Atlan Mod Loader uses darkagesmod.txt as the configuration file for DOOM: The Dark Ages mods. If you're making a mod for DOOM: Eternal, you should use atlanmod.txt as your file name. Including a config in your mod zip is optional, but highly recommended!
The config file consists of several optional properties.
ModInfo Chunk
The ModInfo properties are the only ones that should be included in every config file. Here is an example:
modinfo = {
name = "Your Awesome Mod"
game = "Doom The Dark Ages"
author = "Your Name Here"
description = "Your Mod Description"
version = "3.0"
loadPriority = 1
requiredVersion = 1
}
| Property Name | Description |
|
name |
Your mod's name. Displayed in the Mod Manager |
|
game |
What game this mod is made for. Atlan will not install DOOM: Eternal mods in DOOM: The Dark Ages and vice versa |
| author | Author information. Displayed in the Mod Manager |
| description | Your mod's description. Displayed in the Mod Manager |
| version | Your mod's version. Displayed in the Mod Manager |
| loadPriority | If multiple mods edit the same file, their load priority is used to help resolve conflicts. Mods with a lower load priority override mods with a higher load priority |
| requiredVersion |
The version of Atlan Mod Loader you must be running to load this mod.
|
Aliasing Chunk
The aliasing block is optional. It is meant to help with mod files whose paths are extremely long and convoluted. You may choose to name the files something simple, then alias them to their real asset paths.
The format for an alias is "Real Path In Zip File" = "Game Asset Path"
aliasing = {
"my_first_decl.decl" = "decls/ability_dash/my_ability_dash_decl.decl"
"other/my_second_decl.decl" = "decls/ability_dash/default.decl"
}
Assets, MapSpec, and MapResources Chunks
These chunks are used for assets info manipulation. These are advanced properties that require some experience to use correctly. Their usage is explained in-depth on this page
Load Level Chunk
This chunk enables idStudio level mods that were installed by Atlan. You can use it to load any number of level mods.
// This example causes two idStudio level mods to be loaded
// Their respective installation paths would be:
// 1. base/modarchives/coop_hordamex/
// 2. base/modarchives/pvp_hurricane/
load_level {
coop_hordamex
pvp_hurricane
}
Atlan Mod Packager requires this property to be set when packaging an idStudio level mod.
Total Overhaul Property
This property should only be used under very rare circumstances. Does your mod touch hundreds of files or edit dozens of levels? Does this make it fundamentally incompatible with other mods of similar size? You may wish to designate it as a "total overhaul" mod. Atlan will only allow one Total Overhaul mod to be loaded at a time.
modinfo {
total_overhaul
}
Elevated Gameplay Property
This property only exists for DOOM: Eternal multiplayer gamemode mods. It shouldn't be used anywhere else. When set, only your mod can load gameplay-affecting files. Any gameplay-affecting files in other mods will fail to load. Only one Elevated Gameplay mod can be loaded at a time. The intent of this feature is to prevent players from accidentally cheating in competitive modded multiplayer by unknowingly loading other gameplay-affecting mods.
modinfo = {
elevated_gameplay
}
No comments to display
No comments to display