Jump to content

Kaphotics

Helpful Member
  • Posts

    7272
  • Joined

  • Last visited

  • Days Won

    362

Everything posted by Kaphotics

  1. This is defined by the ROM not the save file.
  2. Are you using the latest release? Please also indicate the game version of the save file you are trying to edit.
  3. PKHeX is a computer program, which cannot run on a 3DS. Extract your save file on your console them transfer it to a computer.
  4. No
  5. Thanks, fixed in latest commit https://github.com/kwsch/PKHeX/commit/b87f1fc8db1b84ff8bf5cd7d79e9b744a642139e Until the next release, just import while on the Main tab.
  6. A [...] move relearner [...] can teach a Pokémon any move that its species is able to learn at an earlier level (Generations II to VI) or at any level (Generation VII) [...]. http://bulbapedia.bulbagarden.net/wiki/Move_Reminder
  7. Bulk modifications: use the batch editor Design choices: There's pros and cons for the way things are done. Preserving stored values over derived values is preferred; in this case, preserving the current EXP is preferable. Redesign: PKHeX is open source using WinForms. Feel free to fork and re-skin yourself. Minor details: Boring research topics for near-useless features are not in my interests. For niche tools, community research is a requirement. Remember to consider time spent vs gain!
  8. lmao just use the batch editor 'changes were reverted' doesn't describe what is really the problem; you'd need to say what properties are not being set. Also, if the pkm were originally not paired with the save file (Current Trainer info does not match the save) then it'd get refreshed when properly setting back. You're better off just using the batch editor than automating user interactions.
  9. It's almost as if you can't have origin forme without having a specific item...
  10. Thanks; I've updated the program with a simplified method for calculating the checksum, and incorporated the offsets as you've listed
  11. Can't replicate the issue you're having. I'm posting a new version in a few hours; I'd suggest trying again with that when the time comes.
  12. Refer to the property type and value hints. It's a boolean (aka True/False)
  13. CRO edits are only possible if you're using custom firmware that patches CRO signature checks. Not having that will prevent you from playing the game (as it crashes on invalid signature).
  14. PKHeX automatically reloads the abilities; it's possible that you had somehow mangled the abilities (in HaX mode?). Try checking the legality of the pkm while still in the box (hold control->right click), and if necessary, re-set them back to the box with their correct abilities.
  15. Select the "Any" dropdown to see the properties for any pkm format; the "All" is for properties common to all formats (sometimes not a real property for certain formats, it's that way for programming convenience).
  16. The green background indicates the current handler. It can be switched by clicking on the groupbox that contains the desired current handler. PKHeX automatically fixes it for you unless you're doing something stupid like having the same OT/ID/SID across multiple savegames/generations.
  17. Does it really need an explanation? You have 3 choices. Give All Fashion... All Legal New Game Everything First is everything that is possible to obtain for your gender Second is everything that you start with on a new game (aka nothing) Third is absolutely everything for your gender, including dyes that cannot be obtained through legitimate play.
  18. HT_ OT_ SuperTrain ^ property prefixes. Use the current value & type hint when determining what to set it to.
  19. You can't hatch anything below level 5; the met level was 1 for both pkm. Transporter 3/4->5 sets the met level to the current level; can't go below 5.
  20. HP IVs are derived from the other 4 IVs (lowest bit of each). I've added the empty-inventory pouch case handling. Thanks for reporting
  21. It's homebrew.
  22. HGSS balls are not available in DPPt Non-pokeball on Gen4 egg (ball inheritance is g6+) Gen4 hatches are level 5 not 1
  23. Try using jksm instead, you likely restored an old save file thus the secure value doesn't match.
  24. If you read my reply, .NET 4.6 is required, not 4.0.
  25. Mega Stones are just unusable items; the mega evolution is triggered off of just holding an item ID. Mega Evolutions are to another pkm forme; in the past, people model swap to overwrite pkm that have formes, basically hijacking their mega evolutions. It's a dirty solution hence why no ROM hacks have no mega evolutions. I'm sure it's possible but I don't know if there's more things that need to be repointed besides the Personal Info indexes and the Model GARC master table. You'll have to use the dirty method to 'add' megas (which is really just replacing another pkm & its formes).
×
×
  • Create New...