Kaphotics
-
Posts
8071 -
Joined
-
Last visited
-
Days Won
493
Content Type
Profiles
Pokédex
Portal
Technical Documentation
Pages
Tutorials
Forums
Events
Downloads
Gallery
Blogs
Everything posted by Kaphotics
-
PKHeX has different modes for different games. If you do not have a save file loaded, then it loads up whatever your default version is (program settings). Which is likely BD/SP, which doesn't have any species > 493.
-
The game does not like an all zero trainer ID. The red boxes are invalid slots; they show the saved underground Pokemon data.
-
[Solved] clear sys flag 779 - Flag research of No Hat
Kaphotics replied to lattechan's topic in Saves - Editing Help
``` public const EvWork.SYSFLAG_INDEX SYS_GET_CAP = 779; public const EvWork.SYSFLAG_INDEX SYS_NO_CAP_MODEL = 780; ``` Try clearing 779. Note that the latest release has an issue with setting a custom System Flag (sets the checkbox state for regular event flags, not the system flag checkbox state), so double check that you have toggled it correctly. Development Build does not have the issue (fixed). -
It's the count of nonzero bytes in the save file region: 0x9CFD8-0x9D03B (100 bytes). The game stores the trainer IDs you've encountered, 1 byte per trainer.
-
Too vague. Event flags and giving items too early can result in the behavior, but not just by resaving within PKHeX.
-
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.
-
If only there was an encounter flag editor...
-
Use the site, or try using the encounter database within PKHeX (CTRL-N).
-
Use the encounter database; stop using "template" pk8 files when creating junk.
-
https://projectpokemon.org/home/forums/topic/59752-bulk-transfer-from-sword-and-shield-to-brilliant-diamond-and-shining-pearl/
-
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
-
BDSP cannot send or receive to other games.
-
Just set the event flags in PKHeX according to the latest commit if you want to unlock them via the Event Flag editor.
-
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.
-
Almost as if anything from the Underground has to have 1 relearn move. Working as intended. Use the encounter database.
-
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
-
Apply the patch to your copy of the game that you dumped from your physical copy & console. -
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.
-
pkNX: Nintendo Switch ROM Editor & Randomizer
Kaphotics replied to Kaphotics's topic in ROM - Switch Research and Development
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. -
Google it; not an issue with PKHeX but instead your operating system is misconfigured.
-
save states are not save files
- 1 reply
-
- 1
-
-
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.
- 1 reply
-
- 3
-
-
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.
