Jump to content

BlackShark

Contributor
  • Posts

    1701
  • Joined

  • Days Won

    102

Everything posted by BlackShark

  1. 1. https://support.microsoft.com/en-us/windows/use-snipping-tool-to-capture-screenshots-00246869-1843-655f-f220-97299b865f6b 2. You have a Gen 7 save file, the discussion above is about a Scarlet/Violet save. If you want all fashion items go into the Misc tab in the Trainer Info editor, there's a big button to unlock them all.
  2. You encounter Zygarde on level 70, not 25. There's more than just the location and level that could be wrong. Hold ctrl and click on the triangle to get a detailed analysis. You can use the Encounter Database (in Tools > Data) instead of trying to create the mon from scratch.
  3. This issue has already been fixed a month ago, update PKHeX. Also keep in mind that PKHeX does not support ROM hacks. They might work, depending on what has been changed.
  4. You can get the data from all Pokemon, items and other Mystery Gifts (Gen 1- 9) from the Event Gallery. Use PKHeX to import the data to your games. https://projectpokemon.org/home/files/category/2-event-gallery/ If something isn't in the gallery, you could check if it's in the Github repo. If it's not in there, it probably doesn't exist or hasn't been contributed yet. https://github.com/projectpokemon/EventsGallery/tree/master/Released
  5. There is a random value that has to match the higher half of one of your Pokemons PID (the last 4 characters you see in PKHeX). So here's what you could do: In the Event Constants you could edit the Mirage Island RND (High). Keep in mind that the values in the Event Constants are shown as decimal while the PID is hexadecimal. You have to convert it. In this case 2670 converted to decimal is 9840, so I would have to set Mirage Island RND (High) to 9840. Alternatively there's a PKHeX plugin that simplifies the process a bit. It shows if you already have a Pokemon with a matching PID somewhere. If you don't have one, simply change the seed value to match a PID. In this case both valus are hexadecimal so you won't have to convert.
  6. This save can't be revived, there is nothing to decrypt. If you open that save in a hex editor you will see that the file is mostly empty and there's only 32 bytes of data.
  7. If you are able to use Action Replay codes you also have access to your save file and you could as well just use PKHeX instead, which is more recommended and safer to use because it doesn't mess up your save. Just open your save and remove the TM.
  8. Whatever this is is not a valid save file. Looks more like a file filled with garbage and it's more than twice as large as it should be. How did you get it?
  9. 359 is Altarias internal species ID. The internal order does not match the national dex order as you can see in this table: https://bulbapedia.bulbagarden.net/wiki/List_of_Pokémon_by_index_number_in_Generation_III You could do what PKHeX does and add/subtract the difference between the internal and actual IDs: https://github.com/kwsch/PKHeX/blob/27b552db134b93015b1641ecdca3bc111b7d0016/PKHeX.Core/PKM/Util/Conversion/SpeciesConverter.cs#L30
  10. There is no "pkmdb" file. I'm not sure what exactly you are looking for, but if it doesn't exist yet, you can create a "pkmdb" folder right next to your PKHeX.exe. In this folder you can put individual Pokemon files which will then appear in Tools > Data > PKM Database. The PKM Database will also show all Pokemon from the current loaded save file as well as from backups (if enabled in the EntityDb settings). There are hundreds of user contributed PKM files that you could put into that folder. https://projectpokemon.org/home/files/category/196-user-contributed-pkm-files/
  11. You should use the .sav file, but you have to save ingame normally as you would on your console. Save states done from the emulator menu don't write to the .sav file.
  12. There are no Pokemon in your save file. If you want to edit your save don't use save states. Also keep in mind that PKHeX does not support ROM hacks. Some hacks might work, depending on what has been changed.
  13. The error tells your what is wrong: Close your emulator or save dumper or whatever other application that might access your save file currently.
  14. BlackShark

    Error

    Install the latest version of PKHeX from the link below. Remove any DLL files from previous PKHeX installations. Only keep PKHeX.exe and cfg.json. Or just put the new version into a new clean folder. Make sure PKHeX is corectly extracted from the zip archive, don't try to run it from inside. Also put it somewhere local on your PC, don't put it on OneDrive or any other cloud drive.
  15. Only for BW. B2W2 were not released when this one was distributed.
  16. Already fixed, update the plugin.
  17. No, you would need to create a ROM hack for that.
  18. It's hard to tell without seeing the file. Make sure that the file has exactly 128 kB, check if GB Operator has a setting to export the proper file size.
  19. Use this list https://github.com/kwsch/PKHeX/blob/master/PKHeX.Core/Resources/text/other/en/text_Moves_en.txt Move ID is line number - 1.
  20. The save file has no progress. If you are on an emulator, don't use save states and save ingame normally as you would on your console.
  21. First make sure to set the modified Pokemon back to the slot. Also make sure to import the correct save back to your console/emulator (not any backup file) and (if on emulator) load the game normally, don't try to load a save state.
  22. Saves can have different formats and file extensions depending on the game. ".sav" was mainly used for save files from Gen 1 - 5, on the 3DS they where simply called "main" without an extension at all. The Switch uses "SaveData.bin" and "Backup.bin", the first is your current save while the latter is the backup used by the console incase the current save is corrupt. Just look how JKSV exports your saves from your Switch, you will see they look exactly like this. You should open the SaveData.bin, if PKHeX can't read it there's no data inside. Save ingame normally and stop using save states, then PKHeX will be able to read the file (assuming it is not a ROM hack that has modified how save data is stored).
  23. .Language=1 .IsNicknamed=false
×
×
  • Create New...