Please consider supporting The Cutting Room Floor on Patreon. Thanks for all your support!

Fire Emblem: Monshou no Nazo

From The Cutting Room Floor
Jump to: navigation, search

Title Screen

Fire Emblem: Monshou no Nazo

Also known as: Fire Emblem: Mystery of the Emblem
Developer: Intelligent Systems
Publisher: Nintendo
Platform: SNES
Released in JP: January 21, 1994


AreasIcon.png This game has unused areas.
CharacterIcon.png This game has unused playable characters.
GraphicsIcon.png This game has unused graphics.
ItemsIcon.png This game has unused items.
Sgf2-unusedicon1.png This game has unused abilities.
TextIcon.png This game has unused text.
DebugIcon.png This game has debugging material.
PiracyIcon.png This game has anti-piracy features.


Fire Emblem: Monshou no Nazo is a part-remake, part-sequel follow-up to the original Famicom game. It's divided into two parts: the first is a slightly shortened remake of the first game, and the second tells the brand-new story of how somebody else's collapsing marriage made Marth's life absolutely miserable, and of how none of this would have happened if it weren't for several sleeping mole-dragon things.

The second part was later given a stand-alone remake as Shin Monshou no Nazo for the Nintendo DS, which ended up also being a Japan exclusive.

Subpages

Fire Emblem MnN Debug Menu 1.png
Debug Menu
Welcome to the Build-A-Battle Workshop.

Leftover Characters

A total of five chapters and six playable characters from the first game were cut from its Monshou remake, but some data remains for both the missing playable characters and the bosses and enemies of the cut chapters, mostly in the form of unit IDs and matching name strings.

  • 08: Wrys (リフ), a playable curate.
  • 0E: Darros (ダロス), a playable pirate.
  • 27: Beck (ベック), a playable ballistician.
  • 2D: Roger (ロジャー), a playable knight.
  • 2E: Jake (ジェイク), a playable ballistician.
  • 33: Gotoh (ガトー), a playable bishop. Gotoh is still a major character in both parts of Monshou, but he never appears in gameplay so this character ID is never used.
  • 35: Wylar (ワイラー), an unused boss name from the original game.
  • 3D: Bentheon (ベンソン), a cavalier boss from the original game's Chapter 4.
  • 3F: Mannu (マヌー), a manakete boss from the original game's Chapter 9.
  • 42: Heimler (ヒムラー), a paladin sub-boss from the original game's Chapter 12. Although the chapter is still in Monshou (now Chapter 10), Heimler is absent.
  • 43: Grigas (ギガッシュ), a ballistician boss from the original game's Chapter 13.
  • 47: Sternlin (スターロン), a paladin boss from the original game's Chapter 18.
  • 4A: Orridyon (オーダイン), a paladin boss from the original game's Chapter 21. Curiously he has a unique palette associated with his ID.

None of these characters (with the obvious exception of Gotoh) have portraits. All of these characters were restored to their original state in Fire Emblem: Shadow Dragon, the second remake of the original game.

(Source: Original TCRF research)

Unused Classes

Dark Knight

Fire Emblem MnN Map Dark Knight.png

The dark knight (ダークナイト; ID 21) is a variant of the cavalier class. It has a unique set of map sprites and it shares its battle sprites with the cavalier. It still wields lances, but unlike the cavalier it is unable to dismount.

Both Tear Ring Saga and Fire Emblem Awakening revisited the dark knight class idea. The Tear Ring Saga class has a very similar look and function to the Monshou class, while the Awakening one is a mounted magic/sword class.

HP Str Skl Spd WLv Def Res Mov EXP Yield
Base stats 22 9 5 6 8 9 5 9 40
Growth rates 80% 30% 20% 20% N/A 30% 0% N/A N/A

Guardian

Fire Emblem MnN Map Guardian.png Fire Emblem MnN Battle Guardian.png

The guardian (ID 25) is a variant of the general class. It has a unique set of map sprites, and shares its battle sprites with the general aside from its unique silver palette. It isn't programmed to use any weapons at all in regular gameplay, but the debug mode treats it as able to wield lances.

Unusually, the guardian has two completely different names depending on where one looks. The game has a separate list of class names used on the battle screen, which is usually used to abbreviate the longer classes to make them fit, but it spells "guardian" completely differently. Menus refer to it as "ガーディアン", a.k.a. the English word "guardian" spelled in katakana, but battle screens call it "しゅごしん", or "guardian god".

Fire Emblem Echoes: Shadows of Valentia later introduced a similar guardian class, which is also a lance-wielding variant of a pre-existing armored class, except that the Shadows of Valentia guardian is a monster class with a slightly different Japanese name.

HP Str Skl Spd WLv Def Res Mov EXP Yield
Base stats 32 10 0 0 16 14 20 5 0
Growth rates 90% 30% 30% 20% N/A 20% 0% N/A N/A

Ocean Dragon

Fire Emblem MnN Map Ocean Dragon.png

