Skip to main content

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

Hi! Thanks for using STM, it means a ton!


I'm on vacation right now, but I'll give this a quick look...

Is the character '。' exactly? In STM, there's a long array of "linebreakUnfriendlyCharacters" which controls what characters can never appear at the start of a line, and this character is in it... Can you make sure there's no space/zero-width space before the '。'?


Also, is the variable "breakText" disabled in the STM inspector? Does disabling "insertHyphens" when using Japanese text make a diff at all?


Off the top of my head, those are two things I can think of to look at first! If neither of those work, I'll have to figure out what it could be... In that case, could you paste that exact string of text you're sending to STM here?

(6 edits)

* OK FOR NOW IGNORE THIS.  Appears the update did not take last time and so now I see the changes.  Sorry about that stupid unity said it was on the latest version but some of the files apparently did not take.  Fixing and will let you know if there are any issues.

WORKING AS DESIGNED NOW.  Again sorry.


Here is the exact text.  You can see there is no space at all at the end character '。'  Actual text is included at the bottom.

Toggling off and on the hyphen made no difference.  Thanks for the help going to take a look as well inside the code.

Also using a true type font so not sure if that has something to do with it???  Though it does appear to be working sometimes with ! inside of text ie not at the end.

Oh another oddity "linebreakUnfriendlyCharacters" could not find this while searching the code.   But I can find linebreakFriendlyChars so that seems odd.  Going to check if the update did not take at some point or if my custom changes interfered with that.

<c=green><a=center><i>ウキウキモード 起動</i></a></c><d=20>

全可動部 機能ヲ確認<d=20> 有機生命体ニ感謝シマス。

It's ok! It's strange, I've actually gotten a few errors where the solution was an update improperly applying... I've even run into it myself when re-importing despite seeing new files and making sure they were checked (in fact, I'm pretty sure that thanks to this, some code in another asset of mine hasn't gotten published so I'm planning a complete manual code comparison...) so... I'm not too sure why Unity's doing that, maybe something could be wrong with my metadata...?


Either way, glad it works!