MonStats.txt File Guide (v. 2.0)

[rpgkdh]

MonStats.txt File Guide (v. 2.0)

MonStats.txt File Guide
By Nefarius
This guide is based on Kingpin's 1.10 update to my 1.09 MonStats.txt guide.

#I have posted this outside of the fileguide thread because most of the fileguides in there are preliminary as I see it.










ID Settings

ID – this column contains the pointer that will be used in other txt files such as levels.txt and superuniques.txt.

HCIDX – this is the actual internal ID of the unit (this is what the ID pointer actually points at) remember that no two units can have the same ID, this will result in lots of unpredictable behaviour and crashes so please don’t do it. This "HarcCodedInDeX" is used for several things, such as determining whenever the unit uses DCC or DC6 graphics (like mephisto and the death animations of Diablo, the Maggoc Queen etc.), the HCIDX column also links other hardcoded effects to the units, such as the transparency on necro summons and the name-color change on unique boss units (thanks to Kingpin for the info)

BASEID – this column contains the ID pointer of the “base” unit for this specific monster type (ex. There are five types of “Fallen”; all of them have fallen1 as their “base” unit). The baseID is responsible for some hardcoded behaviours, for example moving thru walls (ghosts), knowing what units to ressurect, create etc (putrid defilers, shamans etc), the explosion appended to suicide minions (either cold, fire or ice). Thanks to Kingpin for additional info on this column.

NEXTINCLASS – this column contains the ID of the next unit in the chain. (Continuing on the above example, fallen1 has the ID pointer of fallen2 in here). If you want to make a monster subtype less you should simply leave this blank and make BaseId point at itself (its ID pointer). I assume the game may use this for “map generated” monsters such as the fallen in the fallen camps, which get picked based on area level (the same camp, that in the cold plains contains normal fallen will contain carvers and devilkin elsewhere).






Display Settings I

TRANSLVL – this indicates which palette entry the unit will use, most monsters have a palshift.dat file in their COF folder, this contains 8 palettes (5 of them are used normally), these palettes are used by the game to make the various subtypes appear in “a different light” . Note that some tokens such as FC do not accept any palettes whatsoever.

NAMESTR – this column contains the string-key used in the TBL files to make this monsters name appear when you highlight it. Note that string keys are case sensitive, so if you enter a key like “Foo” in monstats.txt you must enter exactly that in the TBL file! (IE if you enter “foo” or “fOO” you will get a nice “not xlated call ken” or “an evil force” displayed instead of your enemies name).

MONSTATSEX – this column contains the ID pointer to an entry in MonStats2.txt. In 1.10 Blizzard have moved all the graphical aspects (light radius, bleeding etc) to a new file to conserve space (monstats.txt is one column short of 256, the maximum M$ Excel can handle, and that’s what they used for their files I guess).






Other links to external files/code

MONPROP – this column contains the ID pointer to an entry in MonProp.txt. MonProp.txt controls what special modifiers are appended to the unit, for example you can use it to give your monsters random resistances or immunities, give them “get hit skills” and almost anything else (look at the MCML).

MONTYPE – this column contains the group ID of the “super group” this monster belongs to, IE all skeletons belong to the “super group” skeleton. The 1.10 MonType.txt works exactly like ItemTypes.txt, furthermore this file is used for special modifiers. (Additional damage vs. monster-class)

AI – this column tells the game which AI to use for this monster, note that every AI needs a set amount of animation modes (GH, A1, A2, S1, WL, RN etc). If you want to make a melee unit shoot missiles you must edit the COF files for its attack animations to use trigger ID #2 and not trigger ID #1 otherwise the missile will either not be released or won’t do any damage, the same change must also be done in ANIMDATA.D2.






Display Settings II

DESCSTR – this column contains the string-key for the monsters description (leave it blank for no description), IE ever wandered how to make it say something below the monster name (such as “Drains Mana and Stamina etc), well this is how you do it. Just put the string-key of the string you want to display below the monsters name in here.

CODE – this is the only graphical setting (besides TRANSLVL) left in MonStats.txt, this controls which token the game uses for this monster (IE in what folder it looks for animations).






