>>57833229Oh wow, somehow I deleted all of the quotes I had written down from the "code experimenter" exchange, whoops.
>>57822548Here's what got left out earlier:
"Im gonna say this as someone that has researched the memory of this game - any code that changes wild encounters or moves will not work at all as intended or even give 100% consistent results due to how the 16 bit expansion works
If someone believes they have a way to do so, then they can DM me about it as I am happy to test things"
"-it doesnt work how you think
Moves are stored in the game as 2 bytes so the game does some weird on the fly calculation to save moves and species as one byte in the RAM
Meaning that it stores a 2 byte variable as one byte
However, this byte isnt consistent and actually varies due to… something
So that byte you gave for the move actually doesnt always give the same move for everyone"
>"haven't tried many species, it seemed to be consistent""I feel you do not understand me
It is for you as the calculation probably isnt changing at all as you just poke a byte
But for those that do things in a different order it does change
An example is - I know where the pokemon species ID is for your party in RAM - a Sandslash for me is not consistently the same as a Sandslash gor you byte wise due to something affecting the calculation for the expansion
It isnt even the same per route lol"
>"so every copy is different"."No
A player doing the exact same thing will get the exact same calculation
But idk how the calculation actually works but I do know it isnt the same value all the time
And more likely than not it COULD corrupt saves
Which is why I am very against sharing untested codes
(If anything this calculation is what I believe breaks the daycare for some people but I could be wrong)
I should look into the how it works again one day."
and then I posted the rest here
>>57833245 