That error is 'normal' (in that it's just a bug in 2.0e). There's no workaround, really, besides not getting caught or playing 2.0d. However, I did some poking around and fixed the commonevent that causes it, if you're interested. Just apply it like you would a translation: extract this and the...