theSLAYER

Even so it’s against our rules. The save could be shared to others. It is less an issue for you, and more are issue for the person sharing. PKHeX has options to unlock the 7* raids, there is no need for someone else’s save.

I’m sorry, but the way you described makes it unclear if it’s one device or two devices. but yeah, you could use device A’s Sysnand (which is hacked) to transfer the save legitimately to device B (unhacked). You should be able to figure out how to move the save around in Sysnand and Emunand on device A. Just make sure you keep backups (saves, mods, nands, etc) before you do any moving of anything.

We can’t guarantee you won’t get banned. However there have been ton of people, who include YouTubers who literally play with mods with friends online as content, so keep that information in mind. All at your own risk of course. I’ll say temporarily remove all mods when you go online to transfer the saves. You can always reinstall the mods after.

Sorry to necro. The amount of “guaranteed IVs” are known based on encounter type, or any other details that were datamined. For example, some brilliant encounters have 1 or 2 (if I’m not mistaken). Wilds have 0. Symbol encounters can have 3, depending on what you’re fighting. Gotta do research on what encounter you intend to use the tool to validate.

I use the program HxD. Not sure where I can point to that teaches how to use them. If Manu shared you screenshots or addresses on how to edit them, then you could just load up the file into HxD and edit as per what he said. Yeah save editing being editing via PKHeX. In this case, loading your save into PKHeX, then reading the data of your target mon, then manually editing the height/weight values. Though frankly modifying height or scale (depending on game) is enough, since weight isn’t really used.

If both Switch’s have the same user profile, you can share saves across them, even if one is hacked and one isn’t. This is done legitimately using Nintendo’s Save Transfer (whatever the process is called). User profile can also be shared locally using that legitimate process. Will require both devices to be next to each other, not banned, updated to a point where they can access the network (needs server authentication before it allows local save transfer)

If you own a 3DS you can simply hack it. All 3DS models can be hacked. In all likelihood, hacking your device and doing jt yourself beats waiting for someone to reply and do it for you; we aren’t a trading nor “Gen request” forum, so those type of requests usually don’t get fulfilled. (Also, said user hasn’t been online in pretty much 5 years) Anyhow, https://3ds.hacks.guide at your own risk.

Deoxys is not capturable in BDSP. Genning it there and transferring wouldn’t work, without a valid server-assigned tracker.

There is no need to multi post. If no one replied your latest post, just edit the new info in. Ignoring Jirachi, your mons (a) have a HOME tracker and (b) appear legal. With that in mind, it may not be going in because (1) exact same Mon with same tracker is already in your HOME or (2) the mons were already edited thus making the tracker invalid [we can’t see what exact details the server expects based on the tracker] If you no longer have the proper originals, best bet is to try again starting from uploading them into HOME from the correct game.

@bigdom8 if you tried to place 5 Pokémon into HOME, and 1/5 of them is bad, you get flagged regardless. try placing them in without Jirachi. Do you get any error now, and if so, what is it?

Perhaps you could try to modify the wonder card to have a fixed size (preset), then inject it via BCAT injection? Else there’s nothing else you can really do. I can’t walk you through that though. As far as I know, nothing in the save can control the size of a Pokémon yet to be received. Besides that, save edit to modify the size.

I can’t remember, but for gifts it’s either preset or assigned randomly.

Upload said file.

This part isn’t true. They’ll just clone server-side data from the tracker provided, then proceed to create a new tracker with the associated data. granted, it is easy to check on their end if they want to (basically check whether duplicate trackers existed, that ain’t Nincada family), but so far they’ve not done that. In any case, it’ll be at your own (reader’s) risk

You can dump the ROM from your console, modify the raids (becomes a ROM Hack), then run the ROM hack on your console. The hacked raid can have species and rewards modified. I know it was literally said earlier, but I’ll like to remind you that it cannot be shared, and make doubly sure you’re in flight mode. (And delete the hack when you’re done)

Sooty I don’t.

Even if PKHeX blocks modification of mons that bears a HOME tracker, the Sysbot can simply wipe the HOME tracker. It depends on the settings that the owner uses..

PKHeX doesn’t support what you’re trying to do. What you can do is: 1) inject the items directly into your bag (cause functionally not any different) 2) perform BCAT manipulation to receive the gift in-game