Misc Boolean Settings I

ENABLED – Boolean, 1=enabled, 0=disabled. This controls whenever the unit can be used at all for any purpose whatsoever. This is not the only setting that controls this; there are some other things that can also disable the unit. (RARITY and ISSPAWN columns see those for description)

RANGEDTYPE – Boolean, 1=ranged attacker, 0=melee attacker. This tells the game whenever this is a ranged attacker; I suspect this has to do with the RANGEDSPAWN column in levels.txt. (Could it be the game uses this for preference settings when spawning monsters to avoid areas being populated only with melee monsters, IE the game picks a set amount of monsters for every level, randomly, only based on their rarity values, from those specified in Levels.txt, now I assume that it could pick 4 melee monsters, however in 1.10 Blizzard added a check to prevent this from happening AFAIK and this could be how they control it.)






Nest/Spawner Settings

PLACESPAWN – Boolean, 1=spawner, 0=not a spawner. This tells the game whenever this unit is a “nest”. IE, monsters that spawn new monsters have this set to 1. Note that you can make any monster spawn new monsters, irregardless of its AI, all you need to do is adjust these four columns and make sure one of its skills is either “Nest” or “Minion Spawner”.

SPAWN – this column contains the ID pointer of the unit to spawn. (in case it is a spawner that is), so if you want to make a new monster that generates Balrogs this is where you would put the Balrogs ID pointer.

SPAWNX, SPAWNY – the x/y offsets at which spawned monsters are placed. IE. This prevents the spawned monsters being created at the same x/y coordinates as the spawner itself, albeit its not needed, Blizzards collision detection system is good enough to prevent them from getting stuck.

SPAWNMODE – which mode will the spawned monster be spawned in. IE. If you make a golem summoner (yes I know, “very original”) you could put S1 in here to make it look as if the golems are really summoned (otherwise they would just appear).






Group and Minion Settings

MINION1, MINION2 – these columns contain the ID pointers to the minions that spawn around this unit when it is created. Lets say you want your super-strong boss to spawn with 5 Oblivion Knights. To do this you would simply enter the Oblivion Knights ID pointer in the MINION1 column. And set PARTYMIN and PARTYMAX both to 5. MINION1/2 are used for several other things. If the monster spawns as unique or superunique then it will have the unit from MINION1/2 set as its minion instead of monsters of its own type. That’s why Lord De Seis doesn’t spawn with other oblivion knights anymore. To semi-circumvent this I suggest you simply put the monsters ID pointer in the MINION2 column (I.E. if you give the Oblivion Knights their own ID pointer in MINION2, Lord De Seis should spawn with both Doom Knights and Oblivion Knights again). The other use controls what monster is created when this unit dies. For example Flayer Shamans will spawn a regular Flayer when they are killed. To enable this you must set SPLENDDEATH to 1, make sure the unit you spawn this was has a raise or resurrect sequence otherwise it will look weird (but it works).

SETBOSS – Boolean, 1=set unit as boss, 0=don’t set unit as boss. The original guide stated that this controls which type of minion the unit spawns with when it’s a boss. This column however does not influence this behaviour. I believe this has to do with AI (IE some units can pass on commands to their minions, maybe this specifies which unit can do so).

BOSSXFER – Boolean, 1=true, 0=false. Unknown, either related to boss modifiers (Lightning enchanted etc) or to AI.

PARTYMIN, PARTYMAX – How many minions are spawned together with this unit. As mentioned above in the MINION1/2 columns, this controls the quantity of minions this unit has. Id avoid setting this to more 15.

MINGRP, MAXGRP – Exactly like the previous two columns, just that this controls how many units of the base unit to spawn. In the past (1.00-1.06), setting the minimum to more then 99 would crash the game. I am not aware if this also occurs in 1.07-1.10 but I’d avoid doing it anyway.





Population Control and Dynamics Settings I

