• ✨ 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 Crash while Battling Rival in Aleza Town

Status
Not open for further replies.

Kitomakazu

Starting Trainer
Describe the bug you experienced here.

What I expected to happen:
...
A battle, that's it. No high expectations :)
I was walking to Ilex Forest fully knowing that the rival would pop up for a fight.

What actually happened:
...
The rival and I popped up in the battle map for Aleza town, his gastly came up and my wooper came up and while I was clicking on the spacebar running through the customary automatic textboxes that's always there in every battle (Say... why didn't the devs take up my suggestion on giving me an option to automatically skip the required button mashing and let the textboxes run by themselves in a battle?) (Checking... the suggestion was posted last Dec in the suggestion subforum)

Anyway while I was clicking... the game just randomly crashed. I do have a crash-log here, but I doubt it's useful except for this specific portion where it mentioned for a failure to find an object reference because it wasn't set to an instance of an object.

Steps to reproduce:
1. ... Not sure, other than just proceeding along the plot of the game in Aleza Town
2. ... Go fight the rival with a wooper in your first slot of your Pokemon team (no idea if it has to do with anything)
...

(Add a crash log here if available and enclose it in the code tag with this button:
)


for some reason.... your launcher refuses to allow me to copy+paste :p phooey to that... So I'm attaching this dat file to the post.
 

Attachments

Tornado9797

Content Developer
P3D Developer
Global Moderator
Describe the bug you experienced here.

What I expected to happen:
...
A battle, that's it. No high expectations :)
I was walking to Ilex Forest fully knowing that the rival would pop up for a fight.

What actually happened:
...
The rival and I popped up in the battle map for Aleza town, his gastly came up and my wooper came up and while I was clicking on the spacebar running through the customary automatic textboxes that's always there in every battle (Say... why didn't the devs take up my suggestion on giving me an option to automatically skip the required button mashing and let the textboxes run by themselves in a battle?) (Checking... the suggestion was posted last Dec in the suggestion subforum)

Anyway while I was clicking... the game just randomly crashed. I do have a crash-log here, but I doubt it's useful except for this specific portion where it mentioned for a failure to find an object reference because it wasn't set to an instance of an object.

Steps to reproduce:
1. ... Not sure, other than just proceeding along the plot of the game in Aleza Town
2. ... Go fight the rival with a wooper in your first slot of your Pokemon team (no idea if it has to do with anything)
...

(Add a crash log here if available and enclose it in the code tag with this button:
)


for some reason.... your launcher refuses to allow me to copy+paste :p phooey to that... So I'm attaching this dat file to the post.
There's a very high a chance that your Pokémon fell asleep during battle, which causes the game to crash. However, I have no way of confirming this unless you copy-paste the contents of the crash log in a post; I have no way of reading the log from my phone as an attachment.
 

RoyalGuard

Trainer
Seems to be a sleep related crash.

OwnPokemon={"Pokemon"[194]}{"Experience"[1737]}{"Gender"[0]}{"EggSteps"[0]}{"Item"[0]}{"ItemData"[]}{"NickName"[]}{"Level"[12]}{"OT"[485028]}{"Ability"[6]}{"Status"[SLP]}{"Nature"[9]}{"CatchLocation"[Route 32]}{"CatchTrainer"[Kitomakazu]}{"CatchBall"[5]}{"CatchMethod"[caught at]}{"Friendship"[95]}{"isShiny"[0]}{"Attack1"[55,25,22]}{"Attack2"[39,30,30]}{"Attack3"[300,15,15]}{"Attack4"[341,15,12]}{"HP"[18]}{"EVs"[1,0,17,0,0,12]}{"IVs"[0,31,17,5,13,0]}{"AdditionalData"[]}{"IDValue"[zHAC1CDgMgr]}
 
Status
Not open for further replies.
Top