Jump to content

theSLAYER

Administrator
  • Posts

    22865
  • Joined

  • Last visited

  • Days Won

    1001

Everything posted by theSLAYER

  1. Just take the one from here It’s one officially received and went through HOME properly. If it still flags then wait for PKHeX to fully support transfers
  2. yeah, probably because no one knows. There's no need to create threads again and again about this tho.
  3. The PID is forced. If you drag the file into PKHeX multiple times, you'll see that you can only get the same PID. What isn't completely forced is the IVs. It is random, but must have three 31 IVs.
  4. So for Gen 8, how it works is that the exact same card for a particular event is redeemed by everyone, then the game itself rolls appropriate details. So in this scenario, the nickname is left blank, so it rolls based on the receiving language (mon language is left unset). The PID (in this case Shiny PID) has a preset value, so everyone uses that. If you look at EC, it's all 0s. Meaning that is unset and is set randomly by the receiving game. If you look at IVs, you'll see that it says 'Set IVs'. Not every event has set IVs, but in this case they're all preset. I don't know what else I can tell you. As I said previously, out of PID/EC/TID/SID that you mentioned, only EC can be random. There are only so many different ways I can convey the same info.
  5. Depends on the event.. Our event gallery might mention if the event has a static PID or dynamic one.
  6. In this Zamazenta's case, out of the 4 things you've mentioned, the only thing that can be changed is the EC. Everything else is preset on the Wonder card.
  7. If it's not meant to be changed, then no matter how you change them, they'll be illegal. It depends on whether the event can be encountered shiny to begin with. Also you're not even specifying which event nor generation. Not every mystery gift pokemon have the same PID generation method.
  8. I mean in general, that's the thing for the popular franchises. People will complain, and still buy the games. Also, if we turn our focus away from the naysayers for a moment, and focus on reality: What franchise spans across 20 years with over a thousand characters in 3D models, and all still fully usable, and releases on a yearly to biennial schedules? You're probably going to have to cut down at least one of those aspects eventually.. On comparison I heard is Yokai Watch, and I was told they don't really carry forward all their creatures into the next installment.. Anyhow, I'm not going to disagree with which one aspect to cut down on, but the point is they chose to cut down one, and the act of cutting down something makes sense.
  9. This thread isn't for you to ask for help. Start a proper thread in the appropriate help section. In any case, just read through each step slowly and carefully on https://nh-server.github.io/switch-guide/ (Switch) or https://3ds.hacks.guide/ (3DS), depending on your system.
  10. It’s fine to deposit. Natural clones can exist under some circumstance, and HOME doesn’t have clone checking anyway. (Besides game wise, I think only BDSP implemented clone checks?)
  11. Good luck! If you're okay with cloning, just send over 15-20 saves containing one single mon, and see which is eligible for the mini/jumbo mark ><
  12. as in pokemon that cannot exist in SWSH, like Hoopa or Meloetta. For those, if you use the files, you should not change any immutable values. They work with HOME properly as long as no immutable changes were made to them.
  13. @ZoroCooKings_YT Reviews aren't places for you to ask questions, I'll be deleting it. If the mon is from Gen 2, don't transfer it to HOME. If the mon is from Gen 3, you can transfer it to HOME. PKHeX flags the PID and stuff cause the event isn't well documented, in regards to the generation algorithm and all, but since you know it's from the machine, it's good enough to be used. HOME doesn't care for the most part.
  14. Alternatively, if it's a species you can catch in Pokémon GO, may be better to just do that. XXS and XXL sized Pokémon are guaranteed to be size 0 and 255 respectively, upon transfer. And for some XS and XL, they qualify for 0 and 255 respectively. Just need to check the height before transfer. I would recommend that over transferring thousands of mons.
  15. From what game did you insert the mons into HOME. If it is from SWSH it is fine (cause you're populating SWSH block, as per what GO would do), but that only applies for species that exist in SWSH. if it's a species that don't exist in SWSH, then you're outta luck. The yellow exclamation mark isn't the problem, I wouldn't look at that if I were you. If you brought the Zarude into SWSH, then into SV, it'll be okay, as per the first part of this response.
  16. No reports about that a save from Emunand causing issues in Sysnand and HOME.
  17. Should be able to. I used to trade from hacked to unhacked, but granted that wasn’t Emunand.
  18. Page is currently hidden and under maintenance, I aim to bring them back online, in some form or another. Edit: the page is partially back online Edit 2: Correcting your misconceptions As of time of writing, these are not in Pokémon GO. While true, there are limitations. Sure, you can inject these into your game, with changed OT, TID, SID. But the moment you move them to other games with Pokémon HOME, their data will become invalid. This is due to how HOME works. Read: So if you want one that has your details, that is able to be transferred between games, you've gotta catch them in GO yourself, and transfer them to your own HOME account...
  19. Roughly the first time it was noticed: https://discord.com/channels/343093766477053953/354645386746527745/1118909845643481158 Joe Merrick reporting on the bug: https://twitter.com/JoeMerrick/status/1669326807248543746 Matt's first explanation: https://discord.com/channels/343093766477053953/354645386746527745/1118909845643481158 Matt's level fix: https://discord.com/channels/343093766477053953/354645386746527745/1119088641587822592 Matt's second explanation + fix explanation: https://discord.com/channels/343093766477053953/354645386746527745/1119089458160095233 Fix relating to bad level transfers: https://twitter.com/JoeMerrick/status/1669366866903457794 Fix relating to XXS issue: https://discord.com/channels/343093766477053953/354645386746527745/1118951441042780180
  20. Version .

    478 downloads

    Observation of the Level-Exp Bug Around June 15th 2023, 10am (UTC), it was noticed by players on mobile, certain Pokémon being sent from GO to HOME has the Level of 1 with a Level 100 moveset. It was subsequently discovered that in HOME on the Switch, they appeared to be Level 100. It was also discovered that if you were to transfer such a Pokémon to Scarlet & Violet, viewing the Summary Screen would cause the game to crash. It was around June 15th 2023, 3pm (UTC), that players noticed that this issue (level-exp bug), as well as issue where XXS from Pokémon GO becomes random height (XXS-Height randomization issue), were both fixed. How the Level-Exp Bug works According to a message left on Discord by Matt (@sora10pls)(Mattyoukhana), depending on a species' experience growth rate, HOME applies an incorrect experience value to the Pokémon upon transfer, with only the Medium Fast experience group being affected. An example to look at would be Mythical or Legendary Pokémon. They are in the Slow experience group, and they got 0xFFFFFFFF written to their experience. As such, they appeared to be Level 1 or 100, due to how the device deals with the value of experience. (Pokémon data don't have Current Level as a data point in the data structure; it is instead derived by the experience stored in it) As such, it is dubbed the GO->HOME Level-Exp bug. A 'fix' on the user end As described by Matt, move the affected Pokémon into a compatible game, do not view the summary, and send it into a battle. The experience it should have would then be fixed by the game, and it will become a regular Level 100. Conclusion The prevailing theory is that when attempting to fix the XXS becoming random height issue, Pokémon HOME borked the code for handling experience values to match the GO Trainer's level, thus creating this secondary issue. It is currently unknown if HOME will revert or fix the levels of Pokémon that were already transferred. (Pokémon that were sent into HOME during the buggy period currently continue to have bugged levels in HOME) Additional info: Background for the XXS-Height randomization issue With the launch of HOME v3.0.0, Pokémon from previous games could be transferred to Scarlet & Violet. In Scarlet & Violet, if the size of a Pokémon is the smallest or the largest (in terms of scale), it qualifies for a Mini Mark or a Jumbo Mark respectively. Thus, players would want to transfer the XXS or XXL Pokémon from Pokémon GO and obtain these marks. In the initial weeks of HOME v3.0.0 launch, players have noticed that their XXS Pokémon from Pokémon GO were average sized when transferred to Scarlet & Violet, thus being unable to qualify for the Mini Mark. As it turns out, Pokémon HOME has been rerolling the Height and Weight values of any Pokémon that had 0 in both stats (explained in Route B on this page), and XXS Pokémon from Pokémon GO were caught in the crossfire. Files and contributors The files uploaded here are contributed by @theSLAYER and @sora10pls. They have been dumped in HOME format (PH2) and converted to PKX via PKHeX for usage with the games. The OT, TID, and SID has been changed for privacy purposes. As these files stand, they'll be similar to a player transferring a Pokémon from GO and leveling it up to 100. In some sense, the only 'special' copies would be the originals (those that have the GO stamp), with the bugged levels, in Pokémon HOME. It is also important to note that the bugged originals in HOME cannot be traded via HOME.
  21. There's no better way. You're probably triggering their system, when you send over multiple Pokemon with the same tracker. If you're sending over a Pokemon from the correct pair of origin games (let's say Origin game Violet, you're sending from Scarlet or Violet), you can wipe the HOME tracker. Else, you just gotta do it one by one.
  22. Not just the double post (which I removed for you ), but I've seen you ask this a few times. I was hoping someone would answer you but it didn't seem to happen
  23. Please stop asking the same thing again and again. I reckon if anyone knew they would have replied you.
×
×
  • Create New...