You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Pokémon Emerald, after the fight where you team up with Steven against Team Magma, the Pokémon he picks for his team confuse the team viewer, and end up sticking around even after trying to reset it with my own Pokémon from the PC. I assume this issue would probably occur with any dual battle with a teammate. tried refreshing the tracker, but that didn't seem to fix it.
Steps to Reproduce
Make it to Mossdeep city
fight team magma
make it to boss battle
team up with Steven
selected only 1 pokemon for myself (not sure if that mattered or not but felt it was worth noting)
after the battle, team viewer should be broken
What tracker version are you using?
v7.5.3
What operating system are you using?
Windows 10
What emulator(s) are you seeing the problem on?
Bizhawk 2.9
Relevant log output
No response
Additional Information
The text was updated successfully, but these errors were encountered:
chandlerbogolin
changed the title
[Bug]: Addition Pokémon showing up in Team Viewer After Battle with Teammate
[Bug]: Additional Pokémon showing up in Team Viewer After Battle with Teammate
May 17, 2023
Whoops, I seem to have replied to the wrong conversation around the Team Viewer. I believe this one has yet to be resolved, and is not currently fixed. Sorry about that.
Describe the bug
In Pokémon Emerald, after the fight where you team up with Steven against Team Magma, the Pokémon he picks for his team confuse the team viewer, and end up sticking around even after trying to reset it with my own Pokémon from the PC. I assume this issue would probably occur with any dual battle with a teammate. tried refreshing the tracker, but that didn't seem to fix it.
Steps to Reproduce
What tracker version are you using?
v7.5.3
What operating system are you using?
Windows 10
What emulator(s) are you seeing the problem on?
Bizhawk 2.9
Relevant log output
No response
Additional Information
The text was updated successfully, but these errors were encountered: