Skip to main content Accessibility help
×
Hostname: page-component-84b7d79bbc-7nlkj Total loading time: 0 Render date: 2024-07-29T17:19:13.270Z Has data issue: false hasContentIssue false

5 - Siege warfare in the Crusader lands

Published online by Cambridge University Press:  05 August 2012

Hugh Kennedy
Affiliation:
University of St Andrews, Scotland
Get access

Summary

Most Crusader castles were designed to resist armed attack by large forces for a considerable length of time. The builders who constructed them were keenly aware of the weapons available to the assailants and tried to devise ways of countering them. The development of castle architecture must be seen as the result of a continuing dialectic between attack and defence which gave the advantage sometimes to one, sometimes to the other. Only by examining techniques of attack can we come to a real understanding of the architecture of defence.

The most basic way of taking a castle was by blockade and starvation of the defenders; simply by surrounding the place and preventing anyone getting in and out famine would complete the task at minimum risk to the attacking army. In practice, forcing surrender in this way was usually impractical and it could only be achieved in special circumstances. The problems for the attacking army were numerous. To begin with, it was not only the defenders who had to eat; the besieging army had to be supplied and this often caused major problems. When the Crusaders blockaded Muslim-held Antioch through the grim winter of 1097–8, their forces suffered terribly from hunger and they were forced to send off foraging parties further and further into the already ravaged countryside; even so, famine among them almost caused the collapse of the whole project. The defenders, by contrast, seem to have been comparatively well provided for and it was treachery, not starvation, which finally led to the fall of the city.

Type
Chapter
Information
Crusader Castles , pp. 98 - 119
Publisher: Cambridge University Press
Print publication year: 1994

Access options

Get access to the full version of this content by using one of the access options below. (Log in options will check for institutional or personal access. Content may require purchase if you do not have access.)

Save book to Kindle

To save this book to your Kindle, first ensure coreplatform@cambridge.org is added to your Approved Personal Document E-mail List under your Personal Document Settings on the Manage Your Content and Devices page of your Amazon account. Then enter the ‘name’ part of your Kindle email address below. Find out more about saving to your Kindle.

Note you can select to save to either the @free.kindle.com or @kindle.com variations. ‘@free.kindle.com’ emails are free but can only be saved to your device when it is connected to wi-fi. ‘@kindle.com’ emails can be delivered even when you are not connected to wi-fi, but note that service fees apply.

Find out more about the Kindle Personal Document Service.

Available formats
×

Save book to Dropbox

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Dropbox.

Available formats
×

Save book to Google Drive

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Google Drive.

Available formats
×