Fire Emblem Wiki


5,860pages on
this wiki
Add New Page
Talk0 Share

“You're about to die. Scream if you must.”

Damian is an enemy character in Fire Emblem: The Blazing Blade and a member of The Black Fang sent to kill Eliwood and his group in Badon. He is the actual boss of Chapter 16x: The Port of Badon (Chapter 17x in Hector Mode). To unlock this chapter, you must make sure that at least one Caelin soldier survives in Chapter 16.

Damian does not appear on the map at the beginning of the battle. It is possible to complete the entire chapter without even engaging Damian in combat. It is not seen what happens when he is spared.

In the battle, the player is challenged by the group of pirates to get past them and talk to the captain in order to obtain free passage to Valor, The Dread Isle. The battle can easily be won if the player simply stays out of the largest enemy group of pirates' range by going across the top of the map. If the player crosses the top of the map they will face only a few pirates and the main group will leave them alone.

If the player leaves a unit within attacking range of the main group of pirates, Captain Fargus will make a comment, and then order his units to attack. In the following turn, Damian will appear at the bottom of the map. He will have a small dialogue then attack any player unit within his range. Afterward, Damian attacks the rest of his small force, and the pirates will converge on the player units.

Damian doesn't have too much dialogue and usually charges into battle rather quickly. Damian is of a relatively high level, he is a promoted unit, a Paladin, at level 5. This means most player units will not be able to easily defeat him at this point in the game.

Damian is shown to be a very arrogant man from the little dialogue he has, or at least very confident. He is also a pallette swap of the boss of Chapter 11 (Hector Mode), Wire.


Normal Modes and Eliwood Hard ModeEdit

Starting Class Affinity
Paladin N/A
Level HP Str Skl Spd Lck Def Res Con Mov
5 34 12 7 5 2 14 13 11 8
Weapon Starting Items

Sword Sword - A
Lance Lance - D
Axe Axe - E

KillingedgeKilling Edge*
SteelLanceSteel Lance**
SteelswordSteel Sword**

*In Eliwood's Story
**In Hector's Story

Hard ModeEdit

Starting Class Affinity
Paladin N/A
Level HP Str Skl Spd Lck Def Res Con Mov
5 38 14 9 6 2 14 14 11 8
Weapon Starting Items

Sword Sword - A
Lance Lance - D
Axe Axe - E

SteelLanceSteel Lance
SteelswordSteel Sword

Overview Edit

in Eliwood's story, Damian will spawn the moment the player steps within attacking distance of the wall of pirates at the west end of Badon. With a Killing Edge in hand, he stands a very good chance of dealing the first enemy critical blow onto the player. It is important to remember that, though Damian spawns the moment the wall of pirates becomes active, will only attack when a unit wanders into his attacking range. Players should defeat the wave of pirates before engaging Damian, then bait him out using a character that can withstand one of his criticals. High defense is of key importance here: critical hits do triple damage, so each defense point will be triply effective at weakening his critical hit. As such, Oswin might be a good choice.

In Hector's story, Damian has mercifully abandoned his Killing Edge. In return, however, he attacks proactively, and packs a Steel Sword and Steel Lance to boot. Oswin and Hector, armed with a Horseslayer or Wolf Beil, are effective at defeating him. Using the chokepoints present in the city can help keep the fight a manageable affair.

Death QuoteEdit

“Gaa... ha... Crow in... triumph... you've--”
—Death Quote

Trivia Edit

  • Despite being a Paladin, Damian's stats seem more fitting for a Knight or General. In particular, even in Hector's Hard Mode, Damian's speed stat is actually lower than that of a baseline generic Paladin.

Ad blocker interference detected!

Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.