voidpet / bugs

61 stars 9 forks source link

Vivid voidpet not appearing in the pet log #680

Closed Khavic closed 2 years ago

Khavic commented 2 years ago

Describe the bug

I traded my elemental vivid for a fathomless + vm. At first everything was fine, the fathomless is in my memory and the vm got added. However, once I went to the pet log, the fathomless did not appear, though I checked and refreched, it's still not here. (It's my first fathomless ever.)

To Reproduce Steps to reproduce the behavior:

  1. Trade something for a vivid voidpet you never catched before
  2. Check if it's in your memory
  3. Check the pet log as well
  4. See that it didn't appear

Expected behavior To see the nex vivid in the pet log, since it's the first time you got one.

Video or Screenshots image image

Desktop (please complete the following information):

Smartphone (please complete the following information):

Additional context Add any other context about the problem here.

benawad commented 2 years ago

Thanks, just fixed this. What's your voidpet username, I'll update your pet log

Khavic commented 2 years ago

Hello, thank you for responding. My username is Khavic.

Le lun. 11 juil. 2022 à 02:20, Ben Awad @.***> a écrit :

Thanks, just fixed this. What's your voidpet username, I'll update your pet log

— Reply to this email directly, view it on GitHub https://github.com/voidpet/bugs/issues/680#issuecomment-1179834018, or unsubscribe https://github.com/notifications/unsubscribe-auth/AZ74FSVRPS3645XPNXJ2G3LVTNSE5ANCNFSM53FI3S3Q . You are receiving this because you authored the thread.Message ID: @.***>

benawad commented 2 years ago

done

Khavic commented 2 years ago

Thank you!

Le lun. 11 juil. 2022 à 16:50, Ben Awad @.***> a écrit :

done

— Reply to this email directly, view it on GitHub https://github.com/voidpet/bugs/issues/680#issuecomment-1180509157, or unsubscribe https://github.com/notifications/unsubscribe-auth/AZ74FSRWRS42XLO4V22ROSTVTQYE7ANCNFSM53FI3S3Q . You are receiving this because you authored the thread.Message ID: @.***>