The ocean dragon (かいりゅう; ID 27) is a water-based dragon species, a concept which had originally been planned for Ankoku Ryu to Hikari no Tsurugi. It is able to move freely on water in the same way as the pirate class. It has a set of unique sprites for moving and attacking on the map, including a very distinctive dodging animation where it ducks underwater; although its stationary map animation no longer seems to exist, one frame of it still appears in unit list menus. In battle scenes, it just reuses the fire dragon's sprites.

It doesn't have a matching breath weapon of its own, but has no problems using the other four breaths if they are hacked into its inventory. Like the other dragon classes, when battle scenes are in map animation mode, it always uses a specific set of breath attack frames exclusive to itself that depict a waterspout, regardless of what breath weapon it is actually using. Appropriately, the Ankoku Ryuu concept also describes ocean dragons as attacking with waterspouts.

The debug menu indicates that a matching dragonstone item was also intended for it at one point, but its slot was eventually repurposed into the Part 2 version of the Aum staff.

Shadows of Valentia later introduced the dagons, a similar class of water-based dragons which also happen to reuse some assets from that game's fire dragons.

HP Str Skl Spd WLv Def Res Mov EXP Yield
Base stats 26 6 0 0 16 15 20 6 50
Growth rates 50% 10% 10% 10% N/A 10% 10% N/A N/A
(Source: Original TCRF research)

Unused Items

ID Icon Weapon Name Translation Durability Worth Help Text Notes
54 Fire Emblem MnN Item Shadow Dragonstone.png あんこく竜石 Shadow Dragonstone 18 N/A マムクートがつかうと
あんこくりゅうに
へんしんする
When used by a manakete,
they transform into a
shadow dragon.
In the finished game, the only shadow dragon is Medeus in Part 2, who doesn't start as a manakete. Works like the used dragonstones, except it doesn't provide a breath attack.
59 Fire Emblem MnN Item Silver Key.png ぎんのかぎ Silver Key 1 5000 ぎんのとびらをあげる Unlocks silver doors. Hints at silver doors as a cut mechanic. Presumably, regular keys would not have worked on these doors.
7A Fire Emblem MnN Item Aum Shard.png オームのかけら Aum Shard N/A N/A せんじょうより りだつ
する
これをもっていると
1どだけ しなない
戦場より 離脱する
Retreats from the
battlefield. When held,
it prevents you from dying
just once, and you retreat
from the battlefield.
Despite its very detailed description, it unfortunately has no remaining functionality whatsoever.
(Source: Original TCRF research)

Unused Palettes

Unused Text

Enemy Midia

Elementary, my dear Cactus.
This needs some investigation.
Discuss ideas and findings on the talk page.
Specifically: Where is it located in the ROM? Original Japanese text?
Heartless fiends who point their arrows at our holy kingdom,
if you wish to step foot inside Archanea Palace,
then you'll have to kill me first!

There is what appears to be a battle quote meant for Midia in Part 2. It is possible that she was initially intended to remain loyal to Hardin despite his corruption, but in the finished game, she is captured by Hardin for trying to lead a rebellion.


(Source: Serenes Forest)

Test Map

Fire Emblem MnN Test Map.png

Map ID 00 contains a leftover test map titled "第99章 デバッグがんばれ!のまき" (Ch.99 Good luck debugging! Nomaki). The map itself is a near-exact duplicate of the Part 2 Final-1 map. According to the status screen, the chapter's objective is to "Find all of the bugs" (バグをかんぜんにとる).

Set the byte at 7E07DF to 00 to access this map. Note that any attempt to save the game in battle preparations will fail and just delete the save file entirely.

The player is allowed to deploy a maximum of 7 units, including Marth. Unlike the actual chapter, the player's army starts right in the middle of the map (pictured). There are 13 enemy units, all of whom are named "Galder Soldier" and all of whom have Marth's Part 1 portrait. None of them have particularly remarkable stats or items, aside from a female mage who has a Nosferatu tome.

The map has a handful of noticeable differences from the actual Part 2 Final-1:

  • The chapter's seize point is missing, so there's no way to end it through normal play.
  • The map plays the Part 1 map and battle themes, instead of the tracks used by the actual chapter.
  • The village and shops along the top are all missing. Instead, a random assortment of village fence tiles is sitting in their place.
  • A few of these fence tiles are also strewn around the bottom-left, where the player starts in the actual chapter.
  • Unsurprisingly, the map has no cutscenes or events at all. This also means that the cursor is not placed on Marth at the map's beginning, and instead sits in the top-right corner of the map.
  • If loaded from the chapter select screen, the game zooms in along the top of the world map, opens a text box to begin the customary opening narration, then crashes.
(Source: Original TCRF research)

Anti-Piracy

Fire Emblem MnN Antipiracy.png

Like many post-1993 first-party SNES games, Monshou no Nazo tries to protect itself against being run on cartridge copiers by checking RAM at startup. The game calls a subroutine at $93EA4E that compares the memory range $700000-$702000 with the range $702000-$704000. If the cartridge has the correct amount of RAM, the ranges will be identical due to address mirroring and the game will pass the check subroutine, but an incorrect amount of RAM (as copiers commonly have by their very nature) will result in mismatched ranges that fail this check, prompting the game to throw up a stern warning message (featuring a fun typo) and freeze.


(Source: Zane Avernathy)