Jump to content

Kaphotics

Helpful Member
  • Posts

    7053
  • Joined

  • Last visited

  • Days Won

    339

Everything posted by Kaphotics

  1. Cosmetic edits that have no impact on gameplay is not something the developers are really interested in. It's not implemented, and usually depends on the community to figure out where that is before it is implemented in the program.
  2. If only there was an encounter flag editor...
  3. Use the site, or try using the encounter database within PKHeX (CTRL-N).
  4. Use the encounter database; stop using "template" pk8 files when creating junk.
  5. https://projectpokemon.org/home/forums/topic/59752-bulk-transfer-from-sword-and-shield-to-brilliant-diamond-and-shining-pearl/
  6. Don't nest PKHeX and its stuff in too deep of a folder. >> System.IO.PathTooLongException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters. Should be self-explanatory
  7. Just set the event flags in PKHeX according to the latest commit if you want to unlock them via the Event Flag editor.
  8. Use the encounter database when creating something from scratch, as PKHeX will fill in most details for you. If no encounter exists, then anything you try to make for that will be illegal anyway.
  9. Almost as if anything from the Underground has to have 1 relearn move. Working as intended. Use the encounter database.
  10. Correct, Darkrai from platinum is not a fateful encounter while shaymin is. https://github.com/kwsch/PKHeX/blob/5cff79f382c74ced01f0af60572717303ea18014/PKHeX.Core/Legality/Encounters/Data/Encounters4.cs#L260
  11. Apply the patch to your copy of the game that you dumped from your physical copy & console.
  12. PKHeX emulates official transfer methods. If a hypothetical transfer method does not exist (Example: SwSh to Ruby) then it will indicate it cannot convert between those formats. A setting is provided to disregard that restriction, but the conversion logic instead tries to copy as many values as possible. Mileage may vary.
  13. Kaphotics

    lukario06

    play it on your 3DS
  14. Probably a separate program. We're ramping down the datamining, and evaluating our options for how we want the long-lived user-friendly programs to operate. Likely will have some similarities to pkNX so we can reuse code (smart randomizers) easily.
  15. Google it; not an issue with PKHeX but instead your operating system is misconfigured.
  16. save states are not save files
  17. 1. Nobody has serialized the Language/Region restriction rules into something PKHeX can understand. It doesn't check for that at this time. 2. Memory feeling was hotfixed a few hours after the last release. New legality checks narrowed what was actually legal, but code still generated unrestricted values.
  18. PKHeX is open source. ROM Hack creators can change the source code to support whatever hack they like. Not only are there many ROM Hacks, but there are many ways in which the hacks change the game which is inconsistent with mainline logic. PKHeX will never support ROM Hacks; any observed support is just a coincidence that the hack didn't change enough from the vanilla game to break the program.
  19. Plugins having errors is outside the scope of PKHeX. Go ask the plugin author, not here.
  20. https://github.com/kwsch/PKHeX/commit/40031fd94d23d83ae3a2c6bb0ee137b0c6c59e95
  21. Set the trainer details for linked save file in the corresponding editor window, so the game knows it has been linked and allows the box.
  22. Added as a setting; default is true so it'll auto-max the IVs instead of the old behavior. https://github.com/kwsch/PKHeX/commit/77d1a990cd4af2ebadb66960b70f61109c5aa990
  23. Even for gen3+, the changing of Hidden power only mutates the IV bits that determine the type; they don't change the power value. For both gen3+ and gen2, you can get a max power arrangement by first maxing the IVs (shortcut is to control click the Randomize IVs button) then change the IVs after. Changing the behavior from only-mutate-type to mutate-type-and-max-power would remove the ability to change just the type. Plus, there's implications for gender in gen2. If you want max power, just max the IVs and change the type after.
  24. done https://github.com/kwsch/PKHeX/commit/640cb3bad10c568462071adf236fd73e26531b99
×
×
  • Create New...