Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags

Hello! I just found out something. If I use DKTools localization with VisuStella Message Core for <WordWrap> and put it in a JSON Dedicated File to localizate it, it won't work. The text will be just empty.
I tried without localization tag {example}, and it will work, and other plugins or HUD elements will work with the two plugins.

Is there something that can be done, or checked?
Many thanks!

Hey there.

It's been a while since I last worked with this plugin, and even more time since I last reviewed this specific part of the code. However, by reading DKTools page on their plugin and taking a quick look at my code, I think you might need just a small change to get it working.

From what I gathered, DKTools use tags with a single pair of {} around it to replace the texts... right? Does it work with json files for each language set?

First, you need to make sure you have objects defined in each language file with the same structure as a single dedicated external json file for book data. This is important, as that is what the plugin will actually use to find the correct text to use. You are getting an empty text because the plugin didn't find any data for the given tag.

Second, set TAA_BookMenu 'Localization Escape Code' to {{key}} (with two pairs, and no '#' at the beginning as is its default). That because my plugin will replace the {key} with the object path for each component of the scenes (categories, titles, book texts, and so on). For example, it will process the tag and replace it with "{library.books.BookTitle1.title}" to get to the "Book Title 1" title text ({key} will be replaced by library.books.BookTitle1.title, so it will then run the tag {library.books.BookTitle1.title} through the localization plugin to find the correct language text for it).

Hope this is of any help!

Thanks for the reply.

The thing is, I don't have any problem to draw the text from the {key} tag. If I don't use <WordWrap>, the text will be replaced without any problem. But, obv., I need to wrap my text, and when I use <WordWrap> from VisuStella, the text will be "erased", it just won't show any text.
I don't understande why it's that, but from what I understand, it could be some incompatibility with VisuStella?
Eventually if more information are needed, I can provide it.

Many thanks!

It may probably be an incompatibility issue. Since VisuStella's plugins are obfuscated I can't do much about it unfortunately =/

Have you tried the wordwrap feature without the localization plugin?
It may be an incompatibility of combining all three plugins as well.

So, I can say that:

With normal text and Visu Wrap enabled, the text will be displayed normally
Localizated text and Visu Wrap disabled, the text will be displayed normally (not wrapped though, one line only)
Localizated text and Visu Wrap enabled,  the text didn't show up like said

Does maybe this info help to understand? I hope ^^"

Well... that seems to be a compatibility issue between the three plugins. No idea what could be causing this though hehe ^^"

I'm unable to work on my plugins for the next few weeks, but I'll try to replicate it when I can, and see if there is anything I can do on my side.

Ok... I finally managed to get some time to look into it. I did find a bug with the Localization File datasource type, but when I solved it I created a whole lot of issues with others functions from the plugin itself. I'll working on it... just hope I manage to wrap it up before I get caught on life stuff again hehe

Like I wrote in a comment yesterday, I did find some bugs around the localization feature. I managed to get it fully working and published version 1.7.0 with the updates.

I also run some tests combining Visustella's Message Core and DK Tools Localization plugins, and have confirmed that the wordwrap feature works perfectly with this combination of plugins.

Be sure to check the "Compatibility Warnings" inside the plugin help section, as I've added some important notes on how things must be configured for proper compatibility with DK Localization plugin.

It took a while for me to get time to look into this, but I hope it was not too late! =)