Localization improvement suggestion

[Andreu35]

Hi Oleg,
I am testing your work, really nice dialogue system, thank you, really awesome.
Just few suggestions to improve the Localization integration...

1

• Instead to be required to "Set Up Localization Table", why not to add also ( if possible of course ) to select an already created table?
  • This suggestion is because, some devs already has prepared the tables for all the texts.

---

2

• Instead to write the texts for the names and dialogues, why not add 2 Drowdown or List items to select the keys?
  • Example:
    • Name -> Key selected
    • Dialogue -> Key selected
      • ( But instead of showing the key, showing the value on the default language )

---

3 Just a personal idea

• If the Localization Tables have global tables like Speakers Table containing only the NPC's name, why not to add a table selection for each field?
  • I saw, after set up the table and updating the keys, inside the table is showing SentenceText_ and SentenceName_ on the same table. Yes, is using the key to recognize each text, but maybe, can be more clear and clean to have separated tables?

I know this can be a tedious work, but I think that can be a really improvement and reduce time when setting up the dialogues.

[Q] Is using the old Input system?

Again, thank you so much for this, is really awesome!

[OlegVishnivetsky]

Hello @Andreu35 thanks for the feedback – I'm glad if my tool helped in any way.

Regarding the first point.
In fact, you can already use ready-made tables. It's not yet implemented in the most convenient way, but the option is there:

1. Manually specify the table name by clicking DialogNodeGraph scriptable object then edit the LocalizationTableName field in the inspector by writing your ready-made talbe name;
2. Then replace keys in each node manually with the keys from this table.
   ! Important: do not click the Update Keys button, otherwise the values ​​in the table will be erased.

Regarding the second point.
I completely agree that the option you described would be much more convenient. I'll try to add this feature in future versions, but I can't promise it will be quick. If anyone has ideas or wants to help with the implementation, I'd appreciate any contribution (contributions are welcome).

Regarding the third point.
I also agree. Initially, I was thinking of creating a separate global table, for example, for character names. Names are often repeated and used in different places, so a common source would really be convenient. In the DialogNodeGraph, you can even see the Character Names Localization Table field - I started implementing this feature, but at some point I got stuck and decided to put it on hold for now.

In any case, thanks for the suggestions! I'll take them into account when further developing the tool.