Jump to content

Kaphotics

Helpful Member
  • Posts

    7957
  • Joined

  • Last visited

  • Days Won

    476

Everything posted by Kaphotics

  1. Hover over the Pokemon in your box/party to see the information that PKHeX infers. Not sure which encounter you are referring to, if one isn't displayed. If not displayed, there either isn't a detectable seed/correlation or it isn't computationally feasible to find (milliseconds vs minutes).
  2. Again, PokeFinder assumes you are using Sweet Scent to trigger, and does not check if you can trigger it manually via steps/turns.
  3. It's either not stored in the save file, or not documented (therefore nothing implemented in the program). Features only get added to the program once the game behavior/storage structure is documented.
  4. The internal flag names dump is at least 5MB, which 99.99% of users do not need. The dump is provided in the development discord channel.
  5. This is mentioned in the changelog/release notes circa 11/16: - - Crossovers are not currently handled for detecting location IDs. Generating from encounter template is 100% legal.
  6. I extended the file size to the correct size (4x'd) then ran it through the recovery program which does some filling in of blocks. projectpokemon/RecoverSaveGen3: Try and recover a Gen3 save file via c onsole app! Pokemon Fire red.sav
  7. Gen3 save files are 128KB, not 32KB. If that was the size you configured, then an insufficient amount of save data was retained, hence the error. Since you're missing 75% of the required save data, it's probably better to start over with a fresh save that is configured correctly.
  8. PKHeX is built to support unmodified game save files. PKHeX cannot know what changes you've made to the ROM. Since you are playing a ROM hack, the modifications by the patcher likely changed more than just bypassing trade evolutions. It probably mirrored ability slots (wrong, a single-ability species needs XX-00 not XX-XX). Changing the ability selection will cause the program to recalculate a PID, hence the second image. Copy the PID, then fix the ability index, then paste the original PID back.
  9. 1. No 2. I already gave you the exact implementation reference in the source code. 3. Best practice is to use the encounter database and not change anything you can't normally change in-game to preserve any RNG correlation it may have had at birth.
  10. For gen3/4 it rerolls to give a PID that matches the Nature, Ability, and Gender. For gen5, it rerolls to give a PID that matches the Gender (and ability?). For everything else, it's just random. PKHeX/PKHeX.Core/PKM/Util/EntityPID.cs at f816b06d97542516ab4a83df1bcb384b9825dc44 · kwsch/PKHeX
  11. It's the exact same process as you exporting your save file originally. Instead of exporting to a file, you import from a file.
  12. Nothing changed for Gen5 handling between now and the previous release. PKHeX will not complete the game for you.
  13. Export the save file from the editor when you are done making changes, and import your save file correctly back to your game. If you reopen the editor after making your changes, and the changes are still there, then it's not the program being wrong.
  14. You aren't restoring it to your console correctly. Data does not revert if you replace it entirely.
  15. Import your save file to your console correctly with homebrew. The fact that the modified data is there when you reopen your modified save should be evidence that PKHeX is in fact working
  16. Just tested, works fine. Be sure you are using the one from the navigation menu. https://discord.gg/66PzPgD
  17. Questionable no, illegal yes. You cannot upload it into HOME, as that is what error 10015 is. Can you be banned for it? It depends. The first post of this thread answers everything.
  18. https://bulbapedia.bulbagarden.net/wiki/Nickname#Changing_nicknames Read the first post of this thread how to randomize a PID.
  19. Even if you were able to import flags, there are a plethora of other savedata structures that are updated as you progress through the game. Simply importing flags/work values will not update anything else that would normally be updated as you play through the game. Save file editors are not a replacement for playing the game. Either use someone else's save file or play through the game yourself.
  20. Change the box number? If you want only Box 1 and Box 3 changed, run it first for Box 1, then run it again after changing it to only process Box 3.
  21. Not something users can access, and I'd rather not make it accessible -- see uploaded "fixed" save file. main
  22. Use $suggest or $suggestAll similar to the other properties that support suggestion requests
  23. Use the drop down in the batch editor.
  24. Use the drop-down inside the batch editor to see the list of properties. GroundTile Not sure why you're using the batch editor to modify stuff; is the Encounter Database not usable?
  25. No. The title says it was unobtainable, because the encounter could never be shiny.
×
×
  • Create New...