On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags

Fleece

A dialogue manager for Unity that doesn't fray at the edges. · By KaiClavier

Unicode stall for ellipses

A topic by theshepherdshound created 18 days ago Views: 34 Replies: 4
Viewing posts 1 to 2

Hey!

We're having an issue for parsing through “…” (U+2026) over "..." which is keeping dialogue from progressing. Is there a way to change internally the parsing of unicode characters, or is it easier if we ctrl+f though all of the dialogue before adding for the code? 

Developer

Hey!


Hm, so is your project set up so that periods cause a full stop, waiting for user input? I recently added a feature to prevent this with ellipsis to Super Text Mesh, so I'll share...

Basically, is it possible to: instead of parsing for a period, to instead look for a period that does *not* have a period immediately after it?


...That's if I'm assuming the situation correctly! Please let me know if I'm misunderstanding... Like are you using the default parser? Or something custom?

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?

Developer

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!