Jump to content

theSLAYER

Administrator
  • Posts

    22400
  • Joined

  • Last visited

  • Days Won

    908

Everything posted by theSLAYER

  1. @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?
  2. 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.
  3. I can’t remember, but for gifts it’s either preset or assigned randomly.
  4. 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
  5. 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)
  6. 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..
  7. 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
  8. 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
  9. 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.
  10. 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.
  11. You sure said it. There’s many topics about the same issue.
  12. 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?
  13. There’s always information to check and collate. No ETA. Wait patiently.
  14. PKHeX hasn’t been updated to deal with saves from the latest SV update. We’re aware of the issue; it happens whenever the game updates and changes the save’s structure. Please wait patiently. No ETA.
  15. You can run ROM hacks. But you’re gonna need to find them, patch them yourself, and perform the required installation
  16. If I recall correctly, without a 3DS + the Tretta game, there’s no other way to use them.
  17. Why are you copy pasting the entire post from Reddit?
  18. You can get Custom firmware on the Switch, but yeah if you don’t have a Switch it’s fine too. Just saying.
  19. I meant move the Pokemon onto the Switch, basically
×
×
  • Create New...