FANDOM


Fred
BM Boss4
Battle with Fred

Location

Area 4

Reward

Key

Pause Trick

Yes

Fred was Jason's pet frog from the first Blaster Master. At first an ordinary frog, Fred grew to enormous proportions upon coming into contact with radioactive material and then led Jason on a merry chase throughout the underworld. Jason was forced to kill his pet frog not once, but twice, during his journey. Despite Fred's "deaths," he escapes the underworld unscathed along with Jason.

It is interesting to note that even though Fred is one of the catalysts for the events of the series, he is not seen or mentioned in any other adventure.

In BattleEdit

StrategyEdit

Fred has a few different attacks, and he follows a pattern:

  1. Three hops
  2. Lashes out his tongue
  3. Two hops
  4. Spits out three pairs of small fireballs
  5. Three hops
  6. Spits out one large fireball, in the direction of Jason
  7. Reapeats cycle


He's only vulnerable point is when his mouth is open. Grenades are the most effective against Fred, if the player dosen't have a powerful gun.


Other AppearancesEdit

Blaster Master (novel)Edit

Though Jason does encounter a hologram-frog at the end of Area 4, it's simply the image of another bullfrog, not actually Fred (whom he would encounter later).

Blaster Master ZeroEdit

Fred appears in Blaster Master Zero and is again the catalyst of events. Instead of being a normal frog, however, it's a drone sent by Sophia III to investigate mutant infested planets. When it arrives on Earth, it takes the form of a frog and is discovered by Jason Frudnick. Jason keeps Fred as a pet, but it eventually escapes, and travels through a self-generated wormhole to Sophia III. Jason follows it, and discovers Sophia III for himself. Jason follows Fred's signal and eventually recovers him. Later, Fred leads Jason to Sophia Zero.


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.