theSLAYER

AFAIK I have no idea how that’s decided and stored in the save. However I do have saves for those legendaries (keep in mind saves for ZA can’t be shared, but that would help with research). For now, under block editor, set the pity count to 254 or something. The next special scan (or one after) would be a legend/mythical portal.

And hello! Also gonna ask, what is your main area of interest?

Well hey! For such instances, I think changing the OT name is fine (for mons without a HOME tracker). Make sure you keep it consistent for all the mons who share the same origin (tho realistically, at least based on present standards, HOME doesn’t check it)

Non-event mons from retail carts of Gen 1 or 2 would likely not be flagged, as they are identical to copies caught in virtual console of Gen 1 / 2. You probably shouldn't let the OT be PKHeX. This questions also implies you're creating mons from scratch, not actually transferring them in. Genning for usage against unsuspecting players would be against our rules, and I implore you to not gen mons for online play. Just transfer them normally. Mons captured in Gen 1 and 2 do not have a "captured date"; the date assigned by Poke Transporter would be the "date transferred".

Welcome! What is your main area of interest?

You should select a Pokemon from the encounter database, rather than create it from scratch. Also, trying to change the IVs/PID/Shininess could cause illegality, as the information is 'calculated based on a formula'. I believe you can set up specific stats you want in the encounter database.

Thanks for the clarification, I didn’t know I could do that! @Makotoitou with that in mind, you can grab the csv for every save, combine them into a single spreadsheet, then check for duplicates.

Hey @Kaphotics, sorry to ping, is it possible to add the HOME tracker ID to the Box Data Report in PKHeX? I've tried taking a look at it for SV and PLA, and I don't see it there

I was doing it partway, but realized there's way too much to be worth my time (it isn't a simple task) If possible, make a single upload, with all the version for each language. Then I can go ahead and hide the old version.

If you aren't good at soldering, you could use a service that solders for you. Use it at your own risk!

You'll need a Switch that can be hacked. Switch (launch revision) can undergo software hacking (easy) Later models (Switch Lite / Switch [mariko] / presumably OLD) will need hardware modification Switch 2 is currently unhackable. if you don’t own a model that has been hacked nor easy to hack, then there isn’t much we can say. What Switch do you currently own? For the record, hacked Switches can use HOME; it’s the Switches with pirated content that cannot go online.

I don't think every part of every save has been broken down and documented. You may be able to use ALM, but to some extent you're gonna have to "suffer" and do it one by one. Another option is (1) play the game fully, or (2) use "complete packs" that people have uploaded (at your own risk)

So hyper training sets a flag (for each stat) on the Mon, so that games know it’s an hyper trained stat (so that games can display the perfect stat), and the flag is retained in HOME transfers.

Just use mints for nature, and hyper training for IVs. It would do you good to be suspicious of any flawless legendaries you receive/find, as those, are likely hacked. (they are possible to obtain, but what are the chances of them being shiny and perfect?)

At your own risk.

1. I don't remember what the value should be, and 2. I think they *do* undergo regrowth cycle, if ignored for too long.

(Maybe I used the wrong save or it was added in a new revision, but I didn’t see it in my save of the other tab on the current PKHeX revision. Or maybe it didn’t show the slots cause my resort could have been empty? It’s an old save so I don’t remember clearly. In any case, I’ll download the latest and check again >< thanks for helping them) So far HOME doesn’t ban for duplicates, and don’t seem to apply action for that. FYI any bans or actions so far: The banned HOME accounts were related to targeted individuals who were buying and selling via using HOME as a platform to complete the transaction. Eternal Bad eggs occurred for those who brought up hacked Eternal Flower Flower (caught in XY); transformation was species+form based, not targeted; suggests it was more to block Eternal flower Floette, rather than a targeted strike against users. HOME previously blocked entry for duplicates of a HOME tracker (is was due to the tracker, not because of the regular details), but trackerless duplicates enter just fine. They’ve since allowed for tracker duplicates now (gets reassigned a tracker); this suggests it was more of a technical issue caused by an assumption they had, rather than actual action Granted, they keep a log for every piece of detail, but they’ve not taken action.

And a change in any data can influence the checksum. Anyhow, since I do not know how to extract Resort data from PKHeX, I'll recommend something else: This may work, even if you're using a save as opposed to a ram dump.

Okay I figured it out. When you Poké transfer a Pokémon into Gen 5, it is assigned the met location ID 0x30001. That number for Met Location then doesn't get modified as a mon is transferred further up. (read Gen 5 ID list here) The CSV generated by PKHeX apparently didn't take that into account; it took the ID and displayed a name based on Gen 7 locations, which would be link trade (read Gen 7 ID list here) So it is merely a display issue (I asked about PKSM cause it had display issues for some transfers and it reminded me of that). In any case, fixing the Met Location to what PKHeX suggests would fix the issue.

Did you previously use PKSM or some other third party app to shift the Golem up into Gen 7? Also, are you sure it was met location you're looking at? what does the full line for Golem in that CSV look like?

legal only if you match all details, such as encounter slot. When we talk about encounter slot, an example is to imagine a table with all the possible grass encounters for a route. It is possible for the encounter slot for your PIDIV, relates to a different encounter (could also be different species).