Check for updates
If your current copy opens, let its updater finish before replacing files. When it no longer launches or the updater keeps failing, check the current guidance from Project Ignis and compare the client version shown in EDOPro with the release information. Confirm the platform and package type before running an update manually.
If you have a portable desktop build, extract a fresh full package into a separate folder and open it before copying anything from the old installation. This lets you check whether the fresh copy starts on its own. Keep the old folder available until you’ve tested the new copy and restored your decks.
Back up your YDK files
Desktop decks are usually stored as .ydk files inside the deck folder. Copy your deck folder to a separate location before reinstalling. On Android, look for a deck export or save option and copy the files to a location you can open outside the app before uninstalling.
If you have several desktop copies, save a deck with a distinctive temporary name and search for that filename. Its location tells you which copy is writing your decks. Open your backup folder before removing the old copy and check that it contains the decks you expect.
Restore decks after reinstalling
Launch the new copy once so it creates its folders. On desktop, copy the saved YDK files into the new deck folder and reopen the editor. If you use several portable copies, check which one you launched. On Android, use the client’s available import workflow and confirm the deck opens before deleting your backup.
Open a restored deck and check its Main, Extra, and Side Decks. If the file is present but a card is missing from the editor, let the first run finish updating card data and check again. For a deck that appears in the editor but fails a room’s rules, check that room’s banlist and allowed card pool.
How to verify the EDOPro download
If setup reports an incomplete file, find the exact filename in the Project Ignis release record and compare its published MD5 checksum with the checksum of your local file. The Windows installer and self-extracting archive both end in .exe, so check the full name before choosing a checksum.
In Windows PowerShell, run Get-FileHash -Algorithm MD5 followed by the path to the downloaded file in quotes. On macOS, use md5 followed by the quoted path. On Linux, use md5sum the same way. Compare the full value shown by the command with the publisher’s value. If they differ, download the matching package again.