Bug Report - Geolocation and encounter data being mangled during transfers (gen 6)

[DrasticGray]

Describe the bug
PKSM Is mangling the data of pokemon transferred between copies of omega ruby and alpha sapphire. I have wiped pksm's extdata completely to fix any potential bad settings. Every time a pokemon is placed on the destination game it has an extra entry in the geolocation data for japan with no subregion. It also apparently does something to the encounter data.

To Reproduce
Steps to reproduce the behavior:
Load a save of pokemon omega ruby, move a pokemon into the storage, save the storage, save the changes to game data.
Load a save of pokemon alpha sapphire from the same ds, move the pokemon into the game's boxes, save everything again.
Open the data in PKHeX, the pokemon will be illegal with the following errors:

Invalid: Encounter Type does not match encounter.
Invalid: GeoLocation Memory: Gap/Blank present.

Expected behavior
Moving pokemon into the storage makes no change, pulling pokemon back down to game adjusts data for handler and geolocation to match the target save data.

Screenshots

If necessary to nail down the issue I can upload a couple of .pk6 files of affected pokemon.

Information about your environment

• OS version: 11.17.0
• PKSM version: 10.1.1, loaded via installed cia
• Entrypoint: luma (b9s)

[DrasticGray]

Just to add, it appears that the geolocation data is being written by PKSM in reverse order as well. new data is appended to the list instead of bumping things down.

[fireanddream]

It has happened to me as well. I thought it was me randomly changing the "edit during transfer" option at some point. That was not the problem.

The error also happens when we put pokemon in storage and put them back in the same game. I could send all 31 boxes to PKSM, save storage and immediately pull them back out for about half of the pokemon to have an entry of [Japan - empty] region entry in the Residence tab.