Architecture

An ItemDefinition stores an item’s footprint, stack limit, weight, and presentation data. An InventoryDefinition chooses a container’s shape and rules. These ScriptableObjects let you author reusable data independently of a particular scene object.

DefinitionBase supplies a stable GUID-backed DefinitionId. GameDatabase and definition registries use that identity to find authored content. Moving an asset in the project doesn’t require changing its definition ID; regenerating that ID can break references in saved data.

Two players can carry the same type of rifle with different attachments and ammunition. Both rifles reference shared definitions, while each runtime instance records what is happening to that particular weapon.

InventoryRuntime handles storage and placement. The Unity-facing InventoryComponent applies authored acceptance rules and connects the model to the scene. Similar Core and Unity assembly boundaries appear across Foundry, although their exact dependencies vary by package.

Use a service when your code needs to query or change another system. IInventoryService, for example, exposes the player inventory and operations for adding items. Check the returned result so your UI can explain a failed operation.

Use an event when other systems need to react to a change. Messaging provides synchronous, in-process publication and subscription, alongside a type-keyed service registry. Registration and subscription lifetimes still belong to the code that owns them.

Packages contribute modules to the Workbench. Each module supplies a page or a set of tools, and the navigation catalogue places it in a workspace. The shell discovers these modules without a direct assembly reference to every package.

FoundryWizardShell provides a step rail, issue tray, and preview dock. Individual tools define their steps and validation. Authoring services perform asset creation and rig assembly; runtime services handle the game after those assets have been created.

A package.json manifest tells Unity Package Manager what to resolve. An .asmdef declares what a C# assembly references. Editor assemblies, runtime assemblies, and optional integrations have different requirements, so inspect both when extracting part of the development project.

The groups below organize packages by purpose. For dependency relationships, follow the links on an individual package page.

Rendering Core defines semantic material and effect identifiers. URP and HDRP adapters resolve them for their pipelines. Pipeline configuration, actual art assets, and visual differences still need attention when moving a project between renderers.

Networking Abstractions provides shared contracts and protocol data. Networking supplies runtime implementations and backend integration. FishNet is the supported backend; other listed backends provide experimental presence and diagnostics integrations. Single-player fallbacks and internal loopback tools serve different purposes from a multiplayer transport.