Jump to content

SciresM

Innovator
  • Posts

    214
  • Joined

  • Last visited

Everything posted by SciresM

  1. Heh, it is -- byte-for-byte identical.
  2. Can confirm this QR is identical to the one I got last week.
  3. I would love a PM of your US code -- I want to see if the memecrypto'd data is identical to EUR
  4. You don't understand the memekey system -- they have an RSA private key with the singular purpose of signing the magearna codes. The codepath taken depends on the memekey index, found after the POKE magic -- in this case, index 9 is reserved for I choose you cap pikachu (it was a reserved, error path in Sun/Moon). Also, the species field gets used to decide what to display in the scan window, so they have to overwrite it.
  5. No. They're game ID bitmasks, among other things. First byte FF = Sun, Moon, US, UM -- FC = US, UM. Also if it's like the magearna event the pikachu species and forms will get overridden by the game's parsing code regardless of what's in the QR anyway >.> (Magearna QR codepath does if (species != magearna) { species = magearna; }) Last 8 bytes are SHA1(first 0x58) but that's standard memecrypto.
  6. It has not been posted anywhere -- I was asked by the person who sent me it not to share it publically yet.
  7. Yep -- once it's usable I can post the cleaned up EU/US code, too.
  8. We already have a JP code from the JP movie.
  9. Pretty sure you should be able to just swap the entries around if you're using a CFW that has RO's hash check patched. Pretty sure luma does this by default? Also you can replace the CRO pretty readily with luma's layeredFS thing nowadays.
  10. According to the list of big preorder bonuses on the Japanese USUM website, it looks like pre-ordering at certain retailers (7-11?) will get you a serial code for a big malasada and a fresh water. Relevant text: "どうぐシリアルコード(おおきいマラサダ・おいしいみず)(『ウルトラサン・ウルトラムーン』のいずれか購入)".
  11. I am pretty sure it's possible. Also..."compile it using a compiler" -- this is....pretty irrelevant to the process of making a tool. The compiler is literally an afterthought, as is the IDE used to write it. The code itself is all that you should really consider. (And PKHeX already has C-Gear code, I think, as I said.)
  12. Pretty sure PKHeX supports C-Gear stuff nowadays, doesn't it? (Also, not sure why the IDE matters, or why we'd not just use VS..)
  13. wc7full for the new saori machamp event, courtesy of nintendo's servers. 0219_saori_PC_MYS_JP_J_1484912559.wc7full
  14. Or, we can get the wondercard straight from the horse's mouth (or the BOSS servers, as it were). present_n_0__1484650169.wc7full
  15. https://github.com/kwsch/PKHeX/commit/fda84ae9921afcae2c448249cbf382a774dcc803 PKHeX now displays the relevant metadata.
  16. SciresM

    SOS Encounter

    Should be fixed in the latest commit.
  17. Magearna's event is not a wondercard, there's nothing to extract -- it's actually a hardcoded in-game event. Here're some QR codes, though: Legitimate US QR code: Legitimate JP QR code: Legitimate EU/AU QR code:
  18. Latest PKHeX supports activating the event/reactivating it if you've already received Magearna.
  19. PKHex's sun/moon support already includes support for Gen VII mystery gifts.
  20. I added support for editing Battle Revolution save files to PKHeX last week.
  21. To be honest: With Rhydon, I explicitly did not support Gen I saves that had been modified via the use of glitches/out-of-bounds IDs. I do not think PKHeX should make any attempt to defend against user-corrupted saves in the specific case of Gen I/II (Gen VI/VII are a different story, of course). If using arbitrary code execution will cause errors like this, I don't think PKHeX has any obligation to resolve those errors -- the user can use arbitrary code execution to unscrew their save first.
  22. New save files are largely uninitialized -- PKHeX can't recognize them because of that. PKHeX can only recognize save files that have been saved at least twice (ideally with the system being powered down between saves, though we're unsure if that's necessary).
  23. Apparently I never posted the cleaned up QR I made:
  24. ...Not sure why you were editing a completely fresh save of Crystal with the MC named "GOLD", but support has been pushed to the master branch of PKHeX. Was, as I expected, a save file size issue. And I don't remember you doing that or my ever feeling pressured, so I wouldn't worry about it.
  25. It *should* be ready. Send me your save file and I'll see about getting it supported? Probably it's a weird file size.
×
×
  • Create New...