The Barbarian Paper is designed to assist Civilization II scenario builders who wish to use the randomly appearing barbarians in their scenarios. By coordinating story progression with the discovery of the trigger technologies that cause changes to barbarian appearances, a great deal of challenge, depth, and atmosphere can be added to advanced scenario designs.

This paper applies the following civ2 game versions: Classic Civ2, Conflicts in Civilization, Fantastic Worlds, and Multi-Player Gold Edition. In the Test of Time environment barbarian behavior and appearance differ significantly from what is outlined in this paper.

Version 1.0 included only the quick lookup tables and a minimum of explanatory text. The rebellion entries for Mobile Warfare and Guerrilla Warfare had errors and/or omissions in this version.

Version 1.1 corrects previous errors. The mode chart from version one has been sub-divided into six tables each with verbose, beginner oriented explanations. Also included is a outline of the Barbarian Activity option.

Version 1.11 includes additional information: brief discussion of the number of barbarians in rebel hordes and pirate vessels and an explanation of unit support for mercenaries from goody huts.

Version 1.12 includes information on Barbarian Wrath, a new found level of barbarian activity beyond Raging Hordes.

Version 1.13 includes information on the longevity of barbarian units and their behavior based on role and domain.

Version 1.14 adds new information on barbarian leaders and the formula to determine the cost to bribe barbarian units.

Version 1.2 corrected the units type that appears with Fanatics. Several new sections added; adds new information on barbarian leaders and the formula to determine the cost to bribe barbarian units and cities.

The best advice I could give to the fledgling scenario designer is to know what level of barbarian activity you want BEFORE you create the your scenario. Once the scenario file is created there are only two ways to change this setting; hex editing, and CivTweak. If in doubt I suggest using the Villages Only option, as this is the easiest level of barbarian activity to work with.

The Villages Only setting produces barbarians units only when one of your ground units enters a square containing a minor tribe village. Villages (hereafter referred to as goody huts) produce both friendly (mercenaries) and unfriendly units (hordes). Pirates and rebels do not appear when the Villages Only option set.

With the Roving Bands setting pirates and rebel bands begin to appear, but with half the frequency of the restless tribes setting and in smaller numbers.

The Restless Tribes option is the standard setting for barbarian activity.

Raging Hordes produces the largest number of barbarians. Rebel bands of up to 39 barbarian units have been reported at this setting.

Barbarian Wrath is a level of barbarian activity that can not normally be chosen, it is only achievable through hex editing. Rebel bands number between 75 and 100 barbarian units. The number of piratical barbarian units appearing is normal however.

To eliminate all barbarian activity in your scenario choose the Villages Only option when selecting the level of barbarian activity. Then after creating the scenario file toggle the menu option Cheat> Scenario Parameters > Wipe All Goody Boxes.

Goody huts will produce friendly units (hereafter referred to as mercenaries) that join the player's standing army and unfriendly units (hereafter referred to as hordes) that surround and attack the player's discovering unit.

The tables below are listed in order of precedent with technologies at the bottom of the table having precedent over technologies listed above them. Goody huts will always produce units of the highest level of precedence. For example, if Chivalry is discovered after Monotheism then goody huts will continue to produce Crusader mercenary units since crusaders have a higher level of precedence then knights.

At any given point in the game goody huts will produce a minimum of two types of units. I have broken these varieties up into two logical groups (A and B). Mercenary units will come from group A about 67% of the time and from group B 33%.

Mercenary units obtained from goody huts will be supported by the city closest to the hut. Should the closest city not be yours then the unit will have support of None.

Table for Group A is broken up into three columns. Units from Group A may come from any of the three columns. The probability of a unit coming from any of the three columns is equal.

Tip: Assigning Conscription (Csc) to one or more civilizations at the beginning of the scenario will minimize the number of units slots used by barbarian units.

All the technologies listed on Table 3 are required to produce unit listed to the right of it. For example, if Gunpowder is discovered prior to Iron Working then huts will continue to produce Archers until Iron Working is discovered at which time Musketeers will be produced skipping Legions altogether.

Tip: The removal of Iron Working (Iro) from the technology tree will minimize the number of unit slots used by barbarian units.

Hostile barbarian hordes appear in the squares surrounding the goody hut and can number from one unit up to as many as eight units. The types of units appearing depend on the discovery of key technologies and the type of terrain the barbarian unit appears in.

Tip: Assigning Guerrilla Warfare (Gue) to one or more civilizations at the beginning of the scenario will minimize the number of units slots used by barbarian units. 

Beginning on game turn sixteen rebels bands begin to appear in wilderness areas on the periphery of settled regions. The owner of the closest city will receive a warning message when they appear.

Rebel bands start off with two units then grow in size over time. Although the exact formula for calculating the number of rebel units comprising a band is unknown we do know that it is tied to the game turn; the greater the game turn the more barbarians appear. The number appearing is also influenced by technological discovery; advances that trigger a change in the barbarian type, like gunpowder for example, reset the number of units appearing back to two again.

The first four units of the band will be of the primary unit type. The next four will be of the secondary unit type. Units nine through twelve will be primary; thirteen though sixteen will be secondary, etc.

There is an equal probability of a band being of Group A or Group B with the exception of the Gue category. Fanatics will appear in densely populated areas and Partisans in more remote areas.

Sea-borne barbarians begin to appear on game turn sixteen. These groups will be comprised of one vessel, a leader, and some number of regular pirate units from Table 6 below. These pirate units will number two plus one for every full one hundred game turns elapsed. Thus, if you are on game turn 350 then each pirate ships will have five piratical units plus one leader. The chance of these units being from Group A or Group B is equal.

Pirates appear in a random ocean square and will continue to roam the seas (or pond) until they find a suitable landing site. What pirates consider suitable is any land square within six squares of any city (including barbarian cities). The owner of the closest city will receive message warning of their landing.

