Also known as: Call of the Movable Feast Machine: Tribal Warfare.

There is already some implicit notion of tribalism in the movable feast machine. We already have blue carpet bombs, and yellow carpet bombs. Why not just have a single carpet bomb that we can decide which flag it flies on the fly?

• These are hostile tribes. The blue tribe hates the red tribe and the red tribe hates the blue tribe, etc. These tribes are not interested in working together. Only total annihilation of the other tribes and world dominance will please them.
• The goal is to have at least 4 tribes, but it should be arbitrary to add more than 4.

There are a number of things that I foresee being interesting investigating in this simulation; a couple things that come to mind are:

• What kind of non-trivial initial conditions benefit one tribe over others?
• Is there a way to keep perpetual warfare going on between two or more nations where no nation is completely wiped out? (think 1984 and Oceania).

• Some sort of Tribal_Element base class which all the other custom elements will extend.

Key: [ELEMENT] ([COST])

1. Base (5 Res): This is the fundamental element for each tribe. It should generate all troop types and even additional bases! – Since we don't want each tribe to have a single point of failure if we are in the robust mind-set.
2. Infantry (1 Res): The most basic unit. This element chooses a direction within one tile of its current position randomly. If that tile is empty it moves there, else if a hostile unit occupies this square it tries to kill it.
3. Cavalry (3 Res): Faster units than infantry and also slightly more powerful. The look range is two tiles in any random direction.

• Is a tribe slider feasible given the current architecture of the MFM?