SPARSEPOPULATE – This column is a great tool for us balance freaks. This is like a “second layer of security” when it comes to population control. Lets say you have a really tough enemy and want it to occur less densely then the other monsters in a level. So, you have the choice of either lowering MONDEN (levels.txt) or MINGRP and MAXGRP. But this would in every case not produce exactly what you want, lowering MONDEN would make the monster population, irregardless of type less dense and lowering the amount of monsters in the group wouldn’t help either (it would possibly make your tough monster easier then you want). So what to do? This column controls the overall chance something will spawn (0-100%), Leaving it blank is the same as 100%. If you enter “80” in this column then whenever the game chooses to spawn this unit it will first roll out the chances. So in 2 out of 10 cases the monster will not be spawned. Setting it lower then 50 is however not recommended. Note, this does not mean that lower values don't work or do something bad. In case the game doesn't roll out the monster and this monster has units specified in minion1/minion2 columns it will only spawn those minions without the "main" unit.






Velocity Settings

VELOCITY, RUN – controls the walking and running speed of this monster (respectively), note that RUN is only used if the monster has a RN mode and its AI uses that mode. I’d suggest staying below 25 on this one.






Population Control and Dynamics Settings II

RARITY – This one also helps controlling the monster population, it controls the overall odds that this monster will be spawned. I.E. Lets say in levels.txt you have two monsters set to spawn Monster A has a rarity of 10 whereas Monster B has a rarity of 1 and the level in question is limited to 1 monster type. First the game sums up the chances (11) and then calculates the odds of the monster spawning. Which would be 1/11 (9% chance) for Monster B and 10/11 (91% chance) for Monster A, thus Monster A is a lot more common then monster B. If you set this column to 0 then the monster will never be selected by Levels.txt (for obvious reasons, and I dare to say, it could lead to a crash if this is the only monster to spawn on the level, it would lead to a division by zero, unless Blizzard added some double checks here).






Level Settings

LEVEL, LEVEL(N), LEVEL(H) – Controls the monsters level on the specified difficulty. This setting is only used on normal, on nightmare and hell (thus the two later columns are actually obsolete) the monsters level is identical with the area level. I did some tests on this and found it to not matter if the level is higher or lower. It will be set to it indefinitely. Note that the monsters level is used by the game to eval‎uate the stats the monster will have in 1.10 (look at the stats section for more info).






Sound Settings

MONSOUND – Specifies the ID pointer to this monsters “Sound Bank” in MonSound.txt when this monster is normal.

UMONSOUND – Specifies the ID pointer to this monsters “Sound Bank” in MonSounds.txt when this monster is unique or champion. For Superunique monsters this is controlled by SuperUniques.txt.






AI Settings

THREAT – Used by the games Threat Rating System to tell AIs which unit to target first. The higher this is the higher the Threat level. So I guess setting this to 25 or so on Maggot Eggs would make your Merc try to destroy those first.

AIDEL, AIDEL(N), AIDEL(H) – The controls delays between AI ticks, however how exactly this is used is still shrouded in mystery. Its likely that each AI may use this in a sightley different fashion. In general however, the higher the number the slower something should become (after all the delay increases that way), what part of the AI this delay applies to however is uncertain due to the quantity of different observations.

AIDIST, AIDIST(N), AIDIST(H) – The distance in cells required for this AI to be enabled. This is only used for mephisto on nightmare and hell, I assume the game otherwise uses some hardcoded default value. For the units “Radius of Awareness”.

AIP1-8, AIP1-8(N), AIP1-8(H) – These cells pass on parameters (usually in percentage) to the AI code. For descriptions about what all these AIs do check MonAI.txt. Note that some AIs are very badly or not at all, explained there (“Thanks” Blizzard!). Many people have trouble with the AI of the Imps, this AI is special and uses multiple rows, to understand what the cells do look at the original monstats.txt file (from D2EXP.MPQ).






Projectile Settings

