Bug report. I've hit this several times now. I edit a trigger. ctrl+s to save. Map comes up with an error about some missing library. I navigate to a different trigger and then click back to the one I had been editing earlier and discover that everything is gone, replaced by this small snippet of corruption: So the error about the missing library is because my several hundred or so lines of code in that trigger have disappeared. Worst is that this gets saved. Luckily I version control my project well, but this could be pretty bad for those who don't make backups often. I haven't been able to pin down how to reproduce this reliably yet, but will provide details if/when I figure it out. It's happened twice to me today in the span of an hour, and a few more times in the past few weeks. The only additional info I can give at this stage is that if I try to ctrl+z on the trigger after this has happened, WE crashes. e: K, so it has nothing to do with saving. Seems like in some cases, if i swap to another trigger and swap back, the whole trigger is corrupted. Something to do with saving/loading the text from memory. One time this happened, it pulled through some random map constants through. I should've taken a screenshot, but didn't. Will do next time I see it. Once the trigger is corrupted, trying to paste the original code back in it doesn't stick - swapping to another trigger and back, reverts to corruptedness. So far the best solution I've found is to delete the trigger, create a new one and paste the old code there. So, I'm inclined to say it's something to do with the metadata you save for that trigger, be it clipboard history, scrollposition, or something else. Something is going awry. Hopefully this'll be enough to help pin it down.