theSLAYER

There isn't any direct way to view your save on PKHeX when you have a non-hacked Switch. The indirect way, would be to locally transfer your save to a hacked Switch, using Nintendo's official save transferring function. Note that both Switches would need to share the same user profile. (also can't be across the internet; locally). If you were interested in extract your mons to see them on PKHeX, you could initiate a trade with 'Sysbot' and they could dump your mon without completing the trade. But since you aren't interested in extract mons, I don't think there's any other alternative for you.

I'm not sure how much I can help. You have a comparison with and without the save, so you know where the save is stored (looks to be location 0x2000). I took a random save from our site, and the length is 0x8000 You could try to use Edit > Select Block (or Ctrl + E) Start from location 0x2000, select length 0x8000, hit OK. This will select all the data in that range, and you can copy it to a new file, and save that new file as a "test.sav", and see if PKHeX would open it.

There's still saves. It is just that saves with a lot of illegal mons (or blatently hacked problems etc) were purged.

not that I know of.

It’s not a save file, but it contains the living Dex. As per our rules SV saves cannot be shared. I’ll recommend you first search through the Downloads sections, instead of asking people for files

@Islushy try this, read and follow all the instructions on the page, keep a safe unedited backup somewhere, use at your own risk

there's all kinds of files in our Downloads section, such as this.

It has been removed for containing multiple illegal files.

Updated I'm assuming you're using the wonder records tool. I've updated it. updated I vaguely recall some mons not actually being stored. You can try to give her a shiny and see what happens.

Not GF, so can't say for sure we know what their plans are. Generation 2 had weird design choices, scrapped content, and many odd 'broken pairs'; like Gloom getting a split evo but Weepinbell didn't (was considered and datamined from Spaceworld), and Vulpix not getting a pre-evo despite the Pokedex hinting at it (was also considered and was datamined from Spaceworld), and Farfetch'd's planned evo. However, the one thing that wasn't datamined from Spaceworld, was a Dunsparce evolution. Granted, that doesn't cover all possible "left on the cutting room floor" ideas, but at the very least, through all the leaks, IIRC Dunsparce evolving wasn't a possibility they pursued. If I had to hazard a guess, GF saw all the hype around fantastical evolutions, and decided to defy expectations.

I’m confused, I think this one is the one that’s locked. I vaguely remember something about “it’s locked to small because Hisuian Typhlosion is small” or something. Anyhow thanks for the clarification. I believe this is the conclusion then: I’m not sure which revision of SV can communicate with HOME; this means that technically if you’re on a revision history that cannot communicate with HOME, your height shouldn’t be locked to 128, cause there’s no way to have scale -> height legitimately. But one would likely to be on a revision that can communicate with HOME so there’s no issues there

Ah so you’re saying scale was always 128, but they’ve just never noticed it, and HOME copying scale to height showed that it became fixed. There’s a few that were variable or fixed to a different value right? Like the Pikachu the unrivaled and The unrivaled Hisuian Typhlosion?

No SV game patch changed the Height/Weight behavior, it was a HOME patch. IIRC correctly it happened with wonder card redemption, and based on their description thought it could have happened to Poke portal news too. While that’s a reasonable conclusion, I think they’ve said stuff they’ve caught are stuck at height 128. Were raid captures always at 128 at the first place? I’m under the impression it was random; I’ve not done Tera raids in a long time, but I recall they could be random, and Anniversary Pika had its scale set to be “highly likely” jumbo.

Game revisions (software patches) had changed the height/weight between variable and fixed for certain scenarios, so using poke portal events that undergone such changes may cause issues. To be clear, I don’t know “which way around” this situation would be. (Basically did it go from fixed to variable or vice versa?) As much as poke portal events vs game revision supposed mismatch is a nightmare, and could cause potential issues legality-wise, it’s possible for such things to occur naturally. Imagine you’ve legally connected to poke portal news during software revision 1.0.0, then never brought your game online nor updated the poke portal news until now. But you’ve also updated your game revision. Thus it is possible to create this kind of “mismatch”. But note this only works in the “forward” direction (you can’t downgrade game revisions, and I do not believe you can legitimately transfer your save to another switch with a lower game revision and the save to load) That part I’m not sure. Keep in mind met date and seed generated isn’t an indication of game revision versions, so as long as their existence is not something that can only be explained using the “backward” direction it should be fine.

No.

Could try to “clone” it outside of BDSP. Like place into HOME, withdraw in PLA. Then backup the PLA save. Now it back into HOME from PLA. Revert PLA’s save. Now you have 2; 1 in HOME, 1 in PLA. Now the one in HOME can enter SV. Keep in mind to never have the both of them in HOME at one time. This way, they should share the same HOME tracker.

Sorry, not understanding the scenario. Is the error from the program, tell you there’s no saves found, or that the NDS homebrew is unable to read and dump the data from the cart? Try following this tutorial exactly, and let me know which step causes problems for you:

I’m unsure if stationary encounters like Calyrex have their height/weight fixed. I’m unsure about wonder cards Based on absolutely nothing, I think you can try to catch/redeem in-game a few and see if it’s fixed. If not, it’s likely random via triangular distribution

1. Depends on context, if caught wild or via raids on the Switch, then likely true. Do note that putting a Mon through HOME can mess with values like scale or height, but depending on context you’ll be able to see the relation 2. For example, for clones transferred into HOME from Bank, they get set height/weight (and height’s value gets duplicated into scale) via randomness that has a triangular distribution. So in this instance yes, height and weight can have combination (scale would be a duplicate of height). But keep in mind how likely it would be.

Yeah maybe not. Sorry to hear that. There’s any kinds of repro carts and AFAIK this method doesn’t work for all of them. One last thing you could try, is to see if you can “dump the save normally” using regular (not bootleg) save dumping options. For all we know, there is some save partition. I know an old repro I got saves the save separately; the downside was the battery died quick and the save got wiped. (I assume they don’t fake carts like that anymore but who knows) or, maybe you’re not dumping enough of the ROM, and the save is nested somewhere further in (and the original save you dumped from it is a backup placed closer to the start) If you do another regular ROM backup, does it have the 4 saves (make sure this new backup is separate and name it different from the existing ROM backups)

Yeah the range is from the file name of the saves you’ve extracted. You should have been able to completely wipe the save data. Try getting a fresh backup and use my bootleg tool to dump to see if you get anything. i wonder if your cart backs up the data elsewhere, or if you didn’t manage to restore it somehow. Also I won’t recommend getting another bootleg cart.

Yeah aware that pkNX doesn’t have some editing for SV. I was trying to say if you have the files, can just try hex editing.

I want you to try something (but make sure you have a original backup stored safely somewhere else first. First make a copy of the ROM. Since you can perform hex editing, I want you to go to 0xFC0000, and make it FFs all the way to the end of the file. (use Edit > Select Block to select the range of data, then use Edit > Fill Selection to make them all FF) Then restore that newly edited file into your cart. That should confirm whether the issue is with restoring data into your cart.

Or you could replace an existing encounter’s reference with the unused one. Like the long string of code that is used by the encounter scenario to call the details of the Pokemon. I recall doing something similar, but it was with a nice pkNX gui (for SWSH). With absolutely no real info, I’m speculating that you can hex edit the reference string to swap to another, provided you know what’s the code and you have the correct file. This way you won’t need to deserialise and reserialise the flatbuffer. (Assuming they don’t checksum the flatbuffer) At least with my experience with SWSH event raids, they don’t checksum the data.

I’ll need to review this. Thanks for the heads up, I’ll review that too.