Final Fantasy Wiki

Mushussu (Type-0)

21,182 pages on
this wiki
Add New Page
Talk0 Share


FF4PSP Cid PortraitCid: Oh, shut up and help me remodel the Mushussu (Type-0) page!
Please expand this article into a full one. More details can be found, and this request can be discussed, on the associated discussion page.

Mushussu is an enemy in Final Fantasy Type-0 that resides in Mount Jubanla.

Enemy CompendiumEdit

Aside from its unique facial markings, the mushussu is nearly identical to the marduk in both physicality and ability. However, while marduks tend to like in schools in the jungle, a mushussu will often maintain a completely solitary existence for its entire lifespan.


Mushussus start the battle asleep and awake when attacked. They blow bubbles of hot steam that slowly advance on the player. After being awoken when in low health they become enraged and start rampaging around the area while continuously blowing bubbles. There is a Breaksight strike chance after their steam attack. When enraged, scoring a Breaksight strike stuns them momentarily.


In the Tower of Agito, it is ideal to position on the middle spawn so that all three spawns can be hit by Fire BOM-II. A damage and channel enhance-maxed Fire BOM-II (also ideally with Mutsuki's BOM magic +10 request complete) that is spammed will kill the Mushussus within two seconds of them spawning. Channelling to Firaga BOM-II is unnecessary and much less effective. Having three to four Fire BOM-II up will ensure they die the moment they spawn.



The mušḫuššu is a creature depicted on the reconstructed Ishtar Gate of the city of Babylon, dating to the 6th century B.C. As depicted, it is a mythological hybrid, a scaly dragon with hind legs like an eagle's talons, feline forelegs, a long neck and tail, a horned head, a snakelike tongue, and a crest.

Related enemiesEdit

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.