• ✨ ARCHIVE MODE ✨
    The forum has now been set to read-only mode, no new posts, resources, replies etc will not be possible.
    We recommend you join our Discord server to get real-time response: Discord Invite Link

Duplicate Rollout causing Crash (No Crash Log)

thelastmoikan

Bug Catcher
Hello i was playing online and once i got in a battle i had geodude and pressed to do the skill 'rollout' and my game crashed all of a sudden..
P.S.: Also i get calls on pokegear that they wanna rebattle and when i go there i am not battling them...
 

Tornado9797

Content Developer
P3D Developer
Global Moderator
Please post the contents of the generated crash log here, and in a code module.
 

thelastmoikan

Bug Catcher
A window appeared telling that pokemon 3d stopped working and it must be shuted down and it had two options to close or check for online solutions...
 

Tornado9797

Content Developer
P3D Developer
Global Moderator
A window appeared telling that pokemon 3d stopped working and it must be shuted down and it had two options to close or check for online solutions...
Oh, that kind of crash... Ugh I hate those...
I guess we just need to experiment with Rollout a little bit before we can confirm this.
 

thelastmoikan

Bug Catcher
Hey thelastmoikan, I just caught a new pokemon on ROUTE 30. Let's battle again some time soon.
And when i get there it says something and not battling..
 

Tornado9797

Content Developer
P3D Developer
Global Moderator
Hey thelastmoikan, I just caught a new pokemon on ROUTE 30. Let's battle again some time soon.
And when i get there it says something and not battling..
Okay that is that trainer's default message, he says something completely different when he wants to battle.
I do say that message is a bit misleading, I voucher for it to be altered to avoid confusion.
 

Darkfire

Administrator
Administrator
P3D Developer
This is a long confirmed issue that we havent fixed yet......
i think we are getting it fixed for next version
 

Malcaroni

Bugs Moderator
Trusted Support
Retired Mod
This is a long confirmed issue that we havent fixed yet......
i think we are getting it fixed for next version
I actually just assumed that you guys must have fixed something this old, so clearly this is something else. Guess not :)
 
Top