FANDOM


BeastMan.EXE
B
Designer:
Operator:Takeo Inukai
Wizard:{{{wizard}}}
NetNavi:{{{netnavi}}}
Compatible human:{{{human}}}
Compatible AM/FM-ian:{{{FM}}}
Compatible UMA:{{{UMA}}}
Compatible Wizard:{{{Wizard}}}
EM-Wave Change:Template:Emwavechange
HP:500, 700 (α), 900 (β)
Movement:
Attacks:Beast Ray, Jumping Claw, Wild Rush
Battle Chips:{{{chip}}}
Leaves:{{{item}}}
Element:{{{type}}}
Weakness:None
Main site:
Original
counterpart:
Appearances
in games:
MegaMan Battle Network 3
Other appearances: MegaMan NT Warrior
Voice actor:{{{voiceactor}}}
Seiyū:{{{seiyu}}}
Sprite:

BeastMan.EXE, known as SavageMan.EXE in the English anime dub, is a NetNavi boss in MegaMan Battle Network 3. He first appears as the boss of the second scenario, where he used the chips planted in the animals at the zoo to take control over them. To get to him, the player must pair up animal programs (all are Mr. Prog) puzzles to deleted viruses blocking the way. He later appears again in Undernet 3 in the same place the player fought FlameMan before as one of the ranked Navis from Undernet.

AbilitiesEdit

  • Beast Ray: BeastMan rushes at the player in a diagonal direction.
  • Jumping Claw: BeastMan leaps into the air, and descends on the player, attacking in a Widesword-esque fashion.
  • Wild Rush: BeastMan disappears. Then, his claws will attack the player in diagonal directions, followed by his head charging at the player.

TriviaEdit

He resembles Slash Man from the original series, possibly even more then his true NetNavi counterpart, SlashMan.EXE. Because of this and the fact that BeastMan.EXE debuted before SlashMan.EXE, it was believed that BeastMan was the Battle Network counterpart of the original Slash Man. It may be that BeastMan.EXE is based upon Slash Beast from Mega Man X4, who in turn resembles Slash Man from the Classic series.


From MMKB, a Wikia wiki.

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.