https://pastebin.com/0CtUbyQA

Just started doing this after one of the recent updates.

So this was an easy fix, just had to make a new quest. After I did that there was no issue copying. This could probably be removed but I'm not taking it down in case someone else has the same thing happen to them.

I don't know how you got it into that state but somehow you managed to copy a quest that existed in the quest line but not in the underlying quest database. I'll attempt to add a pre-check for this but I can't be certain it'd stop it from crashing completely. You wouldn't happen to be working on a pack of considerable size would you? I've been getting an increasing number of reports of network sync failures and maybe that had something to do with this unusual crash state.

Sounds like while messing with them you forgot to maintain all of the IDs properly. For example deleting a quest directly off file but forgetting about its quest line entry. This is partly why I'd rather people use the editors and let the code handle database edits and the IDs

It's got less than 100 quests but a lot of them have auto-complete on if that means anything. I can give you the quest file if you wish. I think it may have been associated with me fucking around with the json file, going back into the game to check it, leaving to mess with it, and so on. I know that if I do this enough over a given session the game becomes unbearably laggy at some point and I have to restart it altogether.

Should I not be doing that?