We are using a custom parser that is a modification of the default one! Where could we check if it is set up to interpret periods that way or where in the original parser does it look for periods to break up passages?
Oh I think I was misinterpreting the issue... do you mean that when a tag like <<set $var to value>> has a period in it, parsing fails? Or is a string with "." in it being considered the end of a section of text, requiring player input afterwards?
The default parser shouldn't be breaking up passages by periods at all, only with linebreaks (and special strings interpreted as linebreaks, as seen here:)
So... make sure that "." isn't in that array! But if that's not the issue, I'll have to take a deeper dive into what may be causing this...
Just checked and it wasn't in that list. Upon closer inspection our hypothesis that its caused by ellipses might not have been accurate as it seems to be parsing them just fine now (as well as "..." and " " lines). I think the bug that this thread was started over might be caused by something else that happened to coincide with ellipses being there. Sorry about that, I'll keep you updated if we find the real culprit!