You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Wonder if your line is running too long without {nl}'s but don't want to count? I built an app that simulates what one would see in-game for dialogue and right-side quest descriptions. Quest titles and books are To-do.
It will simulate things pretty well, adding line breaks at correct intervals and even simulating the cut off we see with Quest stuff on the right side.
Known bugs: If a line perfectly runs for ___interval (120/90 chars for dialog, 45 for quest) and then has an {nl}, the app will actually create a {nl} right before the {nl}, resulting in a double line-skip. Can someone confirm if this happens in the actual game?
Also, this runs best full screen. I've made the app stretchy and responsive and scalable, but I can't guarantee the font sizes/positioning will be perfect.
With this, we can get a pretty accurate idea of what our text will look like in-game without actually playing the game, finding the actual line, etc.etc. No one's got the time to do that for each and every line in a file anyways 😄
The text was updated successfully, but these errors were encountered:
Wonder if your line is running too long without {nl}'s but don't want to count? I built an app that simulates what one would see in-game for dialogue and right-side quest descriptions. Quest titles and books are To-do.
Here it is: http://vtange.github.io/TreeOfSaviorFormatter/
It will simulate things pretty well, adding line breaks at correct intervals and even simulating the cut off we see with Quest stuff on the right side.
Known bugs: If a line perfectly runs for ___interval (120/90 chars for dialog, 45 for quest) and then has an {nl}, the app will actually create a {nl} right before the {nl}, resulting in a double line-skip. Can someone confirm if this happens in the actual game?
Also, this runs best full screen. I've made the app stretchy and responsive and scalable, but I can't guarantee the font sizes/positioning will be perfect.
With this, we can get a pretty accurate idea of what our text will look like in-game without actually playing the game, finding the actual line, etc.etc. No one's got the time to do that for each and every line in a file anyways 😄
The text was updated successfully, but these errors were encountered: