Jump to content

Kaphotics

Helpful Member
  • Posts

    7272
  • Joined

  • Last visited

  • Days Won

    362

Everything posted by Kaphotics

  1. =OT=Ash the reflective searching uses properties from the mystery gift class, not the pkm class
  2. Read the error message.
  3. Kaphotics

    PKHEX USUM

    When it's ready.
  4. You have to use the mono version and I think run it with wine.
  5. Will be hex editing only for now, I do plan to come up with something before the end of the year for this tho.
  6. it's ripping off the last few bytes used for the RTC footer -- it's probably a 1-2 lines of code fix but I'm preoccupied with the new stuff right now You can compare the two files in a hex editor at the bottom, just insert the RTC data at the end of the edited file.
  7. you've used cheats on the save file, which breaks any pattern used for save detection. you'll have to hold control when importing the save.
  8. https://github.com/kwsch/PKHeX/blob/3594d1af5cf86d946bdce1697a9c5e7a1894c995/PKHeX.Core/Resources/text/en/text_Memories_en.txt#L39-L108
  9. fixed: https://github.com/kwsch/PKHeX/commit/9af08763528307258d980c8c2710797422024964 thanks for reporting!
  10. thanks, fixed the checksum issue: https://github.com/kwsch/PKHeX/commit/d08bd25b4f8645c78726317a399ab7539bd2e730 will investigate string for eggs.
  11. I think the batch editor can use those indexes for the pkms you need to fix. In the text resource, Memories start at line 39 (memory 0) and are in ascending order if you'd prefer to fix manually. The legality checker is aimed to highlight flaws first, suggesting fixes second. Hooking up descriptive suggestion messages takes time and isn't really worth my time for every single flagged case
  12. works fine on the latest commits, please ignore the illegal message & wait for the next release https://github.com/kwsch/PKHeX/commit/e9cebf933c47bb49b299daa9f19c8b54106b7ce7
  13. Was fixed shortly after the last release; ignore the message until the next update https://github.com/kwsch/PKHeX/commit/5a09cd91220fb0026fc7cfc5c2e237f5b85c7b8a
  14. paging @evandixon , reading with file encoding issue https://github.com/kwsch/PKHeX/blob/b1641772e6354e2d579cf264d40ea512d547f049/PKHeX.Core/Util/DataUtil.cs#L119-L132 (I'll take a look at this later if nobody else does; critical)
  15. your PC has a corrupted font file for Courier New. https://blogs.msdn.microsoft.com/brandonturner/2009/03/31/courier-new-hates-me-font-courier-new-does-not-support-style-regular/ similar resolution: https://www.drivereasy.com/knowledge/fixed-font-verdana-does-not-support-style-regular-in-windows-7/
  16. Profanity filter tripping for the OT.
  17. it works as intended: white & transparent background, you can see PRESS START there. You can toggle a green-screen effect to see transparency areas by clicking in the image area:
  18. The colosseum issue has been fixed since then, was reported near the end of last month.
  19. are you using the latest commit?
  20. The interface has changed in the past two years since the reply was posted. To use the values as the user posted, convert from hex then divide by 2 to get the 'new' constant ID in the current UI.
  21. most encounters outside of wild encounters is manually entered now is added: https://github.com/kwsch/PKHeX/commit/d7300ce68fe04cdd83e55fce1130c33188b81728#diff-6af58c129f4b680caa6480467b2051b4R580 thanks for bringing this up
  22. No, it's more of a "Method" like those in the main games.
  23. Took awhile to get all the frames to line up, made a specialized routine to check them. https://github.com/kwsch/PKHeX/commit/495eb26740a52e78ef4e431a49ae8a2dbf3df48a Didn't use the already-made lock-unlock checks as those check to see if the locks pass for any origin seed; since we know the origin seed (derived from TID/SID), we can check directly.
  24. Added, thanks sora10pls https://github.com/kwsch/PKHeX/commit/008605c4ff33b07257c095895ca7a112e3a7efa9
×
×
  • Create New...