Hi @makstfate,
Thank you for providing detailed steps to reproduce this bug.
We have identified that this issue occurs in the deck editor in version 0.5.8.147. To resolve it in the current version, please edit the “set_aside” key in your deck to match the starter deck using any text editor (e.g. VSCode).
We appreciate your patience, and we will address this bug in the next version.