I think I've found the issue, it will be fixed in 0.5 (scheduled before August).
Thanks for your report, i'm not sure I can fix it in your current game state :(
I'm also adding debug options to handle these cases in future releases.
thx
