I managed to fix the issue.

I randomly guessed that some conflict was happening while trying to do too many migrations at once (from 0.16.11 to 1.0.0) so instead, I loaded the game in 0.18.34, saved it, then re-opened it in 1.0.0 and it was fine after that.

Hi, I am having the same problem. After bisecting it appears to have started with 0.18.37 (blueprint GUI update), which also has different logs from the later versions. 0.18.34 (on my Linux server) is fine, as is 0.18.36 (Windows steam). It happens even after I delete my blueprint-storage.dat, so I ...