Extension points

Item and container fragments

Derive from URicItemFragment or URicContainerFragment to add definition configuration and instance-creation hooks. Native code overrides OnInstanceCreatedNative; Blueprint item fragments implement On Item Instance Created, and container fragments implement On Instance Created.

Store instance-specific data on a runtime object or in item tag stacks. Definition fragments can be shared by many instances.

Placement filters

Override URicFilterBase.PassesFilter and register the class through a container-filter fragment. The default native filter allows placement.

Filters can be shared class default objects. Avoid caching per-item or per-container mutable state on those CDOs.

Item actions

Derive from URicItemAction to define a menu label, menu visibility, availability, and execution. Include the class in an actions fragment.

Choose the server route with bExecuteOnServer and implement the gameplay checks required by the action. Returning true from the default action hook alone does not implement an effect.

Visual resolvers

Derive from URicVisualResolver for custom text, dimensions, icon materials, and stat-dependent presentation. Use resolver contexts to separate presentation roles and pair subscriptions with cleanup.

Custom containers

A custom URicContainerBase subclass must implement its layout, placement, queries, removal, splitting, save restoration, and replicated state consistently.

Select the class through a URicContainerFragmentContainerBase derivative. Wrap direct storage and ownership changes in FRicScopedReplicationUpdate from before the mutation through completion or rollback.

Swap strategies

Subclass URicSwapStrategyBase and select it in inventory settings. Align availability checks with execution and check every placement result. The provided strategies have known limitations in this snapshot; they are not atomic-transaction templates.

Tick handlers

Subclass URicTickHandler, register the class with URicInventorySubsystem, and implement OnTick(ContainerInstance). Calls use the CDO, not a new handler instance for each container.

Interaction search

Derive from URicInteractionStrategyBase to change local point discovery and selection. UI listeners implement IRicInteractionInterface.

Changing local search does not add server distance validation. Implement gameplay validation in the authoritative execution path when needed.