Hey, just upgraded to 1.8.1 and it's working great so far! There is one small regression from 1.7 involving the <e> and <pause> tags though that I thought I'd bring to your attention as it's probably worth fixing. It seems that now that if you surround a <pause> tag by two <e> tags, the <e> tag after the <pause> is ignored when the text resumes after calling Continue().
For example, when I feed this string into STM, "event1" is correctly received as a custom event as expected, but "event2" is never received after Continue() is called (though "TestB" is printed):
TestA<e=event1><pause><e=event2>TestB
In STM 1.7, both event1 and event2 would be received. For now, I've managed to manually work around this in STM 1.8.1 by inserting a zero-width character between the <pause> and second <e> tag, so it's not really a pressing bug for me, but it still seems like something that'd be worth fixing in the future.
Also, someting unrelated: it looks like the "Events" foldout in STM's inspector has the "CustomEvent" field mistakenly displayed twice. I took a peek at STM's source code and I think a duplicated line of code here is the cause:
EditorGUILayout.PropertyField(serializedObject.FindProperty("onRebuildEvent"));
EditorGUILayout.PropertyField(serializedObject.FindProperty("onPrintEvent"));
EditorGUILayout.PropertyField(serializedObject.FindProperty("onCompleteEvent"));
EditorGUILayout.PropertyField(serializedObject.FindProperty("onUndrawnEvent"));
EditorGUILayout.PropertyField(serializedObject.FindProperty("customEvent")); // customEvent #1
EditorGUILayout.PropertyField(serializedObject.FindProperty("vertexMod"));
EditorGUILayout.PropertyField(serializedObject.FindProperty("preParse"));
EditorGUILayout.PropertyField(serializedObject.FindProperty("customEvent")); // customEvent #2 (remove this??)