Jump to content

Kaphotics

Helpful Member
  • Posts

    7032
  • Joined

  • Last visited

  • Days Won

    336

Everything posted by Kaphotics

  1. CRO editing is not finished (there is more verification that has to be done). Hence why it is not uploaded to the OP.
  2. Reread the stickied thread. Homebrew Menu & Save Manager App X-20 thru X-22 Applet Version (the number after your Firmware Version, no new3DS) using Web Injection <=9.2.0 Firmware Console using SaveDataFiler JP Cart+JP System using Cyber Save Editor & Dongle
  3. Kaphotics

    PKHeX error

    Not being able to put things on your SD card is between you and your 3DS/SD card. Try using the FTP homebrew app if you cannot figure it out. This is not a PKHeX issue.
  4. Kaphotics

    PKHeX error

    Your SD Card is "write protected". Try flipping the switch on the side of the SD card. You can always export your save data to another folder on your computer.
  5. You have to set the wondercard back into the save file. Use the [<] button after you select which slot you want to inject it to.
  6. You cannot play edited ROMs with a Sky3DS. You cannot dump or decrypt ROMs with a Sky3DS. You can play edited ROMs on 9.2.0 firmware or below. There is no way to downgrade your firmware from above 9.3.0 to an exploitable firmware.
  7. It works only if you have a folder loaded. (it needs to know if it is ORAS or not)
  8. computer receives control inputs from 3DS, while the computer has an emulator for the game.
  9. TDVS is not available to the public yet; you will have to wait until it is released before information is known.
  10. gen3 pkm files are not gen4 pkm files. use pk2pk to transfer them.
  11. https://gbatemp.net/threads/tutorial-how-to-decrypt-3ds-roms-for-dummies.372653/
  12. Uploading the latest version which includes SMDH writing fix, mini repacking fix, in addition to other minor fixes/additions later tonight. Edit: Updated. Thanks Mixeli for the help with mini header crashing!
  13. You cannot use a vitamin if the Pokemon's EV stat for that vitamin is >= 100. It's a limit set by the game.
  14. The save file will be saved to your SD card, all you have to do is access your SD contents on your computer and load the "main" file into PKHeX. You'll be able to do all the edits that are possible (same as Cyber Saves), which includes Wondercard Injection and other save edits (map position).
  15. It would help if you could upload the [Details] to Pastebin so that I can see what is triggering the error. Be sure you are using the most up to date PKHeX; there was a new version posted today.I am unable to reproduce your error on my end. Try saving it to another place as the SD might be write protected (switch)?
  16. 8/8/15 - New Update: - Added: Korean Translation. Thanks cocoblue! - Added: Can now copy current moves to Relearn Moves by clicking on the Current Moves groupBox. - Fixed: Showdown Import made a little more flexible for non-exported sets (ie, user created with mistakes). Thanks Favna! - Fixed: Showdown Import now recogizes even more edge cases. Thanks Odaxis! - Fixed: Fill Dex now doesn't error out. Thanks ShaKage! - Fixed: Characteristics should now display properly for all cases. Thanks fcugqx! - Changed: The program now keeps track of the current box to mimic the ingame box system. Thanks codemonkey85! - Fixed: Saving the current box will no longer cause black screens when saving on the Party / Battle Box tab. Thanks RustInPeace!
  17. Did you save your savefile in PKHeX while looking at the Party/Battle Box Tab? Try re-saving with the latest commit. (it might also be worth finding out what exiting the PC ingame @ the battle box as the current view will save that byte at; open your save in HxD and go to that offset)
  18. No idea right now. I did check on my own bank of saves and I saw that 0x483F got altered when the file was loaded, but the checksum calculation worked correctly. That'd be what is causing the 0C block to show up as bad (still have to figure out what is causing that change). (edit: this won't have any bearing and was related to loading a save and showing the current box where something failed) Try transplanting data from other backups to see what area of the save is the troublemaker. Edit2: Was that 0x483F set to 0x1F? Might be the reason why (ie, last used the PC on a non1-31 box and exited, ie battle box?) I just committed a would-be fix so that the checksum error won't appear and the &0x1F is really using a signed byte instead (to indicate battle box). If that doesn't work, maybe keeping it below 0x1F might be the fix...
  19. Which is in the Box Name / Background / Unlock flag section. Did you make any modifications in the past to that section? I'll keep looking.. Might be worth trying to re-save the file, and comparing the differences.
  20. Please do a bunch of tests; edit on both variants of the program with the same changes to see if there's any byte difference on the output save file.
  21. Fixed the EV chopping in latest commit. Thanks for reporting!
×
×
  • Create New...