MISSA1, MISSA2, MISSS1, MISSS3, MISSS4, MISSC, MISSSQ – These columns control “non-skill-related” missiles used by the monster. For example if you enter a missile ID pointer (from Missiles.txt) in MissA1 then, whenever the monster uses its Attack1 Mode it will shoot a missile, this however will not work properly if 1. The COF files of A1 use the #1 trigger (to get it to work change the trigger in the COF files and in ANIMDATA.D2 to #2). And 2. If the AI of the monster doesn’t support missiles it will usually look very weird (but this can sometimes create nice effects). For the beginners, A1=Attack1, A2=Attack2, S1=Skill1, S2=Skill2, S3=Skill3, S4=Skill4, C=Cast, SQ=Sequence.





Misc Boolean Settings II (especially NPC related!)

ALIGN – Switch, 1=aligned, 0=enemy, 2=neutral. This setting controls whenever the monster fights on your side or fights against you (or if it just walks around, IE a critter). If you want to turn some obsolete NPCs into enemies like I usually do this is one of the settings you will need to modify. Setting it to 2 without adjusting other settings (related to AI and also some in MonStats2) it will simply attack everything.

ISSPAWN – Boolean, 1=spawnable, 0=not spawnable. This controls whenever this unit can be spawned via Levels.txt.

ISMELEE – Boolean, 1=melee attacker, 0=not a melee attacker. This controls whenever this unit can spawn with boss modifiers such as Multiple Shot or not. IE Melee monsters will never spawn with MS.

NPC – Boolean, 1=I’m a NPC, 0=I’m not. This controls whenever the unit is a NPC or not. See below.

INTERACT – Boolean, 1=Special NPC features enabled, 0=No special NPC features.
This controls whenever you can interact with this unit. IE. This controls whenever it opens a speech-box or menu when you click on the unit. To turn units like Kaeleen or Flavie into enemies you will need to set this to 0 (you will also need to set NPC to 0 for that).

INVENTORY – Boolean, 1=Has an inventory, 0=Has no inventory. Controls whenever this NPC or UNIT can carry items with it. For NPCs this means that you can access their Inventory and buy items (if you disable this and then try to access this feature it will cause a crash so don’t do it unless you know what you’re doing). For Monsters this means that they can access their equipment data in MonEquip.txt.

INTOWN – Boolean, 1=I can enter towns, 0=I can’t enter towns. This controls whenever enemies can follow you into a town or not. This should be set to 1 for everything that spawns in a town.






Type Settings

LUNDEAD – Boolean, 1=True, 0=False. Blizzard used this to differentiate High and Low Undead (IE. Low undead like Zombies, Skeletons etc are set to 1 here), both this and HUNDEAD will make the unit be considered undead so I don’t see how these two actually differ. This may have to with the Unravelers resurrecting behaviour (IE they only ressurect low undead), thanks to Brother Laz for this input.

HUNDEAD – Boolean, 1=True, 0=False. This is usually set for large magical undead monsters Lichs, Unravelers etc. See comments under the previous column.

DEMON – Boolean, 1=True, 0=False. This makes the game consider this unit a demon.






Misc Boolean Settings III

FLYING – Boolean, 1=I can fly, 0=I can’t fly. If you set this to 1 the monster will be able to move fly over obstacles such as puddles and rivers.

OPENDOORS – Boolean, 1=I can open doors, 0=I’m to stupid to open doors. Ever wanted to make the game more like D1 (where closing doors could actually protect you), then this column is all you need. By setting this to 0, the monster in question will not be able to open doors any more.

