FANDOM


Yu-Gi-Oh!

  • In episode 11, Joey Wheeler finds Tristan Taylor's cards and thinks they are cards somebody forgot until Tristan yelled at him to give it back as those are his cards. Joey notices "Lava Battleguard" and notes it looks familiar. Joey then takes out this card and notices both cards are similar to each other. Tristan gives "Lava Battleguard" to Joey and states he should try it out sometime and Joey states he will. Later Joey uses this card during his Duel against Rex Raptor. He Normal Summons this card in Attack Position after "Flame Swordsman" attacks and destroys "Uraby". This card then gained a Field Power Bonus. On Joey's next turn, he summons "Lava Battleguard" (who also gained a Field Power Bonus). Due to the effects of both "Battleguards", they gained 500 ATK from each other's presence. "Serpent Night Dragon" then attacks this card as Rex was unaware of the effects of the "Battleguards". This card then destroys "Serpent Night Dragon", making the effects of the "Battleguards" more apparent to Rex. In the next episode, Rex Normal Summons "Red-Eyes B. Dragon" and equips it with "Dragon Nails", increasing its ATK by 600. "Red-Eyes B. Dragon" then attacks and destroys both "Battleguards".
  • In episode 16, Joey used this card during his Duel against Seto Kaiba. He Normal Summons this card in Attack Position. Kaiba's "Rabid Horseman" then attacks and destroys this card.
    • This card can also be seen in Seto Kaiba's briefcase when he takes out a Duel Disk from his briefcase and tosses it to Joey.
  • In episode 218, Tristan uses this card and "Lava Battleguard" to fight Zorc Necrophades's henchmen. After a while, Yugi says there is no time to fight as they must find Yami Yugi. With all their concentration, Yugi and his friends escape the henchmen and head towards where Yami Yugi is.

Yu-Gi-Oh! ARC-V

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.