Kaphotics
-
Posts
7843 -
Joined
-
Last visited
-
Days Won
451
Content Type
Profiles
Pokédex
Portal
Technical Documentation
Pages
Tutorials
Forums
Events
Downloads
Gallery
Blogs
Everything posted by Kaphotics
-
So what's the verdict for this topic?
-
First thing IIRC
-
Shadow Lock checks were recently added. We didn't find any edge cases, but this may be one. Basically the game generates the non-shadow mons and shadow mons; they're forced to certain Nature/Gender/non-shininess, so the PID generation loops until a valid one is found. PKHeX probably isn't finishing the final verification to the OT -- I suspect that the NPC got a shiny reroll which throws things off a little. @Admiral_Fish if you're at all curious about this
-
I think instead of it being version specific as previously thought: It's likely OT gender specific (inverted player gender)? Since player OT is never saved to the data, it means either PID encounter is not version specific. new EncounterTradePID { Species = 213, Ability = 2, TID = 04336, SID = 00001, OTGender = 0, Gender = 0, IVs = new[] {15,20,15,20,20,20}, PID = 0x000214D7, Level = 20, Location = 130, Moves = new[]{132,117,227,219}, Version = GameVersion.HG },// Kirk's Shuckle new EncounterTradePID { Species = 213, Ability = 2, TID = 04336, SID = 00001, OTGender = 0, Gender = 1, IVs = new[] {15,20,15,20,20,20}, PID = 0x00020003, Level = 20, Location = 130, Moves = new[]{132,117,227,219}, Version = GameVersion.SS },// Kirk's Shuckle Try removing the Version restriction at the end, recompile, and it should work?
-
See here for Emerald overworld object flags: (1000) https://github.com/pret/pokeemerald/blob/b1b97c1da9f8190ef3d145acf30eb1708f50e3f3/include/constants/flags.h#L933-L1104 (500) https://github.com/pret/pokeemerald/blob/b1b97c1da9f8190ef3d145acf30eb1708f50e3f3/include/constants/flags.h#L516-L629 R/S: (1000) https://github.com/pret/pokeruby/blob/9d62ad060b05848a0cad1f09881c3863596455fd/include/constants/flags.h#L614-L749 (600) https://github.com/pret/pokeruby/blob/9d62ad060b05848a0cad1f09881c3863596455fd/include/constants/flags.h#L258-L357 Should be obvious that they chunk everything up, and start at nice round numbers
-
Thanks, should be good now with the latest commit https://github.com/kwsch/PKHeX/commit/ed3699fbb45b71c723e443eb96b3df3f3cb42f0e
-
@theSLAYER nice find Fixed! https://github.com/kwsch/PKHeX/commit/a3e7c4837e8b837236c1cff8db0f12d8d17b3d51 -
That's fine, but be sure to put the species=Haunter ones in the Unreleased folder
-
PKHeX uses simulated wondercards for these local trade events. The events gallery should instead change the faked data so that it's distributed as a Gengar instead (since there's no way to end up with Haunter after the trade is over). @Sabresite https://github.com/projectpokemon/EventsGallery/commit/f92d5a7a4828376af3f9d013501a513da636bb75
-
Refer to our event database, which lists that event as having its hidden ability. Pretty sure Serebii's site is wrong as bulbapedia also lists it as having its hidden ability.
-
And then when you trade it back to Colo/XD, it will show "MONTE L". I don't think it's absolutely necessary to add edge case handling for this. Colo did not have a legality check of this caliber. Maybe I can do something about it... edit: done, should be Legal now https://github.com/kwsch/PKHeX/commit/93af3e61b7fc12f9d010c7071279107841505359
-
Gen 3 (pk3) through Gen5 have a max OT Name length of 7
-
You have an outdated build of RNG Reporter. Recent builds (and pokefinder) list that PIDIV frame as Slot 1, not Slot 2. https://gyazo.com/e58393c0e696ea29f4593fe6ce6cfc35 Working as intended -
PKHeX's frame detection isn't perfect yet, hence the flagging as fishy if it can't positively verify it. haven't touched it for 10 months: https://github.com/kwsch/PKHeX/commit/3d7b2a2b29664428d53d8ef4e337f35e172a1eae#diff-0b0337837f9d5dc29e00fdcd5c73d009R50 probably not going to take another look at it for a while
-
Neat fact I'll see what I can add rule-wise; I assume this also applies to the fullwidth numbers on the non-latin keyboards. edit: added! thanks for bringing this up
- 1 reply
-
- 2
-
-
I'm not going to spend my time curating the list of possible characters. It doesn't require knowledge of PKHeX or the language it's programmed in. Software programs cannot be fed an image or guidelines; things have to be explicit. The program does not have futuristic artificial intelligence to comprehend a nonspecific input, thus requires a human to manually give it the precise list of available characters.
-
Likely working as intended; you probably don't have any relearn moves set, which doesn't match a bred pkm but instead the gift eevee egg which doesn't have the hidden ability.
-
Needs to be more explicit than "x language allows for latin characters"; instead needs to be literally a list of every single character (abcdefghijklmnopqrstuvwxyzetc) list for every single language/generation
-
Sure I'll add something. But you'll have to give me the precise list of allowed characters for every single language, with separate tables for each generation.
-
If the box storage wasn't already enabled, PKHeX won't enable it automatically. Nobody has figured out how to turn it on.
-
Was originally added as met location 104 https://github.com/kwsch/PKHeX/commit/afde4514e283acb88c89b9f9c19c7d5138d7ce6e#diff-83a32d69355a64376bc77bd07e338a33R446 I have another save file that uses met location 110 (like this one) so I assume it was originally a copypaste assumption from Sudowoodo. Done, changed by: https://github.com/kwsch/PKHeX/commit/03a05364abeb000ca4cea345631a8fa6396ad7ea
-
Updated with the changed encounter type. -
Party stats are not saved when stored in the box; the game tries to save as much space as possible. IVs are 5 bits each (2^5, 0-31). Can't go any higher. EVs are 8 bits each (2^8, 0-255). Recent games prevent them from increasing past 252. Typing is determined by the ROM's Personal data. You'd have to edit the ROM instead of the save file.
-
Offset for FRLG should be Block1+0xEE0, not Block2+0x000 PKHeX's current setup for gen3 saves doesn't work for split-chunk operations, so don't expect it to work for flags >1280 (read the recent commit message). I need to figure out how to rework some logic... Edit: fixed with some workaround, should be all good now
