Jump to content

theSLAYER

Administrator
  • Posts

    22826
  • Joined

  • Last visited

  • Days Won

    991

Everything posted by theSLAYER

  1. Version 1.0.16

    20005 downloads

    PKHeX plugin to check for valid PIDIV and other correlated stats for Overworld8 or Max Raid or Max Lair mons. Once the data is found, the selected row can be sent to PKHeX's viewer, without the user having to copy the data over manually. Other small features include: - Able to update Trainer ID/Secret ID in Searcher based on Save's details or Viewed Pokémon's details - Able to update Trainer ID/Secret ID in Searcher based on viewed Pokémon's details, whenever a different Pokémon is viewed - Able to update Gender Ratio filter (Max Raids/Max Lair searching only) based on the viewed Pokémon - The TSV box updates based on what the user inputs, or the data grabbed from save/viewer. - If a modified IV stat is 31, the Hyper Training Flag would be removed Spiritual successor of IV Searcher portion found here: https://projectpokemon.org/home/files/file/4447-gen-8-ow-shiny-pid-genner/ How to use Put the plugin into the plugins folder in your PKHeX directory, then access it from the Tools menu. Tutorial, under Searching for Particular IVs: https://projectpokemon.org/home/tutorials/save-editing/using-pkhex/pid-mismatch-origin-game-swsh-r114/ Note: Win 10 might block DLL files downloaded from the internet. In that case right click the plugin file, go to properties and check "unblock" (as seen here). [You may have to unblock, reblock, then unblock again to get it to work] Example of how to unblock: Support Sword and Shield. BDSP For help and bug reporting, go here. Credits Kaphotics for PKHeX, his documentation on Github, as well as other various functions found in PKHeX.Core and PKHeX.Drawing SkyLink98 with helping me figure out how to deal with implementing changes on PKHeX's viewer Leanny's Source code for Ability and Gender determination for raid stats from seed. Admiral Fish's Raid stats generation write-up. SciresM and his Roaming8b code write-up used by PKHeX.
  2. Yes, it is common knowledge that if a mon's level (even base level of the raid, before it gets scaled down after capture) is higher than the level your badge allows you to catch, it'll be caught as non-shiny.
  3. One thing you could try, is have 2 eggs in your party with 0 as hatch counter, then take 1 step, and only one should hatch, then immediately shift the 2nd (unhatched 0 hatch cycle) egg into the PC, then save the game, export the save, and see what value it is in PKHeX.
  4. If I'm not mistaken, the ones in the PC should not be genned to 0, but instead be genned to 1.. It could just be game behavior, not PKHeX behavior...
  5. @Parakoopa Defender seems to think it's a virus again, check the latest review on your download. You may wanna track down the line of code that makes the virus checkers think it's a virus. @BobbyKazami read the post above mine. You can also run through the source code that is on github to 'find the virus'. Virus checking programs once thought that my own innocent program was a virus, simply because I look for a particular file in the same directory, to be used as some kind of settings document..
  6. With ROM hacking, probably. If I recall correctly, the effects of the 2 "As one"s are hard written; they're not based on variable abilities. They're just made to look like it's combining 2 existing abilities together. If you're good enough at coding, you can make them appear as anything.
  7. How to encounter wanted max raid mons (change stars and randroll):
  8. I don't know what kind of hack you're using, but it's shiny locked. (this is viewing all the static encounters programmed into the game itself. You're arguing against game data) Besides, even if we account for some kind of glitch or error in the programming when it comes to this encounter, millions of people tried and couldn't get it to be shiny before you. In-game Rayquaza met in ORAS is shiny locked. Static Encounter Mismatch =>"The data on this file does not match known details of an existing static encounter" PKHeX is working as intended.
  9. If you imported the four blocks correctly, then just keep wishing pieces until it happens. Alternatively, use PKHeX’s raid button to change the raid. either way, once the blocks are imported right, this has nothing to do with block editing.. This isn’t a thread dedicated to troubleshooting user issues with raids not appearing.
  10. It’s probably fine for now. If the offsets you gave are accurate and static, then it should work. I’ll get to it once my PC troubles are over.
  11. Is it just me, or is that image for ants? Anyhow, pretty sure Rayquaza caught in ORAS is shiny locked.
  12. theSLAYER

    PKM Go Zarude

  13. Version .

    1792 downloads

    When players logged into Pokémon GO during the period of October 1st to October 10th (2021), they gain access to the special research that yields a Zarude upon completion. Players do not need to complete the research within the period. The special research was available to players to promote the then upcoming movie Pokémon M23: Secrets of the Jungle, which would have been aired on Netflix. For this file to be transferable across games without any stats oddities, you cannot modify any immutable values. Read here: Relevance of HOME tracker
  14. Any issues about "analysis not available for this Pokemon" relating to GO captures have been observed and reported.
  15. theSLAYER

    PKM Go Zarude

    @minx I'm trying to get one, to check if it can be transferred over.
  16. glad you got it working Out of curiosity, what was the size of the entire ROM dump when viewed in Hex editor? I wanna make a program that can pull out a save.
  17. Details for Index 87 of normal_encount and normal_encount_rigel1 and normal_encount_rigel2 (minor differences, in raid chance) Rewards for Index 87 of normal_encount and normal_encount_rigel1 and normal_encount_rigel2 (minor differences, in raid chance) Details for Index 85 of dai_encount Rewards for Index 85 of dai_encount
  18. Version .

    2007 downloads

    This is a Wild Area event held by Sword and Shield. This event gives players a chance to capture the Alolan Starters. An interesting note, is you could try to catch them with other types of Poké Balls, which couldn't be done previously. Only the files normal_encount, normal_encount_rigel1, normal_encount_rigel2, and dai_encount were updated to Index 87. To import these files into your save, use PKHeX's block importing function. Our tutorial should guide you through it. Our first post of this page contains some data relevant to the importing stage. There's info and some common questions regarding Wild Area Events here. To see other Wild Area Events, here.
  19. PKHeX applies an "released so stay in bag" filter to the bag. It's probably in some form of code. Just look through the various pages of the source.
  20. Indeed, Gen 1 have their own encoding. https://bulbapedia.bulbagarden.net/wiki/Character_encoding_(Generation_I) So you'll have to search for 86 80 91 98 Your legit save file? As in the save file from a none bootleg cart? I don't see why that would help. Probably shouldn't upload part of the bootleg ROM.
  21. Yup, the save size is truncated. The error was caused by your FTP, when transferring save to PC via FTP -> if you were using FileZilla, change the setting to use binary transfer mode instead of ascii. (Other FTPs probably have a similar setting.)
  22. I haven't. However based on what you're saying, it probably is in the ROM. You can't send it to us, but maybe if you know hex editing, maybe we can find data that is of some use. Let's use some known data as a pointer. What is the full (including actual capitalization) of your rival's name in your game? If in doubt, you can take a photo of the signboard in front of their house.
  23. glad you got it figured out!
  24. You're not supposed to see edits you made in EmuMMC on Sysnand. If you saw the edits previously, it happened by chance. It's unintended. Your sysnand and emummc happened to be 'linked'. Do you see what the problem is? It sounds like you're expecting behavior that is unintended. Booting into CFW Sysnand and restoring the save should have retained the changes, so I can only assume you didn't restore the edited save. Close PKHeX, then open a fresh window of PKHeX, then drag the edited save into it. Do you see the changes there?
×
×
  • Create New...