BlackShark

The plugin needs to be compiled from source for now, I'll publish a new release tomorrow (Mirage Island and WC3 Plugin will be updated tomorrow as well).

Save ingame normally and open your save file, save states are not supported as they are not valid save files. I guess you are playing on DeSmuME? In that case your save files should be in the Battery folder in the same directory where the exe is located.

This guide is for those who are interested in editing an actual trainer/berry e-Card to use with the real e-Reader. If you are capable of save editing or you are playing on an emulator it's probably easier to inject the trainer/berry into your save file directly. Requirements your custom Trainer (ECT) or Berry (ECB) of course (can be created with this tool) e-Reader dev tools (https://caitsith2.net/ereader/devtools.htm) e-Card headerfix tool headerfix.zip (source) a hex editor (like HxD) a raw e-Card which we will use as a base (English, Japanese) Editing the raw e-Card Decode your raw e-Card with nedcenc like this: nedcenc.exe -i card.raw -d -o card.bin Open the decoded card in your hex editor. Copy the header (the first 83 (0x53) bytes as seen above) and save them for later. Copy and save the VPK (starting at offset 0x53 with "vpk0") into a new file. The full VPK size can be found at offset 0x51. Keep in mind that this is written as little endian, which means if these two byte are "81 07" the actual size is 0x781 (from 0x53-0x7D3). The rest of the decoded card is just padding, you can ignore/delete it for now. You have saved the VPK into a new file, now decompress it with nevpk: nevpk.exe -i trainer.vpk -d -o trainer_decompressed.vpk Open the decompressed VPK in your hex editor. For trainers: navigate to offset 0xD50, that's where the actual trainer data (ECT) is located, it's 188 (0xBC) bytes. For berries: the data (ECB) is at offset 0x4EA, it's 530 (0x212) bytes. For trainers: replace the data from 0xD50-0xE0B with your custom trainer and save the file. For berries: replace the data from 0x4EA-0xA19 with your custom berry. Compress your edited VPK with nevpk: nevpk.exe -i mytrainer.vpk -c -o mytrainer_compressed.vpk Note the size of your new compressed VPK! Create a new file in your hex editor and paste the header you have saved earlier in step 3. Paste your compressed VPK right after the header at offset 0x53. Now fix the VPK size at 0x51 to match the new size. Remember to write it as little endian! Fix the size info at 0x26: in the image above the value is 0x020F0622 bit 9-23 is the same as your VPK size + 2 bits are counted from left to right starting with 0 the original VPK size is 0x781 + 2 = 0x783 or in bits 0000 0111 1000 0011 0x020F0622 in bits: 0000 0010 0000 1111 0000 0110 0010 0010 convert your new VPK size into bits replace the bits marked in red in the size info convert the size info value back into hexadecimal write it back to offset 0x26 Pad the card to a proper size of 2112 (0x840) bytes. You can fill the area after the VPK until 0x83F with FF. Fix the cards checksums by droping it on headerfix.exe and you are done! You are done! You can now encode your edited card back into a raw e-Card: nedcenc.exe -i custom.bin -e -o custom.raw You can use the dotcode printer from the devtools for printing, it can print dotcodes in raw or bmp format. Keep the DPI at 300, choose your card and your printer and print it! You could as well just convert your raw card into bmp (raw2bmp.exe -i card.raw -o card.bmp) and print that. So, I hope everything was clear enough, if there are still questions feel free to ask!

Those are both very outdated. You really should use PKHeX nowadays.

Just save the page and put it on your server. Check this guide https://projectpokemon.org/home/tutorials/save-editing/managing-3ds-saves/

I have no idea why you would need this but this site is still available: http://lunarcookies.github.io/loadcode.html#rsavin.bin http://lunarcookies.github.io/loadcode.html#rsavout.bin

ExtData is used store Battle Videos and downloaded rulesets for wireless battles.

With a modified siskin.tsd the missions will show up ingame. Idk where the data comes from, it probably gets written there during the download process. Now I need to find a save file that doesn't have any missions yet to test if the injected misiions are properly playable. Pokemon Ranger (JP).sav

@ajxpk nice work! Thank you very much! Ok, forget what I wrote previously. Only the first two chunks are static they contain the information about the other chunks. Save Info Chunk (512 bytes) 0x000-0x00B PKR-059 a00 0x00C seed 0x010 CRC16 over the next 492 bytes 0x014 time stamp 0x018 time stamp (see https://projectpokemon.org/home/forums/topic/45846-pokemon-ranger-save-file-encryption/?tab=comments#comment-265265) 0x01C always 0x000000A0 0x020-0x1FF chunk info entries Chunk Info Entry (48 bytes) 0x00 file name 0x1E number of copies 0x20 offset 0x24 data size 0x28 reserved space Each of the other chunks has a 24 byte header. Chunk 0x00 seed 0x04 CRC16 over the chunk data starting at 0x18 0x08 unknown 0x0C unknown 0x10 save counter 0x14 always 0x00000001 0x18-0x?? chunk data A small tool to decrypt/encrypt and fix checksums for Ranger saves (use with caution!): https://github.com/Bl4ckSh4rk/rangercrypt/releases/latest

Make sure your ROM is unmodified and turn off any cheats.

If you mean .gba files, no. PKHeX is a Save Editor, not a ROM Editor. It can edit save files (.sav) from GBA games though. Actually every Pokemon game from the main series from the 1st gen to the 8th gen is supported.

The issue is probably that your ExeFS folder is not named correctly. The expected name is just exefs, not ExtractedExeFS or anything else. To avoid any issues like this you should use the build-in tools in pk3DS to extract and rebuild your decrypted ROMs.

Sounds like you didn't update your checksums before saving the edited save file.

In that case you better use this

Is there any reason why you need to use PikaEdit? It is recommended to use PKHeX instead. 1.9.3 is the latest version.

Get the patch from the google drive link from the first post (RenegadePlatinumv130.zip). Then follow the instructions in the HowToPatch.pdf inside the .zip file.

I can confirm this. @Kaphotics Yancy and Curtis OTs should be swapped. The Pokemon for male players should get the female TradeOT while the ones for female players should get the male TradeOT.

Legality checks for Colosseum and XD are working just fine on the latest release. So why do you need a version that's over two years old? The legality checks might be inaccurate as that version is missing a lot of improvements/fixes that have been made since then.

You can get the latest development build of PKHeX which includes the latest commits from github from here. If you still want to build it from source, first make sure you have .NET desktop development installed in Visual Studio Installer. If you don't have it, install it then redownload the source.

SNA files are "snapshots" made by No$GBA, other emulators call them "save states", they save the current state of the game and are no valid save files. Your save file isn't proper as well. The proper size is 128KB. Yours seems to be compressed. To get proper save files in No$GBA there is an option called GBA Cartridge Backup Media, set this to FLASH 128KB Sanyo. Then open No$GBA.ini with a text editor, find SAV/SNA File Format and set this to Raw it is probably set to Compressed or something like that. Make a backup of your save file before doing any changes!

Just use PKHeX.

The item alone is not enough, you also need to set the Event Constant for Victini to either "Event" or "Battleable" (I don't know which one is correct but one of those should work). For event items it's always recommended to no inject them directly but instead get them via wondercards.

Check the readme in the download from the first post. It explains how to apply this patch to your ROM.

Check step 4 "To restore an edited save back to the cartridge, click "R" until the "Save Backup" section changes to "Save Restore"", you should then be able to select the save file you want to restore to the cart from the SD card.