Unity sync
Unity sync
Section titled “Unity sync”The Unity adapter syncs Poneglyph data into a Unity project’s localization JSON files via a named pipe, and accepts edits back.
Prerequisites in your Unity project
Section titled “Prerequisites in your Unity project”- The
com.unity.nuget.newtonsoft-jsonpackage (Unity Package Manager). - The Poneglyph sync editor scripts copied into
Assets/Editor/PoneglyphSync/. The first sync link offers to copy them in for you.
Set up a sync link
Section titled “Set up a sync link”- Sync → Add sync link → Unity.
- Pick the Unity project root on disk.
- Pick the target table (or leave blank to auto-pick the first available line table).
- Confirm.
The status bar shows a Unity chip; the engine-side editor scripts watch the JSON files for changes once Unity is open.
What syncs
Section titled “What syncs”- Line names → JSON keys (formatted as
FolderPath/LineName, e.g.UI/Buttons/Play). - Translations → JSON values per language.
- Folder structure → key prefixes.
Editing offline
Section titled “Editing offline”Open the JSON files in any text editor or in the Unity inspector. Save your changes; reconnect the sync (or restart Unity); the changes appear as a proposal in Poneglyph’s staging area.
Strict validation
Section titled “Strict validation”When strict validation is on (default), the sync engine rejects proposals that introduce keys Poneglyph doesn’t recognise. Turn it off if you want to allow Unity-side developers to add new lines straight from the engine.