BOSS – Boolean, 1=I’m a boss, 0=I’m not a boss. This controls whenever this unit is a special boss, monsters set as boss IGNORE the level settings, IE. they will always spawn w the levels specified in MonStats.txt. Setting this to 1 for monsters does not cause a crash in 1.10. The only effects it has are that the monster will always use the mlvl specified in MonStats.txt (and it will probably gain the special boss resistances, IE it will not be effected by things like Deadly Strike the way normal monsters are. Though I didn't have time to do test on this yet)

PRIMEEVIL – Boolean, 1=I’m a prime evil, 0=I’m not a prime evil. (=Act Boss). Changing this could lead to unpredictable results, however I assume this controls the Act Boss Specific resistances to special damage modifiers (like Deadly Strike etc).

KILLABLE – Boolean, 1=Mortal, 0=Immortal. Setting this to 0 will make the monster unkillable. There is no reason to set this to 1 for enemies, it will just result in your userbase decreasing.

SWITCHAI – Boolean, 1=Can chance sides, 0=Cannot change sides. Can this units mind be altered by “mind altering skills” like Conversion, Revive etc.

NOAURA – Boolean, 1=Can’t get an aura, 0=Can get an aura. Monsters set to 0 here will not be effected by friendly auras.

NOMULTISHOT – Boolean, 1=Can’t get multishot modifier, 0=Can get multishot modifier. This is another layer of security to prevent this modifier from spawning, besides the ISMELEE layer.

NEVERCOUNT – Boolean, 1=Never accounted for, 0=Accounted for. Unknown but I assume this may have to do with population dynamics and level building. Some also believe this may be related to multi-missile attacks.

PETIGNORE – Doesn't work in 1.10 anymore (thanks Snowknight), previously it was a Boolean, 1=Summons ignore this unit, 0=Summons notice this unit. If you set this to 1 this monster will not be targeted by summons (and mercs?) irregardless of its THREAT level.

DEATHDMG – Boolean, 1=Damage players colliding with my death animation, 0=Don’t damage anything. This works similar to corpse explosion (its based on hitpoints) and damages the surrounding players when the unit dies. (Ever wanted to prevent those undead stygian dolls from doing damage when they die, this is all there is to it)

GENERICSPAWN – Boolean, 1=Use generic spawning, 0=Don’t use generic spawning. Unknown but probably has to do with population dynamics and level building like NEVERCOUNT.

ZOO – Boolean, 1=true, 0=false. Unknown it could be related to AI when this unit spawns as part of a boss pack, but this is just a wild guess rather then knowledge.






Skill Settings

SENDSKILLS – Switch, 1=Unknown, 2=Used for assassin traps, 0=Don’t send skills. This is only used by two of the Assassin traps, but what exactly it is used for is unknown.

SKILL1-8 – The ID Pointer to the skill the monster will cast when this specific slot is accessed by the AI. (from Skills.txt). Which slots are used is determined by the units AI.

SK1MODE-SK8MODE – The graphical MODE (or SEQUENCE) this unit uses when it uses this skill.

SK1LVL-SK8LVL – The skill level of the skill in question. This gets a bonus on nightmare and hell which you can modify in DifficultyLevels.txt.






Resistance Settings

DRAIN, DRAIN(N), DRAIN(H) – Controls the effectiveness of Life and Mana steal equipment on this unit on the respective difficulties. 0=Can’t leech at all. (negative values don't damage you, thanks to Doombreed-x for testing this), setting it to more then 100 would probably make LL and ML more effective. Remember that besides this, Life and Mana Steal is further limited by DifficultyLevels.txt.

COLDEFFECT, COLDEFFECT(N), COLDEFFECT(H) – Controls the effectiveness of cold damage on this unit. The lower this value is, the more speed this unit looses when its frozen. –100 will probably make it stop completely. Positive values will make the unit faster (thanks to Brother Laz for confirm‎ing my assumption), and 0 will make it unfreezeable. The cold length is NOT effected by this, for cold length and freeze length settings refer to DifficultyLevels.txt.


HINT: If you want to give units random resistances and immunities you can use MonProp.txt.

RESDM, RESDM(N), RESDM(H) – Damage resistance on the respective difficulties. Negative values mean that the unit takes more damage from this element, values at or above 100 will result in immunity.

RESMA, RESMA(N), RESMA(H) – Magic resistance on the respective difficulties. Negative values mean that the unit takes more damage from this element, values at or above 100 will result in immunity.

RESFI, RESFI(N), RESFI(H) – Fire resistance on the respective difficulties. Negative values mean that the unit takes more damage from this element, values at or above 100 will result in immunity.

RESLI, RESLI(N), RESLI(H) – Lightning resistance on the respective difficulties. Negative values mean that the unit takes more damage from this element, values at or above 100 will result in immunity.

RESCO, RESCO(N), RESCO(H) – Cold resistance on the respective difficulties. Negative values mean that the unit takes more damage from this element, values at or above 100 will result in immunity.

RESPO, RESPO(N), RESPO(H) – Poison resistance on the respective difficulties. Negative values mean that the unit takes more damage from this element, values at or above 100 will result in immunity.






Misc Settings

DAMAGEREGEN – This controls how much health this unit regenerates. Sometimes this is altered by the units AI. The formula in 1.09 was (REGEN * HP) / 4096. So a monster with 200 hp and a regen rate of 10 would regenerate ~0,5 HP every frame.

SKILLDAMAGE – ID Pointer to the skill that controls this units damage. This is used for the druids summons. (I.E. their damage is specified solely by Skills.txt and not by MonStats.txt)






Stat Settings

NORATIO – Boolean, 1=Don’t use MonLevel.txt, 0=Use MonLevel.txt. Does this unit use MonLevel.txt or does it use the stats listed in MonStats.txt as is. Setting this to 0 will result in an array of problems, such as the appended elemental damage being completely ignored, irregardless of the values in it.

NOSHLDBLOCK – Boolean, 1=Can block without a blocking animation, 0=Can’t block without a blocking animation. Quite self explanatory, in order for a unit to block it needs the BL mode, if this is set to 1 then it will block irregardless of what modes it has.

TOBLOCK, TOBLOCK(N), TOBLOCK(H) – This units chance to block. See the above column for details when this applies or not. Monsters are capped at 75% block as players are AFAIK.

CRIT – This units chance of scoring a critical hit.

Hint: The values below are percentages (if NORATIO is set to 0). The game first checks the monsters level and then uses these percentages to calculate the actual stats from the “general stats” listed in MonLevel.txt. This is done by regular percentage calculation, IE: S/100*P (S=Stat, P=Percentage). As an example, if your monster is level 50, and has 200 listed in MINHP in MonStats.txt and the “general stat” for HP at mlvl 50 is 100 then the following calculation is done: 100/100*200 which results in 200 HP. In the same way, if S=300 and P=200 the result will be 600. If you want the game to use the values directly from monstats.txt and don’t want to set NORATIO to 0 (to avoid the bugs related to doing that), simply change all entries in MonLevel.txt to 100).

MINHP, MAXHP, MINHP(N), MAXHP(N), MINHP(H), MAXHP(H) – This units minimum and maximum HP on the respective difficulties.

AC, AC(N), AC(H) – This units Armor Class on the respective difficulties.

EXP, EXP(N), EXP(H) – The experience you get when killing this unit on the respective difficulty.

A1MIND, A1MAXD, A1MIND(N), A1MAXD(N), A1MIND(H), A1MAXD(H) – This units minimum and maximum damage when it uses Attack 1.

A2MIND, A2MAXD, A2MIND(N), A2MAXD(N), A2MIND(H), A2MAXD(H) – This units minimum and maximum damage when it uses Attack 2.

S1MIND, S1MAXD, S1MIND(N), S1MAXD(N), S1MIND(H), S1MAXD(H) – This units minimum and maximum damage when it uses Special Attack 1 (or Skill 1), usually used for missiles like Arrows etc.

A1TH, A1TH(N), A1TH(H) – This units attack rating for Attack 1 on the respective difficulties.

A2TH, A2TH(N), A2TH(H) – This units attack rating for Attack 2 on the respective difficulties.

S1TH, S1TH(N), S1TH(H) – This units attack rating for Special Attack 1 (or Skill 1) on the respective difficulties. Usually used for missiles like Arrows etc.






Xtra Elemental Damage Settings

HINT: These columns are not used correctly if you set NORATIO to 1. (thanks to Sduibek for finding this stupid little typo that snuck in here)

EL1MODE-EL3MODE – The mode to which the elemental damage is appended. The modes to which you would usually attack elemental damage are A1, A2, S1, S2, S3, S4, SQ or C as these are the only ones that naturally contain trigger bytes.

EL1TYPE-EL3TYPE – The type of the elemental damage appended to an attack. There are several elements: fire=Fire Damage, ltng=Lightning Damage, cold=Cold Damage (uses duration), pois = Poison Damage (uses duration), mag=Magic Damage, life=Life Drain (the monster heals the specified amount when it hits you), mana=Mana Drain (the monster steals the specified amount of mana when it hits you), stam=Stamina Drain (the monster steals the specified amount of stamina when it hits you), stun=Stun Damage (uses duration, damage is not used, this only effects pets and mercs, players will not get immobilized but they will get thrown into hit recovery whenever they get hit by an attack, no matter what type of attack it is, thanks to Brother Laz clearing this one up), rand=Random Damage (uses duration, either does Poison, Cold, Fire or Lightning damage, randomly picked for every attack), burn=Burning Damage (uses duration, this damage type cannot be resisted and shouldn’t be used), frze=Freezing Damage (uses duration, this will effect players like normal cold damage but will freeze and shatter pets). If you want to give your monster knockback use MonProp.txt.

EL1PCT-EL3PCT, EL1PCT(N)-EL3PCT(N), EL1PCT(H)-EL3PCT(H) – Chance to append elemental damage to an attack on the respective difficulties. 0=Never append, 100=Always append.

EL1MIND-EL3MIND, EL1MAXD-EL3MAXD, EL1MIND-EL3MIND(N), EL1MAXD-EL3MAXD(N), EL1MIND-EL3MIND(H), EL1MAXD-EL3MAXD(H) – Minimum and Maximum elemental damage to append to the attack on the respective difficulties. (See the hints under the Stat Settings section, this uses the same calculations). Note that you should only append elemental damage to those missiles that don’t have any set in Missiles.txt.

EL1DUR-EL3DUR, EL1DUR(N)-EL3DUR(N), EL1DUR(H)-EL3DUR(H) – Duration of the elemental effect (for freeze, burn, cold, poison and stun) on the respective difficulties.






Treasureclass Settings

HINT: Because of the new Treasureclass system introduced in 1.10 these entries are only of minor influence regarding what TC is being selected unless you change the system by editing TreasureClassEX.txt.

TREASURECLASS1, TREASURECLASS1(N), TREASURECLASS1(H) – The Treasureclass used by this unit as a normal monster on the respective difficulties.

TREASURECLASS2, TREASURECLASS2(N), TREASURECLASS2(H) – The Treasureclass used by this unit as a champion on the respective difficulties.

TREASURECLASS3, TREASURECLASS3(N), TREASURECLASS3(H) – The Treasureclass used by this unit as a unique or superunique on the respective difficulties.

TREASURECLASS4, TREASURECLASS4(N), TREASURECLASS4(H) – The Quest Treasureclass used by this monster. (For example, the act bosses always have better odds of dropping rare, set and unique items the first time you kill them).

TCQUESTID – The ID of the Quest that triggers the Quest Treasureclass drop.

TCQUESTCP – The ID of the Quest State that you need to complete to trigger the Quest Treasureclass trop.






Special Settings

SPLENDDEATH – Switch, 0=no special death, 1=spawn the monster in the MINION1 column when I die, 2=kill whatever monster is mounted to me when I die (used by guard towers that kill the imps that are on top of them when they die I guess).

SPLGETMODECHART – Boolean, 1=Get Special Mode Chart, 0=Don’t get special mode chart. Unknown but could be telling the game to look at some internal table. This is used for some Act Bosses and monsters like Putrid Defilers.

SPLENDGENERIC – Boolean, 1=true, 0=false. Works in conjunction with SPLCLIENTEND, this makes the unit untargetable when it is first spawned (used for those monsters that are under water, under ground or fly above you)

SPLCLIENTEND– Boolean, 1=true, 0=false. Works in conjunction with SPLENDGENERIC, this makes the unit invisible when it is first spawned (used for those monsters that are under water, under ground or fly above you), this is also used for units that have other special drawing setups.






EOL

EOL – End of Line, used to avoid the trailing bit error M$ Excel usually causes when adjusting the end of the rows. This column must contain 0 unless you want to crash when the game loads.






















Subsequently updated BOSS column (and related ones).