Hello so yesterday after the gold server crashed, my Drapion disappeared from my team, I did not release him and he is not in my pc box(100% sure). I was told on discord by a modo that apparently it is not a known or common bug, a pokemon doesnt appear like that usually. also you dont require the ID to do anything about it either.

 

All I can remember about the Drapion is that he was around lvl 40, don't remember the ID, IV or nature only that he had a quick claw equipped. I was leveling a Skorupi in Cerulean cave for dex entry 5-10min before the crash, evolve him into drapion after that all my team were K.O. except drapion. Next the server crashed during a fight against an Arbok after that I relogged, I was still in cerulean cave with only 5 pokemon K.O. for 5 seconds then teleported in pc. Drapion was missing from my team(empty slot) and not in pc box. It was not a rollback I still got the pokedex entry, sorry that's all I can remember.

 

Like I said on discord it is not a big deal for me if not able to restore it was a pok only for dex I just lost a quick claw.

Edited October 11, 20223 yr by Xxxboom
account: Boomchan gold server

Hi @Xxxboom

 

I'm sorry for the inconvenience.

 

Unfortunately after having checked your account, Boomchan on Gold, it seems that I could not find any Drapion at all in your PC, however it seems that you've released a lv 41 Timid Drapion with the ability Keen Eye, caught on the 3rd of October. As for the Quick Claw item, there appears to be one in your bag, and the released Drapion was not holding the item.

 

I hope I was able to help you. Please let me know if you have any other issues or questions.

Have a great day.

Hi the thing is that I am sure I did not release the drapion myself and nobody have access to my account. For the quick claw I know for sure that I had two (few hours before I traded one with my other account). Thank you anyway I didnt ask to restore them just wanted to report a possible bug.

I appreciate that. Thank you for taking the time to report this bug. Not to cast any doubt, but unfortunately it seems like this particular case isn't a bug, however we will keep an eye out on stuff like this in case it happens again in the future. 

 

I'll be locking this thread now, if you run into any other issues, please feel free to create a new thread.

Once again thanks and have a great day.