chnapy

Hi, I just released PKVault 1.2.0 including Pokemon Legends Z-A support. Note: this support is based on PKHeX 25.11.30, so any issue present in this PKHeX version will be present in PKVault until any update. You can also find minor features, and multiple bug fixes (reported here or on github): Features Log files are now generated in logs/ folder. Consider sharing them with every bug report ! Allow saves paths from other drives ("E:/toto") and network ("\\192.168.1.12/toto") Add alpha icon Bug fixes Fix Alcremie forms display Fix Finizen specific evolve condition Fix crash on some GB saves because of specific legality issues Fix crash with lot of save files Use specific Lugia shadow sprite from Pokemon XD Update pkm ID generation to limit ID collisions Please report any bug or issues, with generated log files. Next feature update is still expected to be dedicated on box management.

@anticristian5 thanks for the report. Issues about Alcremie & shadow Lugia will be fixed in next update, release in few days. I haven't be able to reproduce bugs about totem & noble pokemons, they are rendering well on my side. If it's in Pokedex ensure you've clicked "show forms" buttons. Consider sharing your saves otherwise. Thanks for your feature suggestions, most of them are planned. Note that about "ability to have more than one save file for the same game", it's already allowed, you just cannot use duplicated saves with same ID (aka. copy/pasted file). @Vladcik add pk files directly is planned. It's possible to create multiple pkm versions, one for each generation. But you cannot use multiple of them in saves at once because it would be way too complex to synchronize them. You cannot move shadow pokemon from save to pkvault storage because shadow state cannot be stored in .pk files. So you have to purify the pkm before (from game or using PKHeX).

@EmeSet thanks for your report, I just made an hotfix release (1.1.4), this issue is not present anymore. Next update (1.2) is dedicated to Legend Z-A support and is estimated for the end of the month.

Hi, thanks for all your feedbacks, I don't always reply but I take all your suggestions into account.

I made a small update (v1.1.3) for a specific important bug causing app crash on first launch (+ some minor bug fixes). @GoatLord I don't have long-term plan for now, this app is still very young & in construction. PKVault is open-sourced so in future I guess anyone could participate to its development, but I think it's too soon for that.

@GoatLord you don't have to download anything except the app itself. Can you please provide a screenshot of the app with the error visible. Also please provide save files of related games. And finally please precise the version of the app including build ID, you can find it in Settings page (top-right).

This app is working 100% offline, there is no use of any external web app. Mentions of web app in file description is because technically this app was made as a web app with a frontend and backend. Desktop app is using the backend, and Microsoft WebView2 to render the frontend. This is why you have this WebView folder created. The file PKVault.exe is usable as-is, there is no other dependencies, except NET9 (same for PKHeX) and Microsoft WebView2 (which is already present in all common Windows OS). If you have specific issues please share screenshots, or copy/paste errors.

@l3rittany Most app logic is around the use of PKHeX.Core which is usable as a C# package. This required a lot of time digging in PKHeX code understanding how the tool works since there is no documentation at all. So most PKVault logic is just using PKHeX actions on saves. When you're transfering pkm from save to PKVault storage, pk file is generated (in storage/ dir) and its metadata is stored in json files (in db/ dir). Create pkm version, for instance generation 3 from generation 7, makes a stored copy of source pkm file and try to convert it to given generation using PKHeX tool & more specific actions. Beyond that, I'm using Pokeapi for embedded data (for what is not given by PKHeX) & sprites.

Yes, I try to follow each PKHeX version (currently in 25.09.25). Last PKHeX version (25.10.25) is quite specific since it includes Z-A partial support. I skip this version since its support seems to come with multiple issues which may affect app stability. Next version (25.11.25) will probably include several fixes, so I prefer wait this one. @Vladcik reports can be done here or on github, it doesn't matter to me.

Thanks for all your feedbacks, I'm keeping all your suggestions. I published a new version 1.1.2 focused on bug fixes (including yours @Vladcik), perf improvements & a significant reduced app size (from ~180MB to 58MB). I'll try to work on storage box management/layout rework for next update.

@Vladcik what anti-virus are you using ? It would help me if you can send me screenshot or more details about this. About your issue with sprites it should be fixed with last app version since now the app is using local spritesheets and do not depend on pokeapi anymore. To check if your app is up-to-date, in settings you can see "Build ID" on top-right, its value should be for 1.1.1: "39bf8b0c-66ed-4047-aa05-08f2ec06db5a". @QuArtzX_ thanks for your message. For your issue I opened your save with PKHeX and the result is the same, boxes are all empty. Since PKVault is using PKHeX under the hood I cannot do anything about that. If you consider this is a PKHeX issue you may contact them. About your idea on the pokedex this is something I have to think for, but I keep your suggestion in mind.

Hi, I published a fix version 1.1.1 related to the bug you're describing @Vladcik, so data loss with pkm duplicates in this specific case should not happen anymore. Note that sometimes different pkms can be considered as clones, even when it's not the case, especially with old generations like 1 & 2. You can see more why in this answer. Note that I'll try to improve this behavior in the future. For the rest thanks for your ideas. If you want you can of source DM me and/or write part of your messages in french if it's easier for you.

Thanks @Vladcik, of course feel free to suggest any improvements.

@Alberto14 please can you share your saves so I can see the issue

Hi, I published a new version 1.1.0 with some big changes. First, settings saves paths input is fully remade & simplified, following multiple feedbacks from @RodrigoTR @uhed01 @Andrebarrzz91 @amia7z If you still have issues with this part I highly suggest to try this new version. Then, some new storage features: Multiple saves can be opened, allowing pkm moves between them Each storage can be splitted in 2, allowing pkm moves intra-save for instance, using this button Multiple pkms can be selected via checkbox, allowing actions like move on multiple pkms at once Also, important performance improvements on pkm move action, and save action. Slowness you encountered @anticristian5 should be fixed. Finally, global stability improvements, reducing bugs & catching errors avoiding global app crash.