Siege: Difference between revisions

From Cunnan
Jump to navigationJump to search
No edit summary
 
(completely rewrote article)
Line 1: Line 1:
A '''siege''' is an armed attempt to capture a defended fortified position from an enemy, either through direct assault or by [[starve|starving out]] the defenders. Which tactic was used depended on the strength of the defenses and the strength of the attacking force. If the attackers were of sufficient strength to completely cut off all resupply, the defenders would be dependant on stored provisions; in theory, if adequately supplied the defenders of a well-made castle could hold off the attackers indefinitely.
==How to Siege a Castle for Fun and Profit==
The first step is to raise an army. Rome wasn't built in a day, you know, and neither is an army. To get all the men together (you need 16,000 at least, though you'll wish you had a million), supplies, training, equipment, will take at least the winter and at most 2 years (unless your army is especially daft).


If there was no hope of starving out the defenders, then the attackers must either give up the attempt or try to breach the defenses. Assuming the siege would continue [[engineer]]s would construct [[siege engine]]s such as the[[trebuchet]]s and the [[cat]]. [[Trenches]] could be dug or, if a [[moat]] was to be crossed, a [[mole]] contructed. [[sapper|Sapping]] and tunneling under the walls was also pursued, if practical. One particularly nasty sapper's trick was to undermine a section of [[wall]] with a large gallery supported by [[wood]]en posts, stuff it full of flammable material, and set it on [[fire]]. When the gallery collapsed, the section of wall would crumble, allowing the breach to be stormed.
==Before you begin, ask yourself the following questions:==
1. What is the terrain? Is the castle on a large field? Then you probably want a large army with some decent cavalry to mop up any escapees. Is the castle bordered by the sea? Use some ships to back up your land army. Is it in the mountains? Close off the roads and use infantry almost exclusively. Is it on an island? Naval blockade. Pick the right force for the right job.


Sieges were a standard of medieval warfare, owing to the widespread use of fortifications. In the ordinary run of medieval warfare the tradition of forty days' military service meant that most fortifications were not starved into submission, but rather stormed by force. In conflicts with non-Europeans, however, or during periods of great strife (such as the [[Hundred Year's War]] or the [[Crusades]], prolonged sieges (some lasting years) did occur.
2. Why are you attacking the castle? Do you want it for yourself? You should probably surround it and starve out the current residents. Pack plenty of food, because you can be certain that they will. Is it in the way? Use siege engines to knock it down. Do you want to make an example? Find a way in and slaughter everyone. If you don't know why you are attacking, go home.


==Sieges in the SCA==
3. Consider your enemy. Does he have allies? Is his army fielded? Does he possess a superior number? Better technology? Is he more handsome? Take all of these factors into account before you start.
For practical reasons, long-term sieges are not recreated in the [[SCA]], with one exception: the [[castle battle]], a type of battle which recreates storming a fortification.


[[category:combat]]
4. What are the consequences? Who would retaliate? Would your major religious leader or secular ruler be upset? What happens if you lose?

==Moving Out==
If you have decided, after asking yourself these questions, that you wish to go through with this, congratulations! You are on your way to making war. Organize your men, discuss your plan with your subordinates. Before you go, check your "Handy Checklist of Sieging":

[]Troops

[]Arms

[]Food for at least a year

[]Personal Equiment and Effects

[]Did you use the bathroom?

[]Is your fireplace still on?

[]Small siege engines (ballistae, small rams)

If all of these are checked, go ahead.

==Starting Your Siege==
Okay, you've bottled your enemy inside his castle. Ask for his surrender. Either he'll give in, or tell you to go to Hell.

''finishing later-WanderingSpy''

Revision as of 04:59, 3 May 2006

A siege is an armed attempt to capture a defended fortified position from an enemy, either through direct assault or by starving out the defenders. Which tactic was used depended on the strength of the defenses and the strength of the attacking force. If the attackers were of sufficient strength to completely cut off all resupply, the defenders would be dependant on stored provisions; in theory, if adequately supplied the defenders of a well-made castle could hold off the attackers indefinitely.

If there was no hope of starving out the defenders, then the attackers must either give up the attempt or try to breach the defenses. Assuming the siege would continue engineers would construct siege engines such as thetrebuchets and the cat. Trenches could be dug or, if a moat was to be crossed, a mole contructed. Sapping and tunneling under the walls was also pursued, if practical. One particularly nasty sapper's trick was to undermine a section of wall with a large gallery supported by wooden posts, stuff it full of flammable material, and set it on fire. When the gallery collapsed, the section of wall would crumble, allowing the breach to be stormed.

Sieges were a standard of medieval warfare, owing to the widespread use of fortifications. In the ordinary run of medieval warfare the tradition of forty days' military service meant that most fortifications were not starved into submission, but rather stormed by force. In conflicts with non-Europeans, however, or during periods of great strife (such as the Hundred Year's War or the Crusades, prolonged sieges (some lasting years) did occur.

Sieges in the SCA

For practical reasons, long-term sieges are not recreated in the SCA, with one exception: the castle battle, a type of battle which recreates storming a fortification.