Fandom

Chuggaaconroy Wiki

Pokémon Platinum - Episode 30: Crashing and Burning

910pages on
this wiki
Add New Page
Comment1 Share

"Crashing and Burning" is the 30th episode of Chuggaaconroy's Let's Play of Pokémon Platinum.


DescriptionEdit

"We have our fifth Gym battle and are a terrible friend to Barry because it's time for multi-player!"

SummaryEdit

Screenshot (31)

Emile's Game Over.

Chuggaaconroy battles Crasher Wake, the fifth Gym Leader of Sinnoh. Wake defeats Chugga with only his Gyarados fainting. Chugga then defeats Wake in their rematch. Chugga and Wake then encounter Barry, who tells them about a Team Galactic Grunt threatening that he has a bomb. Emile then does multi-player stuff with ShadyPenguinn, and defeats him in battle with just Bodhi.

BiosEdit

None

Pokémon Encountered Edit

Major Battles Edit

Crasher Wake

Emile vs. Crasher Wake (Attempt #1)Edit

Emile's TeamEdit

Crasher Wake's TeamEdit

  • Gyarados (Lvl. 33)
  • Floatzel (Lvl. 37)
  • Quagsire (Lvl. 34) (Not Used)

ResultEdit

Winner: Crasher Wake (2 Pokémon Remaining, 1 Pokémon Fainted)

Loser: Emile (0 Pokémon Remaining, 6 Pokémon Fainted)

Crasher Wake

Emile vs. Crasher Wake (Attempt #2)Edit

Emile's TeamEdit

Crasher Wake's TeamEdit

  • Gyarados (Lvl. 33)
  • Floatzel (Lvl. 37)
  • Quagsire (Lvl. 34)

ResultEdit

Winner: Emile (3 Pokémon Remaining, 3 Pokémon Fainted)

Loser: Crasher Wake (0 Pokémon Remaining, 3 Pokémon Fainted)

Shady Penguinn

Emile vs. ShadyEdit

Emile's TeamEdit

Shady's TeamEdit

  • Frisco/Luxray (Lvl. 35)
  • Felicia/Houndoom (Lvl. 30)
  • Steph/Meditite (Lvl. 34)
  • Defiant/Prinplup (Lvl. 31)

ResultEdit

Winner: Emile (4 Pokémon Remaining, 0 Pokémon Fainted)

Loser: Shady (0 Pokémon Remaining, 4 Pokémon Fainted)

TriviaEdit

Screenshot (32)

Emile's PC Box 1 in this episode.

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.