Leaderboard

And for the record, if the Pokémon's origin isn't a SV game, then absolutely no. The HT/WT/Scale was GIVEN BY HOME. It is generate/rerolled in HOME. It has the data before it even enters SV. No offense, I think you have no idea what you're saying, and might be unconsciously bending known facts to fit your mental narrative, to justify you being able to whatever size you want. It is likely an unconscious cognitive bias, and not a personal attack. Just pointing it out before you fully commit to that train of thought. It is true that if a mon was caught/bred in SV, HOME would absolutely have no way of knowing what size it was supposed to have before entering SV, but then you encounter a different breed of issues: the size is defined by RNG, and what if that RNG state was correlated, and became public knowledge after? Changing HT/WT/Scale could break that. A lot of people in Gen 8 didn't know there were RNG correlations (cause at that time it wasn't discovered), and all the edits became illegal. So both sides (pre-HOME and post-HOME) of the coin you're causing trouble for yourself. Literally keeps tracks of data structures. HOME probably doesn’t assign the space for every piece of data to a user, but instead give all of them a list of trackers regarding what mons a user has, done for space saving purposes. In any case I’m not too interested in discussing how to beat HOME’s TOS; this feels like it’s slowly moving to that direction. You probably shouldn’t. When a HOME Tracker changes (if it mutates data from a previously valid tracker), it Carries forward all valid data from the previous tracker. That said, HOME could easily bring forward the previous tracker too, making a chain of trackers. Meaning they can follow the chain to find the first entry point, and see who is the first device that brought stuff over. I feel like I've already tackled the original queries, plus more, in this thread. Any last questions from the people that are in this thread, before I lock this thread?

In order for these pokemon to be shiny XOR = 1 (you can check this by hovering over the PID box in pkhex (only works for .pk8 files) ) If XOR does not equal to 1 you will get the " Invalid: Static Encounter shiny mismatch." error. Here are 3 methods to fix this: Method 1: Re-roll PID and click the shiny button. Repeat this until its legal. Method 2: Do the same as Method 1 but this time try to get the lowest XOR you can. In my example below I got XOR = 5 now adjust the last number (0-9) or letter (A-F) until you XOR=1 then check legality in this case I had to change 6 to 2. Method 3: Step 1: First you need to put you SID and TID next to each other to form a 10 digit number some TIDs and SIDs have 0s infront of them make sure you include those. For this example I will use SID = 1234 and TID = 567890. Putting them together we get 1234567890. Take this number and convert it into hexadecimal (converters are online). Converting 1234567890 to hex we get 499602D2. Step 2: Choose a 4 digit hex number and put it next to itself. For this example I will use ABCD so next to itself would be ABCDABCD. Step 3: Now we need to take both hexadecimal numbers from step 1 and 2 and XOR them so it will be 499602D2 XOR ABCDABCD. You can find a XOR calculator online. So 499602D2 XOR ABCDABCD is E25BA91F. Step 4: Decrease the last number (0-9) or letter (A-F) of step 3 by 1 so E25BA91F becomes E25BA91E. Step 5: Use the result of step 4 as your PID