Installing and Requirements

Export

Install the released Ultimate Inventory System Version 1 package and confirm that its editor, runtime, and Opsive Shared dependency compile before creating database or scene content.

Requirements

  • Unity: Use Unity 2022.3 or newer for the current released documentation baseline.
  • Packages: Install one copy of Ultimate Inventory System Version 1 and its matching Opsive Shared package.
  • Compilation: Resolve every Console compiler error before opening Main Manager or importing optional integrations.
  • Sample: The demo requires TextMesh Pro and uses Universal Render Pipeline content.
  • Project ownership: Keep project databases, prefabs, UI schemas, and edited assets under project-owned Assets folders rather than modifying package content.

These pages document released UIS Version 1. Version 2 development APIs and editor labels are not interchangeable with the current package.

Install the package

  1. Import or install the UIS package supplied through the Opsive download workflow.
  2. Allow Unity to import UIS and Opsive Shared completely.
  3. Wait for compilation to finish before importing integrations, samples, or copied project scripts.
  4. Confirm that Tools > Opsive > Ultimate Inventory System > Main Manager and UI Designer are available.
  5. Open Main Manager and confirm that Setup, Item Categories, Item Definitions, Currencies, Crafting data, Integrations, and the other installed Version 1 editors load without exceptions.

Do not combine package files from different UIS or Shared releases. An older integration should also be removed before importing its current replacement so duplicate types cannot hide the core package result.

Verify the project structure

The runtime package appears under Packages/Opsive Ultimate Inventory System or the corresponding package entry. Treat it as package-owned content. Create a project folder such as Assets/MyGame/Inventory for the Inventory System Database, duplicated UI schema, Item prefabs, and project scripts.

Import the optional demo

  1. Open Tools > Opsive > Ultimate Inventory System > Main Manager.
  2. Select Setup and import the Demo sample.
  3. Install TextMesh Pro and its essential resources when prompted.
  4. Confirm that the active render pipeline can display the sample’s URP materials, or use the demo only as a structural reference in another pipeline.
  5. Open the sample from its versioned Assets/Samples folder.

The sample uses DemoInventoryDatabase and demo-specific scripts. Reimport it when it is changed accidentally; do not turn the versioned sample folder into production content.

Installation checkpoint

Before creating a database, confirm that:

  • the Console has no compiler errors;
  • Main Manager and UI Designer open;
  • UIS and Opsive Shared exist once;
  • the project-owned inventory folder exists; and
  • any imported sample opens without missing-package errors.

Troubleshooting

Symptom Check Fix
Main Manager is missing. UIS package import and compiler errors. Reimport the matching package and resolve the first Console error.
Duplicate type or assembly errors appear. Multiple UIS, Shared, or integration copies. Keep one matching release and remove the incomplete/older duplicate before reimporting.
Demo text is missing. TextMesh Pro package and essential resources. Install/import TMP, then reopen the sample.
Demo materials are pink. Active render pipeline and sample URP materials. Use a compatible URP setup or treat the demo as a structural reference.
Project edits disappear after an update. Assets were edited under Packages or a versioned sample folder. Duplicate/create them in a project-owned Assets folder.

Next step

Continue with Your First Inventory.