- v50 information can now be added to pages in the main namespace. v0.47 information can still be found in the DF2014 namespace. See here for more details on the new versioning policy.
- Use this page to report any issues related to the migration.
Difference between revisions of "v0.31:Siege engine"
(→Using Siege Engines (simple): should be able to use a burrow too..) |
|||
Line 22: | Line 22: | ||
*Fire at Will: Siege Operators will fire and load normally. | *Fire at Will: Siege Operators will fire and load normally. | ||
− | Once an engine is given orders to fire (or prepare to), a dwarf with the {{L|Siege operator|siege operating}} labor designated will respond and report to the engine. The dwarf(s) will (re-)load any siege engine that is not currently loaded; there's no way to prevent this short of disabling the labor on all dwarves or forbidding every piece of ammo (or otherwise blocking a {{L|path}} to it, perhaps by locking {{L|door}}s.) | + | Once an engine is given orders to fire (or prepare to), a dwarf with the {{L|Siege operator|siege operating}} labor designated will respond and report to the engine. The dwarf(s) will (re-)load any siege engine that is not currently loaded; there's no way to prevent this short of disabling the labor on all dwarves or forbidding every piece of ammo (or otherwise blocking a {{L|path}} to it, perhaps by locking {{L|door}}s or using a {{L|burrow}}.) |
{{L|Ammo}} is destroyed upon landing, unless it falls a z-level, and then it falls harmlessly. (See [[#Catapults as stone movers|below]].) | {{L|Ammo}} is destroyed upon landing, unless it falls a z-level, and then it falls harmlessly. (See [[#Catapults as stone movers|below]].) |
Revision as of 17:03, 24 July 2011
This article is about an older version of DF. |
A siege engine in Dwarf Fortress is half building/half heavy weapon, and includes both the catapult and the ballista. Both are capable of launching hazardous projectiles at a tremendous range (more than a screen-width, around 80 to 100 tiles for a catapult and between 130 and 200 tiles for a ballista). A Template:L can kill or injure each creature in its path indiscriminate of friend or foe, but a stone launched from a catapult cannot harm dwarves or tamed animals.
Siege engines can be made to face any cardinal direction, but they cannot be moved after placement. They can, however, be deconstructed back into their 3 parts, to be moved elsewhere (individually or together). Both the construction of siege equipment and the engine itself require a dwarf with the "Siege Engineering" Template:L designated, which uses the "Template:L" Template:L.
The player determines when/if each engine is actively firing or not; when active, a single engine is crewed by a single Template:L. Ballistae require specially made Template:L, Template:Ls, made from wooden Template:Ls at the siege workshop (and optionally tipped with Template:L Template:Ls that have been made at a Template:L by a Template:L). Catapults use simple Template:L as ammunition.
Building Siege Engines
In order to build a siege engine, you first need to produce (at least) three catapult or ballista parts in the Template:L; catapults are made from any 3 catapult parts, and ballistae are made from any 3 ballista parts. All parts are made from any type of wood at the siege workshop. Beyond that, "parts" are generic - there are no particular "sub-types" of parts beyond the distinction between those for the two different engine types. The quality of the parts determines the overall rate of fire and accuracy of the engine - the best are made with 3 masterwork parts. This won't make up for an untrained siege operator, but every little bit helps.
Once you have the parts, you may then build the respective siege engine like any other building, selecting the parts that you wish to construct that particular engine with. It is not known whether the skill of the dwarf assembling the siege engine has any effect, but the quality of the parts certainly has: siege engines put together from Template:L parts have a much higher rate of fire and accuracy.
The assembled siege engine is, effectively, a 3x3 building. It cannot be moved about other than by taking it down and re-assembling it at the new site. Siege engines do not impede movement, though, so you don't have to worry about building them in a corridor.
Using Siege Engines (simple)
o will let you change the orientation, whether the siege engine is pointing north / south / east / west. This takes effect immediately, it does not require a dwarf to come and turn the engine.
f toggles the current status between:
- Not In Use: Dwarves with the Template:L Template:L will reload unloaded engines and leave them unattended.
- Prepare to Fire: Siege Operators will load the engine and remain stationed for further commands.
- Fire at Will: Siege Operators will fire and load normally.
Once an engine is given orders to fire (or prepare to), a dwarf with the Template:L labor designated will respond and report to the engine. The dwarf(s) will (re-)load any siege engine that is not currently loaded; there's no way to prevent this short of disabling the labor on all dwarves or forbidding every piece of ammo (or otherwise blocking a Template:L to it, perhaps by locking Template:Ls or using a Template:L.)
Template:L is destroyed upon landing, unless it falls a z-level, and then it falls harmlessly. (See below.)
######## CCC..._# CCC..._# CCC..._# ########
The Template:L at the end of this firing range preserves the stone. For catapults there is usually so much spare stone that this is not necessary, but it could be used for fast stone transport, or simply to set up a self-contained training area. A similar effect can sometimes be observed when firing a catapult over bumpy ground outside.
The design can be further improved by using a Template:L rather than a wall, this way when the drawbridge is raised it acts like a wall deflecting the stone into the channel below. In the case of an attack on your Template:L the drawbridge can be lowered allowing the catapult to fire.
##################### CCC..._¦............. CCC..._¦............. CCC..._¦............. #####################
Drawbridge raised deflecting stones into channel.
##################### CCC...[]............. CCC...[]............. CCC...[]............. #####################
Drawbridge lowered allowing catapult to shoot down the corridor.
Special considerations
- Both catapults and ballistae have narrow fields of fire - they will only shoot at creatures basically "in front" of them, and so cannot target anything off at an angle. They can be turned 90 degrees, but that often will not solve the problem. (The field of fire is perhaps only 10-20 degrees wide. Wild shots may go (well) beyond this, but those are not aimed.)
- Both catapults and ballistae aim and fire only along one z-level. While ammo from both may drop down z-levels, they do no damage to creatures there. This also means that no "head room" is necessary - ammo just flies out, never up.
- Catapults have a minimum range - at least 30 tiles.
- Catapults can and will fire over any creatures between them and their target.
- Neither are affected by Template:Ls.
- Template:Ls are "civilians", and as such they will run in fear if enemy units come too close to them. "Too close" varies somewhat, but may be as far as 10 tiles.
Safety Warning
Ballistae can and will kill anything in their path! Ballista arrows appear to hit any units in any square that the head passes through. They are devastatingly dangerous weapons, and should never be used with friendlies anywhere in their cone of fire, including the space the ballista arrowhead occupies when loaded on the engine. Always designate a Template:L for a lot of tiles along the firing arc and keep dwarves out of the area or, better, wall off anything in front of them with fortifications to prevent all friendly traffic, or both. The shots appear to travel until they hit a wall or fly off the screen; the maximum range is about 150 tiles for an ordinary ballista. If the bolt passes through a Template:L, the tree will disappear, presumably reduced to toothpicks.
Surprisingly, catapults are relatively safe. Catapult operators will target enemies (and wild animals) if there are any in their field of fire. If not, they will loose the shot in a high arc (not requiring additional z-levels, though) that misses everything until it lands. It is perfectly safe to operate a catapult in the cave: just point it at a nearby wall of solid rock. A nice side effect is that this will, in due time, clear the whole area of stone.
Using catapults to shoot into the open may provide some meat: as said above, the operators will target animals if there are any. However, Template:Ls don't take nicely if you slay some of them. You also have a slight risk of killing your own dwarves or Template:L escorts if they happen to be hunting the selfsame animal (and hence are close to it).
"Fire at Will" does not mean there has to be anything to shoot at! The siege engine will simply continue to be loaded and fired, simply launching ammo (stone or arrows) downrange with no (visible) target if given this command. This can be good against unseen Template:Les, or if you wish to move Template:L across a map, but not if you are worried about depleting an ammo stockpile.
Using Siege Engines (advanced)
Placement
Siege engines can almost only shoot at targets right in front of them on the same Z-level. The target may deviate only slightly, as the field of fire is about 20-30 degrees wide. Because of the huge blind spots, it is advisable to Template:L so that the enemy will be channeled through the field of fire.
Siege operators are civilians! They will drop their work and run if the enemy comes too close, which is around 20 tiles. You should therefore place the engines behind a Template:L or a wall of Template:Ls that will keep the enemy at a safe distance, or shield access to their location in some other fashion.
Siege engines can shoot through Template:Ls, just like any other projectile weapon. As fortifications appear to provide some protection against incoming Template:Ls and Template:Ls, it's usually a good idea to protect the siege engine in that way. The siege engine only needs a one tile wide fortification to shoot out.
Skill and Quality
The quality of the siege engine parts affects the engine's accuracy and reload time. It is not known whether the siege engine itself also can be of a certain quality. The quality and material of the ammunition (in case of ballista arrows) affects the damage and possibly accuracy as well.
The only way of obtaining high-quality siege engine parts is to have them made by a trained engineer; the only way to train an engineer is to make parts or ammunition. Assembling and disassembling siege engines does not train the Template:L skill. Dwarves will occasionally produce masterpieces long before reaching Template:L skill level, but be prepared to waste hundreds of logs until you have three masterpiece parts. Bringing an engineer to Template:L level (the highest you could buy when starting a new fortress) will take about 120 logs. Becoming Legendary requires the wood of 600 trees.
The operator skill certainly affects reload time. It will take a whole month for an unskilled dwarf to load a catapult; a Legendary operator with nearby ammo will get several shots at a running enemy. Operator skill has little or no effect on accuracy.
Operators are best trained on catapults, as these require nothing but cheap stone for ammo. It is recommended to have a number of dedicated operators that will follow no other line of work, and enough catapults for all of them to play with. As they're often going for a drink or sleep, you may get along with three catapults for four operators, and even two pieces would go a long way. Since the dwarf must hold the heavy stone in his inventory during the entire loading procedure, dwarves that have increased their strength statistic load catapults much more rapidly than others, making them good candidates for operator duty. You should start training early: it can take one year for an operator to become Proficient, and two more years until he finally reaches Legendary level; by then he will have spent 300 rounds.
Loading ballista arrows seems to be much faster than loading catapults, probably due to the much lighter weight of the projectile.
An alternative approach is cross-training any highly-skilled dwarves who aren't doing anything useful at the moment. With a couple levels each in strength and agility, a decent-quality catapult, and an ample supply of ammunition nearby, a dwarf can become a Legendary siege operator within a few seasons at most, giving more flexibility in defense and several more levels for the fortunate dwarf. Template:L Legendary Template:Ls out to siege-operation and then to stone-hauling duties sets up an efficient cycle.
In Battle
Catapults are generally less effective in battle situations than are ballistae (as of version 0.31.08). The launched rocks will often glance off mail armor, making them poorly suited for killing even Template:Ls. It is still faster to fire stones than carry them, at least. Catapults are very inaccurate, but they are less likely to harm friendly creatures, and their ammo is easily replenished, making them ideal for target practice.
Ballista arrows tipped with softer materials (such as wood) can glance off ordinary clothes, making the choice of arrowhead significant. However, the arrows penetrate through any unit they strike, allowing them to hit many multiple targets in a single launch. This makes ballistae many times more efficient than catapults, which fire in an arc that hits only a few tiles per shot and is nearly useless against anything larger than smaller, poorly-armored foes. Ballista arrows fired through too many successive targets will be lost or destroyed; the limit seems to be roughly 5-6 goblin-sized targets hit before the arrow is lost.
A siege engine you want to use for actual defense should be not set to fire at will, as this likely means that it's not loaded and ready at the time you actually need it. You should train your operators on other pieces.
When the time comes, switch off all training engines and set all of the ones you'll be using to prepare to fire so the operators will be on-station; if some of them are currently not loaded, designate them to be disassembled so to prevent your operators from loading the training weapons instead of firing the real ones.
Remember, operators are civilians. They do not care that the fortress is at stake: hunger, thirst, sleep and breaks will always come first. It's wise to train more operators than you have engines, and disable all other work for them in times of need. The most effective way to ensure that your operators won't run off is to lock them in with the siege engine during the moment of truth.
Ballista battery
If you place ballistae close enough together, you can completely cover a two or three tile wide corridor. Because siege engines are 3x3, they need to be staggered, so each one fires through the edge of the one ahead of it. This can be dangerous for your operators. To minimize risk, place Template:Ls to keep dwarves from wandering too far, and have only one entrance to the ballista room. There is still some risk that dwarves might wander into the line of fire, even with no reason to do so.
Three tile-wide corridor (battery room 5 tiles wide)
╔═══ ══════════════════════════╦══╦══╝▐▀\ Entrance++++++++++++▼·····╬++╬▐▀\◄═« (~ammo~) Entrance++++++++++++▼·····╬▐▀\◄═«▐▄/ Entrance++++++++++++▼·····╬◄═«▐▄/+(~ammo~) ══════════════════════════╣▐▄/+(~ammo~) ╚═════════
- + - floor
- ═ - wall
- ▼ - ramp (down)
- · - channel (aka "empty space" on this level)
- ╬ - fortification
Due to the rare wild shot, the staggering should always be from one side to the other, and not put one ballista far ahead of the one it overlaps, as this may increase friendly-fire accidents.
Ammo storage can be on the same level, or via Template:Ls or Template:Ls on another Template:L. Expand the room as desired for more storage. Also note that ballista arrows are stored in Template:L, not ammo stockpiles.
An alternate strategy could be to place a Template:L or retracting Template:L in the center of the 3x3 hallway, and activate it during times of crisis so that the Goblins are forced to fight in two separate 1x1 corridors rather than a single 3x3 corridor. If the corridors are further lined with spike traps and weapon traps, this combined defense can assure your dwarfs that any attempts to assault your base will be very, very bloody.
A drawbridge can be combined with the channeled area to provide a practice area, as discussed above. The channels would be accessible from the battery area via a staircase, keeping the dwarfs below/behind the lines of fire at all times.
Catapults as stone movers
When a catapult throws a stone, that stone is destroyed upon landing, unless it falls a z-level, where it lands harmlessly. That means that if you can arrange it so ammo hits a wall (or door, or raised bridge), and there is empty space immediately under that, the stones arrive at that point. If ammo reaches its maximum range, again, it falls harmlessly. Even with a single, no-quality catapult and an untrained crew, this is massively faster than hauling stone by hand. Ammo that hits Template:Ls is destroyed, even if it can fall a z-level.
Gatling Catapults
This involves a catapult, a garbage stockpile, and a legendary siege opereator. Setup your catapult, as you wish to use. Train at least one operator to about Legendary. Mark a garbage stockpile in the middle of the catapult. Dump enought ammo for train / usage. Reclaim the ammo(d-b-c), and off you go. With a good quality catapult you can easily manage 2-3 stones flying at once per catapult.
See Also:
Rooms |
Barracks • Bedroom • Dining room • Dormitory • Jail • Meeting hall • Hospital • Office • Sculpture garden • Tomb • Zoo |
---|---|
Furniture |
Animal trap • Anvil • Armor stand • Bed • Bin • Box • Bucket • Cabinet • Cage • Coffin • Restraint • Seat • Statue • Table • Weapon rack |
Access | |
Constructions | |
Machine & Trap parts |
Axle • Gear assembly • Millstone • Screw pump • Water wheel • Windmill • Lever • Pressure plate • Trap • Support |
Other Buildings | |
Related Articles |