Kaphotics
-
Posts
7272 -
Joined
-
Last visited
-
Days Won
362
Content Type
Profiles
Pokédex
Portal
Technical Documentation
Pages
Tutorials
Forums
Events
Downloads
Gallery
Blogs
Everything posted by Kaphotics
-
tool Pokemon ROM Changer
Kaphotics replied to Kaphotics's topic in ROM - NDS Research and Development
Refer to the post directly above yours. They're hosted in our downloads section. -
Another issue with the Pal Park in Pokemon Platinum
Kaphotics replied to Meowdoleon's topic in PKHeX
Message shows it is matching to a static encounter, and that static encounter is a gift (which requires a standard Poké Ball). The best-match generator for gen3 has been altered to do the same collision detection (gift && ball not pokeball) as gen4: https://github.com/kwsch/PKHeX/commit/072f1ba83d965310b43ad916b3760e376f67f3f0#diff-611d41e12eb876fe009aa88436d0acf9R285 Should be resolved with the latest commits. -
Has been fixed since the last release. The next update is scheduled in 7 days.
-
Nothing has changed handling wise since it was first implemented; OP likely injected a hacked card or something which didn't trip the 'set const' routine.
-
Not 100% sure; could be an error in this site's Event Gallery. Looks like a fixed gift data is being uploaded (soon) @theSLAYER
-
The mystery gift data explicitly states that it's in a Cherish Ball.
-
It's pretty much confirmed that VC G/S will not have Korean games (no announcement for korea), thus is there really a need to have it incorporated to PKHeX? There'd be a lot of required things: Different character table (strings) Different item/species/etc names (strings) Prevention of loading to VC1/Gen7 games Mixing in a 3rd set of offsets Korean G/S would be locked to itself, so I don't see a need to support it in the multi-game editor (pkhex). Maybe a separate program / fork of PKHeX is best? Korean G/S is essentially a rom hack
-
They're hacked.
-
Already been reported & fixed: https://github.com/kwsch/PKHeX/commit/f3382bbd603652230508cc232379424080a0d9e3
-
-
Trading to RBY removes the met location data; since the PKM on crystal had met location data, it implies it was never traded back to RBY (as the met data still exists).
-
ROM related limitation.
-
Probably something preventing it from truly being a Happiny encounter (ie something only Chansey can have).
-
No
-
QR Injection still works for generation 6. You're generating QRs in the generation 7 format; load a generation 6 save file then generate the QR.
-
Use the latest release; you still need an exploitable browser version (-22).
-
a simple google search for "pkhex sun moon qr" will give you all the help you need.
-
Delete the PKHeX.Core.dll and executable, then extract the latest posted release.
-
It's a new addition; for gen6 it isn't behaving correctly like the gen7 variant. It's accidentally resetting other flags (unknown side effects), so you're probably best off reverting to the backup. The new version (posting maybe tomorrow) will have it fixed. Relevant fix: https://github.com/kwsch/PKHeX/commit/9864d84704a8e487c79c7b242cb6ef0c1f7d4755#diff-6477ac5c93a0823ea429ed4c67f8455dL434
-
Do you have an mgdb folder? Not sure how you snuck invalid mystery gift data into the program (I'm not able to replicate what you're experiencing).
-
fixed 1,4,5; would need to see pkms for 2 & 3 https://github.com/kwsch/PKHeX/commit/fb326500c1427774c34a346ec2b77ed49e1c7c97 thanks for the report
-
that umbreon is definitely hacked, xd/c pkm need to have a valid pidiv
-
Use the advanced search option with the same syntax as the batch editor? G7TID or whatever is a PK7 property.
-
A couple of odd things I noticed, possible bug?
Kaphotics replied to NekoSabrina's topic in Pokémon Legality
No, it's not a false illegal check result; Emerald has two pairs of Lati@s encounters. One has a fateful encounter, while the other does not. The one without is checked first, which fails because the PIDIV is invalid for that encounter. It then checks the other encounter (with fateful), which also fails the PIDIV check. Since there are no more possible static encounters, the program will continue on assuming that the final encounter was hacked, then checks the ancillary attributes. There is no correct encounter match, thus it keeps the last tested encounter to finish up with.
