A guide to the export_descr_units.txt file

Medieval II - Americas Medieval II - Britannia Medieval II - Crusades Medieval II - Tutonic: Total War: Medieval II - MODs Broken Crescent 1.05 Broken Crescent 2.02 Stainless Steel 5.1b Stainless Steel 6.1 Deus Lo Vult 5.7 Deus Lo Vult 6.0 HTF: Eagle of the Elbe 05 The Long Road 2.0 Lands to Conquer Gold DarthMod 1.4D: The Last Episode. Medieval II: Total War Cheat Codes. Below is a list of ancillaries (with their ANCILLARYNAME) that can be given to Spies and/or Assassins. Unofficial fan site for Medieval 2: Total War, dedicated to bringing you the latest news, guides, FAQ, campaigns, strategies, forums, discussions, information, scenarios, mods, patches,and downloads for the latest game in the Total War series. This is a list of all buildings that are only available to certain factions, and their effect. Military Academy Who: France, Spain, England, Portugal Where: cities What it does: train some faction-specific units, gives command-related traits and ancillaries to governors. Discussing Complete Unit, Trait, and Ancillary List on Medieval 2: Total War PC message board and forum (page 1). TRAINERS CoSMOS REQUESTS QUEUE BOARDS REWARDS SUPPORT We have 27,230 trainers for 6,733 Games.

By Mythic Commodore

This guide assumes that you have unpacked the data files using the method found here.

Once you have successfully unpacked the game's files, you may be wondering where to begin. A good starting point is the export_descr_unit file, or EDU. Here you will find the definitions that tell the game about all of the different soldiers and ships that you will encounter. First, a sample. We will be using Swiss Pikemen as our example. Here is the code which defines Swiss Pikemen:

Looks daunting, huh? ;)

In reality, the file is simple once it gets broken down with each line being analysed. This guide is mainly a line-by-line breakdown, with a brief final section about the file and its limitations.

Part I - The Line-by-Line Breakdown

This part is intended to be more of a reference than anything else. It is not essential for anyone to know what each line does but it helps.

type Swiss Pikemen
type - This line defines the unit's internal lookup name, which is the name that the game uses in its files whenever it refers to a unit. Note that there are two internal lookup names, the other one being defined by the dictionary line. Each one is used in different applications but the names are usually identical, except for where the type line uses spaces, the dictionary line uses underscores. Which files use the type name?

descr_rebel_factions.txt
descr_sm_factions.txt
descr_sounds_units_x.txt
campaign_script.txt
descr_mercenaries.txt
descr_strat.txt
export_descr_buildings.txt

These are the primary examples. As a general rule, if you see a file which references units and no underscores are used, then you must use the type name.

dictionary Swiss_Pikemen ; Swiss Pikemen
dictionary - This line defines the unit's other name, which is the name used in some other applications, including creating unit cards. Note the second part with the semicolon. A semicolon is called a comment. What putting a semicolon into your code will do is tell the game to ignore the rest of that line. So although we see:

dictionary Swiss_Pikemen ; Swiss Pikemen

The game sees:

dictionary Swiss_Pikemen

This is useful for inserting comments. In this case, the developers used it to tell you what the name of the unit is. It may seem self-explanatory, but some units have names which are not the same in the game's files as they are in-game. Retinue Longbowmen and Unhorsed Knights are good examples. Retinue Longbowmen are referred to as Dismounted Longbowmen, while Unhorsed Knights are Dismounted Crusader Knights. In that case, comments are useful.

category infantry
category - This tells the game what troop type this particular unit is. This should be fairly self-explanatory. Options include:

infantry
cavalry
siege
ship

Note that 'wagons' like the Great Cross and the Carroccio Standard fall under the siege class. Although the game lists handler and non_combatant as also being options, those are most likely relics from Rome: Total War days, which should not work.

class spearmen
class - This tells the game what particular type of unit it is. Options include:

light (used with infantry, cavalry, and ships)
heavy (used with infantry, cavalry, and ships)
missile (used with infantry, cavalry, and siege)
spearmen (used with infantry)

Note that if you want to create a 'wagon' like the Great Cross, you would have light as the class - an exception to the other members of the siege category, which only use the missile class.

Fill your library, not your device. ICloud Photos can help you make the most of the space on your Mac. When you choose “Optimize Mac Storage,” all your full‑resolution photos and videos are stored in iCloud in their original formats, with storage-saving versions kept on your Mac as space is needed. Sign in to iCloud to access your photos, videos, documents, notes, contacts, and more. Use your Apple ID or create a new account to start using Apple services. Iphoto.

voice_type Heavy
voice_type - This determines the type of voice used by the unit. The options are:

Light - Use this for ships or for troops that need a weaker-sounding voice (like Peasants)
Heavy - Use this for troops requiring a stronger voice (like Feudal Knights)
General - Use this for a general's bodyguard.

accent German
accent - This optional line will tell the unit to always speak with a particular accent. If this line is not present, then the unit will speak using the accent of the owning faction e.g. if it is owned by England, it will have an English accent. However, because of this line, Swiss Pikemen owned by England will have a German accent. Accents are described in the descr_sounds_accents.txt file and include:

English
Scottish
French
German
Mediterranean
East_European
Arabic
Mongolian

banner faction main_spear
banner faction - This tells the game what sort of banner the unit is to use as its main banner - the really big one. The main banner also specifies the 'mini banners' that show on the unit once you get experience, armour, and weapons upgrades. The available banners are described in the descr_banners_new.xml file and include:

main_spear
main_infantry
main_cavalry
main_missile

Basically, the banner corresponds to the unit type. Of course, you are free to use whichever one you want since the only effect of this line is the banner of the unit. Note that since ships never appear on the battlefield, they do not have this line in their entries.

banner holy crusade
banner holy - A unit will have any of a number of secondary banners which indicate various things. For example, the king will have a 'royal banner'. This optional line defines whether or not the unit will have a secondary banner to indicate that it is on a holy war. Again, this is defined in the descr_banners_new.xml file If this line is present, then the unit will use the indicated banner as a secondary banner on a holy war. The options that you would probably want to use are:

crusade
jihad

If you do not include this line, then the unit will have no secondary banner when on a holy war.

soldier Swiss_Pikemen, 60, 0, 1
soldier - This is the first line with multiple values. They are all separated by commas and do different things. The first value (Swiss_Pikemen, 60, 0, 1) is the soldier model to use. This references an entry in the battle_models.modelsdb file, which determines how the unit looks. Changing this to a different entry will change the look. The second value (Swiss_Pikemen, 60, 0, 1) is the number of men in the unit. This is affected by your size settings in the options page. The smallest possible is 4, while the largest is 60. In the Kingdoms expansion, however, unit sizes can be increased up to 100! The third value (Swiss_Pikemen, 60, 0, 1) is used only with units with 'extras' such as siege equipment. It tells thegame how many

Medieval Total War 2 Ancillary List