If I remember correctly, have the item in your bag. Make sure the entire Terapagos storyline has been completed. Go talk to the peach figurine at the shop in Kitakami. if it still doesn’t happen then I have no idea

Ultimately these points are what I’ve seen, but they could have been picked subconsciously due to my biases, in order to align with the narrative in my head. There are probably arguments out there that counter my point, but well, due to my biases, I may have subconsciously found them not reliable. I’m not the most reliable narrator out there when it comes to this topic. but in any case yeah, we’ll never know what they’ll do. To throw in a line relating to investments, “past performance is not indicative of future performance.” As it stands, the past is really all we have to go off of. But we must never never forget that they can simply do whatever they want.

sounds like you did something you shouldn't have. you probably missed something under current clothes/skin. Everything associated to the player's body (was it current status? can't remember the name) needs to be changed to match the other gender, else the game will be confused by what it sees and just not load.

You sure said it. There’s many topics about the same issue.

My Biases I’m the opposite from you; there’s some stuff I am okay with them being forced into being mini, since 1/16,256 to randomly roll for a size mark is a pain. Now with my biases explained, let's go on and discuss. 4 key points you need to know: 1. When the hyper training issue (from transfers during initial HOME launch) was a thing, they acknowledged the issue, and fixed it promptly. [This shows they’re capable of checking their logs and digging out initial entries and combining initial unmoved data and mixed data] 2. When the GO Lv 1 transfers was detected to be a bug on their part, they acknowledged and fixed that (by having them correctly reflect as lv 100). However, notice how they didn’t revert to the level the Mon that was sent into HOME, despite the fact that they have logs and could have checked. 3. They *did* fix the 0 scale issue, but from a different perspective; LGPE XS and GO XXS mons doesn't retain the size when shifted into HOME, because the size were forced to rerolled; they acknowledged it and fixed that. Notice how they didn’t do anything about the issue you have in mind. 4. You may want to read up on all the issues they have had. I won't be discussing all of them, but some may show up. With those 3 key points out there, lemme discuss *why* I think the fix wouldn’t happen. 1. No public acknowledgement nor announcement. Whenever there is an issue, they’ll acknowledge it and work on and fix it. What you described isn’t acknowledged (that I know of) and thus not fixed. 2. Issues along the same vein or core were fixed 6 months ago. They already fixed issues tangentially related to the one you have in mind (like 6 months ago), but ignored the scale 0 thing. Given the proximity, you would think they’re aware. This suggests they wouldn’t/doesn’t want to fix it. 3. Do they even see it as an issue. "Canon in player's-mind" thing - since you’ve already seen it as mini in PLA, it would be weird for it to suddenly become XL when shifted. But I can’t say for sure. Data the player normally cannot see - given height/weight/scale are hidden data-points that the player should not have been able to witness directly, and the HOME's implementation of the hidden values should not have been determined, perhaps them screwing up the randomness was not a big deal in their head? 4. Timeliness. If there is an issue, they tend to fix it within a few weeks or at most a few months from the time frame that it occurred (I think that is the maximum, being the Nincada/Shedinja tracker issue). Not half a year. 5. Other issues that should have been fixed Commonality is that they exceeded the time-frame. Spinda - Spinda EC was set incorrectly by BDSP; important as EC determines the spots. Was acknowledged to some degree, by the presence of their 'fix'. Their 'fix' was to prevent entry and exit via BDSP, instead of playing around with the EC. Totems-sized Pokémon - These Pokémon from SMUSUM are taller than what you regularly catch, and tower over regular captures. In the game-data, how the game recognizes them as separate, is that they have a different form ID. When transferred via HOME, they lose that status and get set into the regular species. Since SWSH nor BDSP doesn't show HT/WT in game, there is no 'canon' in terms of sizes, and the least they could do is retroactively max out their scale. Wasn't acknowledged, wasn't done. Personal Conclusion Using factors 1 to 5, I believe HOME won't retroactively fix it. There's no acknowledgement for that specific issue. Issues surrounding the issue has already been addressed. Do they even see it as an issue. It's been 6 months since the fix for related issues has been completed. It will likely fall under the umbrella of other issues that should have been fixed. But that is just my personal conclusion based on the years I've seen them operate. They might suddenly be compelled to fix it, even though it has been left in the corner of the dusty room this entire time. I don't work for them. Who knows really. Have you tried sending a support ticket to them?