theSLAYER

and how did you get Zekrom into Moon. Not talking about how you transferred into SWSH. How did the Zekrom get created?

Guh. Given you cannot provide any real info,I don't have any real responses to provide too, besides "there's provide something wrong with your Zekrom, or your injection method (or both). Stop hacking mons in."

if this is a response to my statement about "cannot be done with official methods", then you're proving my point >< It *probably* is fine if you don't do it online. :3 but yeah, we don't have the values for block data. Plus there's other potential issues, being the game might crash if you insert the wrong NPC. But given you haven't talked about that, I guess it isn't an issue in this instance

I'm not asking for a picture. I'm asking for the Zekrom file. Presumably a pk8 file.

Focus on the two Registeels. It proves (a) The GO symbol is tied to Go origin game and Go Met Location. (LGPE mons from GO doesn't have it) (b) It implies that "barred entry into a game" could be a byte, or some other form of data on the pk8. If it wasn't, either both Registeel will be disallowed entry, or both Registeel will be allowed entry. (The cross symbol) The user chanced upon the oddity when testing my claim of Go mons needing to be Go origin game and Go met location. (The user was using a Zapdos, and was puzzled by why it appeared to allow entry when that SWSH save doesn't have a Zapdos). I got the user to have both mons side by side in one image, to confirm the situation. (As I said, if the HOME checking wasn't dependent on some other value, either both Registeel will be disallowed entry, or both Registeel will be allowed entry. Not half and half.) (1) HOME ID is re-assigned whenever it re-enters HOME. The mon will persist not being able to enter SWSH saves that never had that species. I tested that for myself. SW caught Melmetal, SH didn't have it. GO Melmetal couldn't enter SH, despite being in SW and re-entering SH. You could argue that they could just recalculate the HOME ID to match that formula on re-entry, but thus far the HOME IDs just climb sequentially, doesn't appear to adhere to any weird jumps to match a formula. (2) As per what I said in number 1, it "does not get cleared". The requirement to enter a save that has had it persists. In any case, I'll like to attempt more tests to narrow down the phenomenon. Also, apparently only mythicals/legendaries has that entry requirement. Since we know HOME isn't checking by species (the Registeel example above), it'll make sense that they leave a bit/byte on it somewhere, then just keep checking if the bit is flipped. My next order of business, would be to check the fateful encounter byte (I think it's shared with other stuff), could be fun.

That's not a question mark. XD Before I state my theory, I'll like to see the Zekrom file you used here.

erm... watch the video.

You, probably. ;P

Let me stop you right there. While what you've found hasn't been said before, this kind of thing (regarding gym leaders and exclusive content) to an extent has been around since SWSH. For example, if your swap the save at certain times, you will see Zacian's model (above the Power Plant) in Pokemon Shield. You'll see the wrong gym leader in a different game (tho talking to them will crash the game, presumably cause the game tries to summon story text, but you're interacting with the wrong character), you can get the wrong t-shirt from Klara/Avery, etc etc. Also, this is not a bug. It is only a bug if it occurs without some kind of modification somewhere along the process. For example: if you were able to officially send SW saves into SH, then it is properly a bug (unintended behaviour using official intended methods). Since you discovered it using unofficial behaviour, all I can say is you this behaviour did not have to be considered by the devs, since you used unintended methods. Don't get me wrong: it is certainly something interesting, however you cannot claim this is a bug. As per my point earlier, this was presumably done with some homebrew app on CFW, not via official methods. Someone would have to do research for it. Nothing can be implemented without proper research and documentation. (and sadly, I doubt it'll occur) However I suggest to not use doing that, especially if you intend to go online, as this is not legal. Don't risk your save or your console bud

I've mentioned the Met Location thing being relevant here: also, it's been soft confirmed on discord: Left Registeel from GO, right generated (as per met location), and the GO symbol appears. However, there appears to be another flag on the mon, hence why the generated Registeel can be moved into SWSH.

they don't keep their moves after transferred.

Join a Discord channel that supports Sysbot. You don't need a hacked Switch. Drag and drop the pk8 file into the chat window, and comment .trade/$trade (depends on what syntax the channel uses), and it'll set up a link trade. Do note there is a queue, so you may have to wait. In any case: https://disboard.org/servers/tag/sysbot From my understanding, Sysbot shares the same core.dll as PKHeX, meaning it has the same legality checking system. so it depends on (a) whether PKHeX's legality checking is updated to include those (b) whether the server you joined is using the latest one (c) Alternatively, if (a) and/or (b) is false, does their channel support illegal trades

or you could use Sysbot to trade you all the mons individually, this way you're not taking up someone else's time for 63 trades. Just a thought :,x

It could be a special cause for GO. Plus Gen 6 to Gen 8 used similar PKX structures anyway... So even if the data is still there (for Gen 6 onwards, they are), it may simply have gone unused and not referenced by the game. The game checks the Origin game data to show that it was from Kalos region or whatever, for example.

This segment shouldn't be mostly blank. Should have your Trainer name. I think you're using the state save feature on Citra, and never saved in-game once.

upload your save here.

so it's legal then. probably just some kind of minor error. just set it into the game and move on edit @Shady Guy Jose going back to what we were talking about, how HOME treats the mons, appears to be because of Met Locations. (ignore the illegal symbol; I'm using an outdated PKHeX atm)

no prob.

Take the blocks from a save that have them inactive. At the first place, that's the point of what we're doing. Maybe take the blocks from here:

I don't think you imported the blocks correctly. And you can see, this is still active. When I imported one of the blocks into your save, it turned false Either that, or you imported a block that still has it active..

can you send me the edited save?

You didn’t mention importing the blocks into the current save. Did you do that ?

I literally just tested that. The sticker you see on Mobile HOME changes due to HOME tracker updating. Yup, it is as per what I concluded in my previous post.

a) You didn't answer my question. There was a purpose to me asking. b) Not true. If you bothered to look hard enough, you'll see it.