Lost Lily/Grid ToolkitDocs 1.0
Table of Contents
BeginnerValidated 1.0.0

Update or remove Grid Toolkit

For an existing installation, follow the update or removal procedure below. New projects should start with Install Grid Toolkit.

Before you start

Identify project-owned scripts, scenes, prefabs, and ScriptableObjects that reference Grid Toolkit types. An update must leave one installed version; removal must also account for serialized references.

Update Grid Toolkit

  1. Read the target release's migration guidance.
  2. In Window > Package Manager > My Assets, download and import the target Store version. For a directly supplied archive, use Assets > Import Package > Custom Package... instead.
  3. When the release requires a clean replacement, remove only the existing Grid Toolkit package roots, then immediately import the target version at the same paths. Do not keep a renamed or duplicated copy of the older package.
  4. Confirm that only one Grid Toolkit version remains.
  5. Check authored boards, snapshots, actions, and renderer integrations used by your project.

For unpublished or pre-1.0 builds, follow the pre-1.0 reset policy. Version 1.0.0 does not promise compatibility with earlier API signatures, serialized assets, or snapshot payloads.

Remove Grid Toolkit

  1. Remove project code references to LostLily.GridToolkit.* and LostLily.Inspector assemblies.
  2. Remove or migrate project assets that serialize Grid Toolkit types.
  3. Remove the shipped Assets/ExternalTools/LostLily/GridToolkit, GridToolkit.uGUI, and GridToolkit.Samples roots. Remove the shared Common root only when no other Lost Lily tool in the project uses it.
  4. The GridToolkit.uGUI root is Grid Toolkit's shipped Canvas module. It is not Unity's com.unity.ugui package. Remove com.unity.ugui from Package Manager only when no other project code or package needs that dependency.
  5. Confirm that no remaining assembly or serialized asset unintentionally depends on Grid Toolkit.

Troubleshooting

Symptom Check
Duplicate type or assembly errors Find and remove the older imported version.
Missing-script components after removal Restore the project, migrate or remove serialized assets first, then repeat removal.
Pre-1.0 assets fail to load Use the reset policy instead of assuming serialized compatibility.