Snowka Posted January 9, 2021 Posted January 9, 2021 (edited) The title is the bulk of the needed info. I can't seem to figure out what's wrong with it as the only thing I changed on it (SEVERAL PkHex versions ago) was making it shiny while I still had it in LGPE, and it was counted legal then (yes, I know this probably means it was always illegal, but I know shinies can be obtained from these trades?) At first I assumed it maybe had to do with me being on the previous version of PkHex, so I updated earlier tonight, but I'm still getting the same error. Edited January 9, 2021 by Snowka title technically didn't make sense
Delta Blast Burn Posted January 9, 2021 Posted January 9, 2021 I believe for LGPE the xor needs to be 1 for it to be legal, Ctrl + Click the shiny star to make it so.
Snowka Posted January 9, 2021 Author Posted January 9, 2021 6 hours ago, Delta Blast Burn said: I believe for LGPE the xor needs to be 1 for it to be legal, Ctrl + Click the shiny star to make it so. This did not work for me.
ryuko2002 Posted January 9, 2021 Posted January 9, 2021 I had many legit trades marked as illegal in the last version. I haven’t had time to submit my files but black 2 Belinda trades (the one you need to call her and meet in front of the Ferris wheel as well as the trades from let’s go pikachu. I traded extra alolan Pokémon’s and then evolved them to get alola raticate, golem and so on and they are now marked as illegal. They were legally caught so it seems to be an error in the database that I’m sure will be connected in the next version. 1
Snowka Posted January 10, 2021 Author Posted January 10, 2021 22 hours ago, ryuko2002 said: I had many legit trades marked as illegal in the last version. I haven’t had time to submit my files but black 2 Belinda trades (the one you need to call her and meet in front of the Ferris wheel as well as the trades from let’s go pikachu. I traded extra alolan Pokémon’s and then evolved them to get alola raticate, golem and so on and they are now marked as illegal. They were legally caught so it seems to be an error in the database that I’m sure will be connected in the next version. This is unfortunately what I was starting to think, I almost hoped there was something actually wrong with my Sandshrew because then I wouldn't have to wait on an update to potentially "fix" it
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now