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
The localisation table containing the default language lines for a yarn script is not automatically updated when lines in the script are changed. This occurs in at least two situations:
When the project has changed. For example, moving a script which currently belongs to Yarn Project A into a directory which would have it register with Yarn Project B. Yarn Project A is told about the change, but Yarn Project B is not.
When the table has not been touched in a while. This one a bit more vague, but if you have been working on other parts of a Unity project and then make changes to a Yarn script, then come back into Unity, the localisation table will not have changed. If you make another change to the same script and then return to Unity, it will have now applied both changes.
Please provide the steps to reproduce, and if possible a minimal demo of the problem:
Move a script from the directory which corresponds to one Yarn Project, to a project which corresponds to another. Observe that the loc tables for the destination project have not changed.
Apply changes to a Yarn file in a project which has been open for some time but in which no changes to Yarn have been made. Observe that the loc tables have not updated in response to the script changed.
What is the expected behavior?
In each case, that the localisation tables should get regenerated with up-to-date contents.
Please tell us about your environment:
Yarn Spinner Version: 2.4.2
Unity Version: 2022.3.38f1
The text was updated successfully, but these errors were encountered:
What is the current behavior?
The localisation table containing the default language lines for a yarn script is not automatically updated when lines in the script are changed. This occurs in at least two situations:
Please provide the steps to reproduce, and if possible a minimal demo of the problem:
What is the expected behavior?
In each case, that the localisation tables should get regenerated with up-to-date contents.
Please tell us about your environment:
The text was updated successfully, but these errors were encountered: