Persistent Variables source

Providing Arguments to a Smart String often requires writing a script. The persistent variables source works with Global Variables and LocalizedString Local Variables to let you specify arguments to a Smart String without a script. In the Editor you can configure arguments for various data types, and create custom arguments.

Inspector window showing Smart String Persistent Variables source field.

Local Variables

Local Variables let you set up arguments to a Localized String that can then be driven by scripts. You can add Local Variables in the Editor or via script. When you change the value of a Local Variable that is in use, the Localized String automatically refreshes.

You can preview Local variables outside of Play Mode, which makes it quicker to author Smart Strings. As such, Local Variables are ideal for testing Smart Strings with various inputs. You can replace the local variable when the Smart String is completed.

Example of a Local Variable being Previewed in the Editor. .

The Smart String {player-name} scored {score} points and {objective:Completed|Failed} the objective. becomes Player 1 scored 55 points and Completed the objective.

Global Variables

You can configure the Persistent Variables source with multiple global variables to pull data from an external source and convert it into a Smart String without requiring any additional arguments. When the value of a Global Variable changes, you can configure it to automatically update any LocalizedStrings that currently use it.

Access Global Variables by using dot notation inside a placeholder with the following structure:

{group-name.variable-name}
{group-name.nested-group-name.variable-name}

Variables Group asset

A Variables Group asset can contain multiple Persistent Variables and/or Nested Variable Groups. Create a Variable Group through the Assets menu: Assets > Create > Localization > Variables Group. You can assign a Variables Group to the Persistent Variables Source as a Global Variables Group, where it is accessible from any Smart String. It can also be assigned to a Localized Strings Local Arguments where it is only accessible from that Localized String instance.

Inspector window showing Variables Group asset with 5 configured variables. From top to bottom, a float variable named my-float with the value 1.23; a string variable named my-string with the value "This is an example"; an int variable named int-variable with the value 1; a bool variable named my-bool with a checked tick box and a nested variable field named nested-group with a reference to an asset called Nested Group.

To allow Smart Strings to access Global Variables, you must add a Persistent Variables Source to the Smart Format Sources list.

You can add Variable Groups to the list, so long as each group has a unique name with no spaces.

The following example shows a single group with the name global.

Two inspector panels, the one on the left shows a persistent source configured with a global variable reference to the above variables group asset, which is also shown on the right panel.

Example Smart String Result
My Floats value is {global.my-float} My Floats value is 1.23
{global.my-string} of using global variables. This is an example of using global variables.
The door is {global.my-bool:Open|Closed}. The door is Open
This is an integer {global.int-variable} as Hex {global.int-variable:X}. This is an integer 255 as Hex FF
Values can be nested {global.nested-group.player-name} Values can be nested Player 1

Triggering updates

Persistent Variables can trigger automatic updates to any LocalizedStrings that are currently using it. This means there is no need to track which UI fields need to be updated. If a value changes, the LocalizedStrings automatically update to the new value. To configure a Variable to automatically update LocalizedStrings, have the Variable implement the IVariableValueChanged interface. The LocalizedStrings checks which Variables it references, and adds itself to the Value Changed events of those Variables. When a value changes, the Value Changed events run and the LocalizedStrings automatically refresh to the new value.

var source = LocalizationSettings.StringDatabase.SmartFormatter.GetSourceExtension<PersistentVariablesSource>();
var myFloat = source["global"]["my-float"] as FloatVariable;

// This will trigger an update
myFloat.Value = 123;

You can stop the automatic updates of the LocalizedStrings when changing multiple Variables by updating within a PersistentVariablesSource Update Scope. Use this to prevent unnecessary updates.

public class RandomPlayerStats : MonoBehaviour
{
    public string[] stats = new[] { "vitality", "endurance", "strength", "dexterity", "intelligence" };

    public void RandomStats()
    {
        var source = LocalizationSettings.StringDatabase.SmartFormatter.GetSourceExtension<PersistentVariablesSource>();
        var nestedGroup = source["global-sample"]["player"] as NestedVariablesGroup;

        // An UpdateScope or using BeginUpdating and EndUpdating can be used to combine multiple changes into a single Update.
        // This prevents unnecessary string refreshes when updating multiple Global Variables.
        using (PersistentVariablesSource.UpdateScope())
        {
            foreach (var name in stats)
            {
                var variable = nestedGroup.Value[name] as IntVariable;
                variable.Value = Random.Range(0, 10);
            }
        }
    }
}

Persistent Variable types

By default you can add the following Persistent Variables:

Name Description
Float Contains a single float value.
String Contains a single string value.
Integer Contains a single int value.
Bool Contains a single bool value.
Object Reference Can be used to reference a UnityEngine Object.
Nested Variables Group Can be used to contain a reference to a Persistent Variables Group Asset. This can allow for nesting of variables.
LocalizedString Can be used to provide nested translations.

Nested translations

A Localized String can be a persistent variable, allowing for nested translations. For example the following dynamic string could use localized values for both the item name and the color: The {item} is {color}.

The localized string should be configured in the following way:

Inspector showing a LocalizedString with 2 local variables, both of which are also LocalizedStrings, one is called item and the other is called color. The English value is The {item} is {color}.

Localization table window showing multiple entries which can be nested into each other.

The nested localized strings are extracted during the formatting step. If a nested localized string is not currently available, such as when the table is still being loaded, an empty string is returned. When the string loads, a ValueChanged event is triggered, which triggers the root LocalizedString to refresh. If you wish to avoid this, Unity recommends you enable preloading on the nested tables if they are different from the root table.

Handling gender

In some languages gender can change the version of a word that must be used. For example, in Spanish all nouns have a gender, that means they are either masculine or feminine. The gender of the item affects the structure of the sentence.

When the sentence The {item} is {color} is translated to Spanish, it changes based on the gender.

When masculine the structure would be: El {item} es {masculine color}

When feminine, the structure would be La {item} es {feminine color}

For example if the item was a pen(bolígrafo) then the masculine version would need to be used, if the color was red we would also need to use the masculine version which would be rojo. The full sentence would be: El bolígrafo es rojo

One way to handle this is by using the Choose formatter.

For example: {gender:choose(Male|Female):El|La} {item} es {color}. In this example gender could be defined as a local variable in the LocalizedString.

To enable translators to define the gender of the item they are translating, add metadata, for example:

[Metadata(AllowedTypes = MetadataType.StringTableEntry)]
[Serializable]
public class ItemGender : IMetadata
{
    public enum Gender
    {
        None,
        Female,
        Male
    }

    public Gender gender = Gender.None;
}

Translators could then add the metadata to Spanish entries to define the gender of the entry. You could sync this to a Google sheet or CSV to let translators set the gender remotely without using Unity.

Screenshot showing a field with Spanish text boligrafo (pen). Next to the text the metadata for Item gender is set to Male.

To enable access to metadata, implement the IMetadataVariable interface in the metadata script.

The example below shows how the gender metadata could be updated:

[Metadata(AllowedTypes = MetadataType.StringTableEntry)]
[Serializable]
public class ItemGender : IMetadata, IMetadataVariable
{
    public enum Gender
    {
        None,
        Female,
        Male
    }

    public Gender gender = Gender.None;

    /// <summary>
    /// The name used to identify this metadata.
    /// </summary>
    public string VariableName => "gender";

    public object GetSourceValue(ISelectorInfo _) => gender;
}

The VariableName identifies which metadata to use. GetSourceValue then extracts that value during formatting.

A string with {item.gender} can extract the gender metadata from the returned Entry. Nested localized strings also have access to the current value, this can be used within the nested scope. This means that a translated string for red would look like:

{gender:choose(Male|Female):rojo|roja}

The selector gender is first checked in the current value, if one is not found it will then check the local variables. This means that you do not need to provide the full path and can use different data types providing they have a selector that matches gender.

The final Spanish translation would take the form:

{item.gender:choose(Male|Female):El|La} {item} es {item:{color}}

When formatting a nested translation, they have access to both the parent local variables and the local variables defined in the current LocalizedStrings. The local variables are first evaluated and then the parent variables if no match was found locally.

The colors would be translated to:

Color Spanish
red {gender:choose(Male|Female):rojo|roja}
green verde
blue azul
white {gender:choose(Male|Female):blanco|blanca}
black {gender:choose(Male|Female):negro|negra}

Note: not all colors have a gendered version.

Animation showing text being generated for English and Spanish when picking the items backpack or pen and the colors white, black, red, green and blue.

The following diagram shows a breakdown of the Smart String:

Diagram showing the breakdown of the Smart String and how each part is evaluated.

This diagram shows how the Spanish translation for "The backpack is red" would be resolved.

Diagram showing the breakdown of the Smart String and how each part is evaluated.

The above example can be found in the package samples under the Persistent Variables sample.

Custom Persistent Variables

A custom Variable must be Serializable and implement IVariable. The following example demonstrates how to use a Variable to return the current time.

/// <summary>
/// This is an example of a Global Variable that can return the current time.
/// </summary>
[DisplayName("Current Date Time")]
public class CurrentTime : IVariable
{
    public object GetSourceValue(ISelectorInfo _) => DateTime.Now;
}

This example shows how to create a variable to convert XML text into an XElement variable.

[DisplayName("XML Text")]
public class XmlElement : IVariable
{
    public string xmlText;

    public object GetSourceValue(ISelectorInfo selector)
    {
        try
        {
            if (!string.IsNullOrEmpty(xmlText))
            {
                return XElement.Parse(xmlText);
            }
        }
        catch (Exception e)
        {
            Debug.LogException(e);
        }

        return null;
    }
}

To trigger updates to any LocalizedStrings that uses the Variable, implement the IVariableValueChanged interface.

[Serializable]
public class MyVariable : IVariable, IVariableValueChanged
{
    [SerializeField]
    string m_Value;

    public string Value
    {
        get => m_Value;
        set
        {
            if (m_Value == value)
                return;

            m_Value = value;
            ValueChanged?.Invoke(this);
        }
    }

    public event Action<IVariable> ValueChanged;

    public object GetSourceValue(ISelectorInfo _) => Value;
}

Custom Variable Groups

Use Custom Variable Groups to return custom Variables. The following example demonstrates this.

struct ReturnValue : IVariable
{
    public object SourceValue { get; set; }

    public object GetSourceValue(ISelectorInfo _) => SourceValue;
}

/// <summary>
/// This example shows how a nested group can be used to return custom data without the need for Reflection.
/// </summary>
[DisplayName("Weapon Damage")]
[Serializable]
public class WeaponDamageGroup : IVariableGroup, IVariable
{
    public object GetSourceValue(ISelectorInfo _) => this;

    public bool TryGetValue(string key, out IVariable value)
    {
        switch (key)
        {
            case "sword":
                value = new ReturnValue { SourceValue = 6 };
                return true;

            case "mace":
                value = new ReturnValue { SourceValue = 5 };
                return true;

            case "axe":
                value = new ReturnValue { SourceValue = 8 };
                return true;

            case "dagger":
                value = new ReturnValue { SourceValue = 2 };
                return true;
        }

        value = null;
        return false;
    }
}