Jump to content

Kaphotics

Helpful Member
  • Posts

    7839
  • Joined

  • Last visited

  • Days Won

    451

Everything posted by Kaphotics

  1. [TABLE] [TR] [TD]0013[/TD] [TD]19E00[/TD] [TD]00000504[/TD] [TD]75EB2[/TD] [TD]Constant & Event Flags 19E78 - Ash Counter 0x1A0FC-0x1A27B - Event Bitflags (0x180 * 8) [/TD] [/TR] [/TABLE] 0x19E00-0x5400 = start end = start + 0x504 copy to [start] to replace [start-end] bytes. The wiki's offsets are shifted by 0x5400 (to reference the 1MB container saves, "main" starts at 0x5400).
  2. Just copy the entire block of data. Transplant the Constant & Event Flags block from one save to another with a hex editor, then resave with PKHeX.
  3. Latest commit now supports this if you hold ALT when exporting a save file. Thanks for the suggestion
  4. There's too many. Just copy someone's save file or even the Event Flags region.
  5. Implemented editing in latest commit. Behaves just like the Egg RNG seed editor, except it is disabled if there is no current GameSync ID (all zeroes).
  6. http://projectpokemon.org/forums/showthread.php?21828-Moving-Stationary-Pokemon-B-W&p=145246&viewfull=1#post145246 Regular movement permissions for the in-game NPCs for comparison
  7. Implemented property in the latest commit; should be accessible in a future commit. Thanks daxtsu!
  8. Hey I think it would be neat if people looked at the list of shortcuts before requesting features. (To see if it already exists) What do you guys think? Complete list of shortcuts and update history is available within program via Options->About.
  9. You can save it with whatever filename you want; PKHeX just suggests a name.
  10. Forms that aren't accessible in the Personal editor don't exist; nothing is hidden in that editor.
  11. Kaphotics

    pokédex editor

    This issue with Pokédex flags has been fixed for a few months (although after the latest release). Feel free to compile the latest version from the source code until a new stable version is posted There's a bunch of new experimental features in the current development cycle that have not been sufficiently tested.
  12. Better to use custom firmware (cfw) to edit the save file directly, install games/apps like the updated browser that is vulnerable.
  13. Changed to at least 2*31, no other restrictive logic.
  14. Maybe it's just 2 flawless IVs in all, not requiring HP to be flawless.
  15. Hm, multiple sources say it's 25 & 2*31 https://www.reddit.com/r/pokemon/comments/3j6jtw/psa_pikachu_cup_reward_now_available/ http://www.gamefaqs.com/boards/792673-pokemon-omega-ruby/72414595
  16. The one posted has an HP IV of 0xFD (instead of 0-31 or 0xFF or 0xFE); reading online a few sources say it also has 2 flawless IVs (maybe frozen 25 + 2 31's enforced). It seems that there's some special rule / flag that is unknown that determines whether or not it get X IVs flawless, and this 0xFD is new too. Maybe it's just if the HP IV is set certain things happen. If you have any insight or find other quirks, let me know It seems HP IV determines the IV logic: 0xFF = Truly Random IVs (if unset) 0xFE = 31 HP, 2 other random IVs 0xFD = 25 HP, 2 other random IVs Wonder if there's any other values (<0xFD for HPIV) that do special logic... Anyone want to try changing that in a hex editor and report back if anything fishy happens? Implemented 0xFD and tweaks in the latest commit.
  17. Fixed in the latest commit; also with that Tyranitar I've fixed PID setting as well. Thanks for reporting!
  18. Updated OP with latest version. 12-02-15: - Fixed: OWSE: Map Permission Dumping - Fixed: Tools: Thread tracking - Added: RSTE Expanding important teams to 6 Pokemon. - Added: RSTE Allow random Mega (default) formes. - Added: **WE: Arceus-Fairy to formes list.
  19. Committed a few fixes: Fixed not having 3 random flawless IVs by default. Fixed Fateful Encounter not being applied. Fixed the Memories not being set to the right memory type. Fixed the Friendship being set to only one Trainer. Thanks for reporting
  20. Yeah it's still a pretty rough conversion right now; it'll be massaged a bit as I test more wondercards (and memories etc). I'm not familiar with the exact logic required for all cases, so if you had a few examples I can try my best to match that end result.
  21. Of course. If they error out, then that data isn't present in the demo
  22. Fixed * 2 Thanks for reporting
  23. Fixed, thanks Find where that data is and how it should be edited; only then can it be possible to add it to the program.
  24. Fixed in latest commit. I went with an increment of +1 so that the first few gyms don't fluctuate that intensely. Thanks for reporting
×
×
  • Create New...