Thanks very much for looking into this. I'm afraid I can't answer your question. Tahnan and I both got the same crash after we played and attempted to delete the architecture board version of this hold. I've been trying to reproduce the crash starting with a new player.dat and haven't been able to yet. I'd be happy to send you my old .dats, if they would be helpful. Or maybe with some guidance from someone who knows what they're doing, I could make better progress at this.
I can reproduce other weird stuff that appears to be wrong with my old "
corrupted"
player.dat, but I haven't made it crash like it did before. Part of player.dat is a list of "
messages"
, which includes a chronological list of demo titles (for TCB) and hold text plus demo titles (for other holds). I think this is what the line in drod.err referred to? In my old "
corrupted"
player.dat, this list has become scrambled, out of chronological order, and begins with a message fragment. I can reproduce the scrambling, by (1) starting with a new player that has only played TCB (2) importing and playing some of the Inferno (3) without quitting DROD, hit ESC and Play New Game (4) play a couple rooms over again. This scrambles the message list, sometimes leaving a fragment at the beginning, but doesn't cause a crash when I delete the hold. (There is no message scrambling if I quit and restart DROD before playing a new game.)
I also noticed that deleting a hold never deletes the text from the opening screen of that hold. But again, this doesn't cause a crash.
If it's not other people's demos (the only holds I've played in 3.0 are TCB and the Inferno), I don't know what else it could be. All I know is I've got some .dats with an undeletable hold in them.