Jump to content

Kaphotics

Helpful Member
  • Posts

    7216
  • Joined

  • Last visited

  • Days Won

    357

Everything posted by Kaphotics

  1. It's the label shown underneath the 'criteria/action' dropdown. (in the example above, right underneath the "Set Equal To" is '0', which, indicates that the current value of _0x73 is 0 for the pkm currently loaded to tabs. If nothing shows up, then the pkm in tabs doesn't have that property. The "Byte" indicates the value type of the property (integer, byte, etc).
  2. Thanks for reporting, fixed in latest commit https://github.com/kwsch/PKHeX/commit/f351e9550fd68b310f539c96ce506a30ab03acb2
  3. Better to finish your ROM hack first, you're getting ahead of yourself. You'd eventually accomplish this in the cleanest way by using the plugin system and a new savefile class.
  4. TID and SID are internally as 16 bit numbers. You can modify the pkm in the main editor tabs to have the new tid/sid you want, then in the batch editor it will tell you the current value (stored format).
  5. structure: https://github.com/pret/pokeruby/blob/de2fe2cbbae599d9b336cb6762e3a03445cd5027/src/hall_of_fame.c#L39-L46 location: https://github.com/pret/pokeruby/blob/84c5825c8ecc9804313ec3b1a8dcc0271ee4c2cc/src/save.c#L77-L91 (last 2 chunks of the full save file [@ 2*0xE000], no backup present)
  6. Working as intended, PKHeX detects that the ribbon is hacked. Receiving one of those ribbons increases the original trainer affection by 20 for each contest it participates in. Max out the OT affection and you're done.
  7. Probably "Stat_Level" isn't changed since it is a party stat in all other formats. May be best to just have that as a 'gotcha' rather than accounting for it in the code?
  8. Thanks for reporting; fixed in latest commit https://github.com/kwsch/PKHeX/commit/fffc9436684808dfa6393557e21112eb7de65afe
  9. You'd need to export (save) the save file when you are done with your edits.
  10. Are you setting the CurrentLevel? Post the inductions you executed.
  11. Probably just need to differentiate the strings when they're initially loaded. (note to self).
  12. Double check that your 3ds is loading both the edited romfs AND the exefs. The exefs contains the actual move to be taught, and the romfs contains the text description.
  13. Set the OT_Memory, OT_TextVar, OT_Intensity, and OT_Feeling with the desired legal values?
  14. .AbilityNumber=$2 should work on all gen6+ save files.
  15. Read the changelog.
  16. I only had a few save files so I was only able to find one consistent location for 'party'-ish data. PBR saves aren't well documented outside of box data and a few other minor things. If the Party data is stored at a varied offset I'd rather not bother since it'd be a little too much effort for little gain (although, anyone can submit a pull request...)
  17. PKHeX does not support non-mainline series games. This includes ROM Hacks and unofficial game dumps.
  18. Bulbapedia has a list of values for each generation. eg https://bulbapedia.bulbagarden.net/wiki/List_of_locations_by_index_number_(Generation_VI) There's also a way to look certain values up using PKHeX: 1. Use the pkm editor to select the met location you want the value for 2. Open up the Batch Editor (ctrl-M) 3. Select the "Met_Location" from the dropdown entry field. 4. The Met Location property type (integer) and current value (from the pkm editor) are displayed in a label right above the large text box.
  19. 1) 3->4 overwrites the met location to Pal Park 4->5 overwrites the met location to transporter thus 3->4->5 ends up with transporter (overwritten on both transfers) 2) Anything with the PID type of "Pokewalker"; you can inspect the PID fields of any specimen and the middle 4 characters are always the same for a given OT (either 0000 or FFFF), due to how the PID creation works. 3) Dream World pkm have a met location of "Entree Forest", which is Met Location 75 in gen5 origin pkm: Pokémon Dream Radar is met location 30015.
  20. 1. Once it's transferred forwards, it loses its original met location data. PKHeX finds the first possible match, which in this case is Route 3. 2. See above 3. It doesn't matter, it's just listing somewhere the pkm may have originated from if the met data was overwritten. 4. Yes, for certain cases. Check the source code's usages of "CheckIdentifier.EC".
  21. Yeah you can probably extract them if you play with PKHeX's source code. ShadowInfo = new ShadowInfoTableXD(Data.Skip(Shadow).Take(subLength[7]).ToArray()); From ShadowInfo you can spit out each entry's Species and PID values.
  22. Should be fixed in the latest commit https://github.com/kwsch/PKHeX/commit/e82dcdb1240840b8a731dc5dfb9295002105ec6d Thanks for bringing this to our attention!
  23. Not anymore https://github.com/kwsch/PKHeX/commit/565a96db2a2bbdbf2368a061e032928bd5b34af6 Thanks for reporting !
  24. Should be good to go with the latest commit https://github.com/kwsch/PKHeX/commit/199512a9f76264e97c9523928c9226022352d243
×
×
  • Create New...