From StrategyWiki, the video game walkthrough and strategy guide wiki
< Dominions 3: The Awakening
Revision as of 16:42, 22 September 2010 by Jack67 (talk | contribs) (→‎Army setup)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Dominions is primarily a strategic game, not a tactical game. Furthermore, it is designed with an eye towards supporting a variety of multiplayer methods, including play-by-email (PBEM); and a large number of players, of which only two will be in any one battle. Therefore, the players' control of tactical battles is limited to preparation; it is up to the tactical AI to determine what individual units will do, and when.

As such, your direct control stops when the battle starts. A recording of the battle will be sent to anybody with a presence in the contested platform -- including stealthy sides not involved in the battle. In addition, battles that are initiated via remote summons are shown to the caster, regardless of whether the summons are associated with the caster or merely 'unflagged' monsters.

There is no hidden information in a battle recording. That is, all viewers get perfect information regarding unit ownership, items, spells cast, and so forth. You do not, however, get to see the actual scripts or squad assignments -- just their effects.

All battles are single-attacker versus single-defender, although either or both sides may summon monsters. Most summoned monsters are loyal to their summoner, although some will attempt to slaughter everyone on the battlefield. Battle summons are ephemeral, and will disappear after the battle.

Army setup[edit]

Army setup is quite important. For instance, it would normally make little sense to have your frail magicians in the front and your slow-moving heavy infantry in the rear. You want your vulnerable-but-important units to be fairly safe, while you want others ready to enter the fray. If you have units which are always surrounded by flames, cold, or poison, you might want to keep them separated from units which are not immune. And so forth.

Troops may be organized into squads, each of which can be placed somewhere within the army organization, and then given some basic order such as 'Hold and Attack'.

Each commander can command a maximum of 5 different squads of units.

Scripting a small squad of units (2-5) to guard a mage keeps them within a square or two of the mage, providing a meat shield that can greatly increase survivability against breakaway enemies because enemies tend to attack whomever is closest instead of picking out spellcasters specifically. This is also worth doing if a warrior commander is going to charge into melee; it prevents him from getting totally surrounded. Since mages cost 200+ gold apiece it's worth a little investment in a couple of light infantry to keep him alive. Think of it as a virtual hit point boost.

Scripting mages & commanders[edit]

As with squads, you can give your commanders a particular place to stand when planning the disposition of your army.

Commanders can command up to five squads, subject to their maximum leadership values. In addition, each may have up to five specific orders (such as "Cast Nether Darts" or "Hold"), followed by a general order (such as "Cast Spells" or "Attack").

Killer combos[edit]

If you want your magicians to use specific combinations, you should script them to ensure their use.