Main Menu
Main Page
Recent changes
Random page


Major Glitches
Trainer escape glitch
Old man trick
Celebi trick
Select glitches (Japan)
SRAM glitch
CoolTrainer♀ corruption
LOL glitch
Rival LOL glitch
Super Glitch
ZZAZZ glitch
Pomeg corruption glitch (Glitzer Popping)
Elite Four door glitch (Japan)
Pokémon merge glitch
Pokémon cloning
Time Capsule exploit
Arbitrary code execution
Coin Case glitch

Other Glitch Categories
Glitches by generation
Glitches between two generations
Japan-only/language specific glitches
Music glitches
Natural glitches
Non-core series glitches
Non-Pokémon glitches
Officially acknowledged glitches
Recurring glitches
Dead glitches

Pokémon GameShark codes
The Big HEX List
GB programming
Debugging features
Easter eggs
Error traps
Glitch areas
Glitch myths
Non-glitch exploits
Placeholder texts
Pokémon glitch terminology
Unused content and prerelease information

Useful Tools
8F Helper
GBz80 to Items
Old man trick name generator
PATH (Prama's Advanced Tweaking Heaven)
Save file editors
Special stat/Pokémon converter
Trainer escape Trainer Pokémon finder

Legendary Star Blob 2 (Hakuda)
Pokémon Speedruns wiki
PRAMA Initiative
Become an affiliate!

Search Wiki


Search Forums


Author Topic: Pokémon Battle Revolution U-turn Poké Ball error  (Read 248 times)

0 Members and 1 Guest are viewing this topic.


  • Member+
  • *
  • Offline Offline
  • Gender: Male
  • Probably on Bulbapedia
    • View Profile
Pokémon Battle Revolution U-turn Poké Ball error
« on: February 03, 2017, 10:21:06 am »
This YouTube video shows a player using U-turn, but the Poké Ball used when it goes back to its Trainer seems to be incorrect. Swellow is caught in a Poké Ball, but the U-turn animation shows it going back in a Master Ball. Latios—the Pokémon that was previously in the same slot as Swellow, but fainted—was caught in a Master Ball, however.

I have not tried this myself, but thought I should share it here since it didn't seem to be common knowledge. Also, it might be worth looking into the exact conditions to reproduce this, since the video seems have found the bug entirely accidentally.