After all its units have disembarked the Barbarian vessel will vanish, if the vessel has a hold (carrying capacity) greater then zero defined in the RULES.TXT file.

Tip: Assigning Mobile Warfare to one or more civilizations at the beginning of the game prevents piratical units from ever appearing.

(37.25 / Distance + 2) * (1 + Treasury / 750) * Shields = Cost to Bribe

Distance refers to the distance from the capital. Normally barbarians have no capital so Distance is equal to 16. However, if the bribing civ operates under a communist government the Distance reduced to 10. On average, it is 40% more expensive for a communist civilization to bribe barbarian units.

Treasury is the amount of gold in the Barbarian Treasury. Normally this is zero, but it can be modified by hex editing or using the civtweak utility.

Shields is the number of shields required to build the unit.

Double the Cost to Bribe if the unit is a settler type (role=5).

Immunity to Bribery is granted to any civilization, including the Barbarians, that operate under a Democratic government.

Judging from the low cost to incite a revolt in a Barbarian city one would naturally assume that the game uses a different formula for the Barbarians the it does for the seven "real" civilizations. The difference is due to the Barbarians lack of gold in their treasury and the absence of a capital (the palace improvement) not a unique formula. The complete formula, in all its glorious complexity, is covered in the city bribery paper - Inciting a Revolt. A truncated version of that formula is presented below.

Cost to Incite Revolt = City Size * 52.63 (or 76.92)

When the bribing civilization operates under Communism multiply by 76.92, all other government types use 52.63 instead. Round up in both cases.

The Cost to Incite Revolt is modified by following (these modifiers are cumulative):

A Spy incites revolts at 5/6 the price of a diplomat.
A Veteran Spy incites revolts at 2/3 the price of a diplomat.
Disorder in the revolting city reduces the price by 1/2.
No Units in the revolting city also reduces the price by 1/2.
The Previous Owner of a city can incite a revolt at 1/2 price.

The minimum amount of gold the barbarians will demand is equal to the City Size * 25. But, not less then fifty in any case.

• They simply conquer the city if less than the minimum demanded gold there is in the treasury.
  
• The Barbarians will demand the minimum amount if your treasury has at least equal to minimum demanded gold and less then twice the minimum.
• Half of the treasury will be demanded iof nations with more than twice the minimum demanded gold. Rounded fractions down. If the treasury contains 203 gold, they'll ask for 101.

Once paid, the threatening Barbarians vanish - the whole group.

During the game various barbarian activities can cause messages to appear. Listed below are those messages. Each is located in the GAME.TXT file. Included with each is the reason why they occur and how to modify them.

Barbarian Surprise
This message appears when you open a goody hut and barbarians pour out.

@SURPRISEBARB
@width=300
@title=Village
You have unleashed a horde of barbarians!

Leader Captured!
The simple explanation for this message is that it is displayed when a barbarian leader is killed. However, the truth is that whenever a barbarian unit with a role of 5, 6, 7 is killed this message is displayed. This is true even when the unit is not from the diplomat slot.

@RANSOM
@width=300
@title=Defense Minister
Barbarian leader captured! %NUMBER0 gold ransom paid.

%NUMBER0 is determine by the level of Barbarian Activity in the game.
Along with this message a picture of the barbarian leader unit is displayed even if the unit killed that triggered the message was not a barbarian leader.

Barbarian Landing
When a piratical group of barbarians disembark from their vessel this message appears to the civilization who owns a city closest to the landing spot (or perhaps to the vessel; not sure).

@BARBARIANSLAND
@width=320
@title=Defense Minister
Barbarian raiding party lands near %STRING0. Citizens are alarmed.

%STRING0 is the name of the closest city.

Barbarian Rebellion
This message is triggered when a barbarian Rebellion occurs.

@BARBARIANS
@width=320
@title=Traveller's Report
%STRING0 near %STRING1!

%STRING1 is the name of the closest city.

%STRING0 comes from the LABELS.TXT file. Specifically, one of the five lines from the following table.

The Barbarian Threat
This is the message you get when a barbarian unit is about to capture your city.

@RANSOMCITY
@width=320
@title=Defense Minister
The leader of the Barbarian %STRING0 has sent us a message: "We shall mercilessly sack the city of %STRING1 unless you pay us %NUMBER0 gold at once!"

"Do your worst!"
Pay %NUMBER0 gold.

%NUMBER is the about of gold demanded.

%STRING1 is the name of the city.

%STRING0 is a bit complex. It is a tribe name selected from the @BARBARIANS section of the CITY.TXT file. The choice of Barbarian tribe name appears to be random according to Kull. He wrote:

A test involving 10 different cities generated threats from 9 different tribes. The Burgundians threatened my capital, and then it was Avars, Frisians, Vandals, Huns, etc. threatening the other cities. There was no discernible pattern. First came the Burgundians (9th on the city.txt list), followed by the Avars (10th), Frisians (15th), Vandals (11th), Huns (1st), Ostrogoths (3rd), etc. The first time a city is threatened, the choice of Barbarian tribe appears to be random. However, the SAME tribe will ALWAYS threaten the same city. Thus the capital was always threatened by the Burgundians.

A clever designer can use this information to change the leader unit into any other type of units he wishes. For example, it could be changed into an aggressive, attacking stealth bomber by manipulating the statistics in the diplomat slot of the RULES.TXT. If the role assigned to the Barbarian Leader is 5, 6, or 7 the unit will behave normally; run way when alone, attempt to stack with other barbarian units, and yield gold when killed. If given a role of 0 through 4 the leader will not yield any gold.

Written by William Keenan

With technical input from John Possidente.

Special thanks to Cam Hills, Kull, and the Scenario League.