Jump to content

theSLAYER

Administrator
  • Posts

    22462
  • Joined

  • Last visited

  • Days Won

    925

Everything posted by theSLAYER

  1. 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.
  2. No reports about that a save from Emunand causing issues in Sysnand and HOME.
  3. Should be able to. I used to trade from hacked to unhacked, but granted that wasn’t Emunand.
  4. 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...
  5. 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
  6. Version .

    397 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.
  7. 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.
  8. 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
  9. Please stop asking the same thing again and again. I reckon if anyone knew they would have replied you.
  10. maybe it is the software version of the backup tool. trying using a different version
  11. @Juan Carlos Fernandez Piña I’m on windows 10 and I built it what’s the error you get thrown at you? Also, what the heck is this Those strings should not be in a save.. does not look like a save. Looks like stuff for Animal Crossing.
  12. It’s weird that you can’t launch the program. What OS are you running on?
  13. @Steinn transfer moves from Bank aren’t retained when they are sent into BDSP, PLA, SV. They’re changed to regular moves. If you check the Pokémon under Bank View on HOME mobile, you’ll see the event moves. But those moves aren’t used by those games (unless they can learn it) Anyway, moves on a Pokémon doesn’t dictate its event status most of the time. Having regular moves replace event moves aren’t uncommon. It’s more alarming if it had an event move from a different event.
  14. Don’t upload ROMs here, it is against our rules. To be sure, drop your .GBA file into my program and run it. Does it detect save for you to spit out?
  15. To be clear: what is the movie listed there vs what movie you think it is?
  16. I used a custom made plugin to dump all the HT/WT values in my save into a CSV file, which I then ported the data to my Excel file that already have graphing set-up. Yeah, ultimately it matched the triangular distribution curve. Testing with 50k mons for 95% confidence would be the gold standard, but that just takes way too much time. Even if the odds cannot be confirmed, at least the 'shape' of the distribute is.
  17. Few different options: - not have EmuNAND/EmuMMC. I use fusee.bin directly on TegraSMASH, so it loads directly into Atmosphere on SysNAND + CFW - use Hekate boot loader. It allows you to pick Clean or CFW, and Sys or Emu
  18. Version 1.0.1

    628 downloads

    This tool calculates a possible range for the Scalar Height used in Switch Core series games, from the rounded height value provided in Pokémon GO. This tool is still undergoing testing, so any constructive comments/feedback would be appreciated. Use at your own risk. This tool uses the logic in PKHeX.Core of Absolute Height -> Scalar Height. I just repurposed it and made the logic work for our purposes. Edited Note2: 0 in Height can safely be sent to HOME now.
  19. Background When Let's Go Pikachu & Let's Go Eevee launched, the games added back an old forsaken property to various Pokémon, namely sizes. To be specific, height and weight. While this property remains as a core part in data structure of Pokémon past Let's Go Pikachu & Let's Go Eevee, it will go unused in Sword & Shield and Brilliant Diamond & Shining Pearl (while the values for it are still generated and assigned by those games) Well, if we are being technical, height & weight will continue to go unused in Legends: Arceus and Scarlet & Violet, until HOME v3.0.0 makes it relevant to some degree. Size makes a more prominent impact in those games, as scale. One last bit of information to know, is that prior to HOME v3.0.0, any transfers from Bank do not have height & weight, and those Pokémon would be assigned 0 in both height & weight. So right now, 3 properties for size has been described: height, weight, and scale. Relevance In Scarlet & Violet, new marks were added to those games. Two of those marks are of note, as these two marks are different from the marks previously introduced: these two marks can be obtained by a Pokémon after it was caught. These two marks are known as the Mini Mark and the Jumbo Mark. The Mini Mark gets assigned to a Pokémon with 0 scale, and the Jumbo Mark gets assigned to a Pokémon with 255 in scale. The relevance here would be: scale didn't exist as a property before Legends: Arceus. In order to maintain compatibility of transfers between Sword & Shield, Brilliant Diamond & Shining Pearl and Legends: Arceus, HOME made is so that height gets duplicated into scale. As a result of this compatibility, any Pokémon that didn't already have scale attached to their data on HOME's end also get height duplicated into scale. With this, we have arrived at a method for transfers from previous games to acquire those two marks. Origin games: GO (via GO -> HOME direct transfer) The size depends on whether a Pokémon is XXL in GO. If they were XXL, then the height would be 255. It is believed that XXS would correlate to the height of 0, but currently GO transfers do not possess a height of 0. It is not known if it is a bug or intended. Edit 1: As of 17th June 2023, XXS can be sent to HOME and they retain height 0. Edit 2: Some XS and XL Pokémon actually qualify to be 0 or 255 when transferred. This tool helps give you a range based on the height shown in Pokémon GO. Origin games: GO (via GO -> GO Park in LGPE) XXL Pokémon in GO become 255 in height in Let's Go Pikachu & Let's Go Eevee. XXS Pokémon in GO become 0 in height in Let's Go Pikachu & Let's Go Eevee. This is limited by whether the GO species exists in Let's Go Pikachu & Let's Go Eevee. Since the height & weight values are already assigned in Let's Go Pikachu & Let's Go Eevee, there is no need for HOME to assign/reroll them. Edit 1: As of 17th June 2023, XXS can be sent to HOME and they retain height 0. Edit 2: Some XS and XL Pokémon actually qualify to be 0 or 255 when transferred. This tool helps give you a range based on the height shown in Pokémon GO. Origin games: Switch games The summary would be that the scale values are generated via triangular distribution, which would be 1/16,512 (for 0 or 255 in scale) for basic circumstances, without modifiers. Anubis has written up an easy to digest article here. (how those games generate the values aren't the point; this technical documentation category is about how HOME deals with it) I believe the same method of the generating the values were used for Height and Weight in the other games, as it would be a simple task to port over the mechanism without giving the whole thing much thought. Since the height & weight values are already assigned, there is no need for HOME to assign/reroll them. Origin games: Pre-Switch games (Route A) As I mentioned earlier: This means that any pre-Switch Origin Pokémon that enters HOME prior to v3.0.0, would have their height and weight set to 0. And when they enter Legends: Arceus from HOME prior to v3.0.0, their scale gets locked in to 0. And thus, when they enter Scarlet & Violet, they retain the scale of 0, and are eligible for the Mini Mark. It is important to note that with this method, for non-Switch origin Pokémon, they can only qualify for Mini Mark, not Jumbo Mark. Origin games: Pre-Switch games (Route B) One thing that HOME v3.0.0 set out to fix accomplish, was to assign and reroll height & weight values to any Pokémon that had both 0 height & weight values. The only exception to this (as seen in Route A) was any Pokémon that had visited Legends: Arceus (meaning they have a scale value initiated, even if it was 0). [Note: this fix technically had no 'real' repercussions to the user; they would not have been able to see height/weight values without hacking] So if you have a Pokémon with 0 height & 0 weight, but didn't visit Legends: Arceus prior to HOME v3.0.0, it will be assigned a random height & weight the next time it enters HOME. Now that we know that height & weight reroll exists, and that height gets duplicated into scale for Legends: Arceus and Scarlet & Violet, the question becomes: (a) is it possible to get 0 or 255 in height, and if so, (b) what are the odds to getting them? Based on Anubis' simple explanation of the triangular distribution Scarlet & Violet uses (read here), and me throwing stuff into HOME for it to reroll, I came up with this: I did a mini study, where I threw 18,600 Pokémon into HOME to have their height & weight rerolled. I plotted 2 graphs, one for height (blue dots), and one for weight (orange dots). x-axis are for the values (0 to 255), and y-axis for the number of hits I have come across after collecting all the height and weight rerolled. The black line follows Scarlet & Violet's triangular distribution of 1/16,512. There were adjusted to fit the study based on the number of samples I have (18,600). From the looks of it, the generation of height & weight follows the same triangular distribution used in Scarlet & Violet for scale, and so that answers question (b). As for question (a), I confirm that it is indeed possible to generate 0, as well as 255, in height. Here's a picture of my Mew getting the Jumbo Mark. If you're interested in my data, and the crappy plugin (only for SWSH) used to grab the HTWT data, it can be found here: HTWT.rar for the Excel file and plugin With this method, for non-Switch origin Pokémon, they can qualify for either Mini Mark or Jumbo Mark. Notable mentions: HOME gifts redeemed prior to v3.0.0 (origin games appears as Sword & Shield) Those gifts were distributed as height & weight being 0. If they have been transferred to Legends: Arceus prior to v3.0.0, they follow Route A, thus qualifying them for the Mini Mark. If not, they can also go Route B, and have a 1/16,512 chance to qualify for Mini Mark or Jumbo Mark. Alpha Pokémon in Legends: Arceus These Pokémon have their height, weight, and scale, maxed out at 255 each. This means they qualify for the Jumbo Mark when transferred into Scarlet & Violet. Former Titan Pokémon in Scarlet & Violet These Pokémon have their scale maxed out at 255 (as seen in the Iron Treads image at the start of the page). This means they qualify for the Jumbo Mark when transferred into Scarlet & Violet.
  20. Well, 255 only in Weight. Have yet to get 255 in Height yet. Nah that is still within odds. It could be 1/16512; think of it as getting a shiny Pokémon at the 500th encounter. That doesn't mean that shiny odds are not 1/4096, it just means that you got it under odds This would need to be tested multiple times to the full extent, to conclude the probability. (But I probably won't, cause it is mind numbing..) As of now, I'm just trying to see what distribution it forms, and whether 255 in Height is possible or stopped by HOME. edit: Edit yet again: Hopefully this page helps explain it all.
  21. Due to online save verification against shared saves being a thing for PLA, I urge everyone to not share their save. And also to you, OP, to not ask for PLA saves.
  22. Your post isn't an event contribution, thus post moved. Anyhow, I've got one in here. Make sure you read the description of the download page thoroughly
  23. Yeah I came to the same conclusion in my tweet. Either not possible or possibly triangular distribution. For triangular, need roughly 51 full boxes to be transferred. edit: @apri in case you're curious about my findings
×
×
  • Create New...