Fragment catalog

Base fragment lifecycle

URicItemFragment calls its native initialization hook and OnItemInstanceCreated Blueprint-native event for an item instance. URicContainerFragment similarly provides native initialization and the OnContainerInstanceCreated Blueprint event.

Fragments are instanced configuration attached to definition assets. Runtime state belongs to the created instances.

Item fragments

Presentation

• URicItemFragmentText: localized Name and Description as FText.
• URicItemFragmentIcon: a 2D icon texture.
• URicItemFragmentWorldMesh: a static/skeletal mesh reference and MeshScale.
• URicItemFragmentVisualResolver: the presentation resolver class.

Shape and rotation

• URicItemFragmentJigsawShapeBase: common abstract shape interface.
• URicItemFragmentJigsawItemShape: filled rectangular item shape.
• URicItemFragmentJigsawItemShapeCustom: an explicit occupied-cell mask.
• URicItemFragmentRotation: allowed 90°, 180°, and 270° rotations.

Use one appropriate shape source for an item rather than conflicting rectangular and custom shape fragments.

Runtime initialization

• URicItemFragmentSetStats: initial integer tag-stack values in InitialItemStats.
• URicItemFragmentGameplayTags: initial gameplay tags, each added with a stack count of 1.

Nested containers

• URicItemFragmentContainer: creates one configured container inside the item.
• URicItemFragmentContainerCollection: creates a collection of containers inside the item.

Actions and ammunition

• URicItemFragmentActions: ExecutableActionClasses, returned as action CDOs.
• URicItemFragmentMagazineData: ammunition-definition reference used by the ammo operations.

These fragments supply configuration, not a complete weapon or interaction UI.

Container fragments

Implementation selection

Set the definition's main ContainerFragment to:

• URicContainerFragmentJigsawFixedSize: grid implementation and shape.
• URicContainerFragmentOneItem: single-slot implementation.

Both derive from URicContainerFragmentContainerBase, which holds the ContainerClass and ContainerTag.

Additional rules

• URicContainerFragmentDynamicFilter: tag-match mode, tags, and child inheritance.
• URicContainerFragmentFilters: filter classes and child inheritance configuration.

These rules are read by container initialization. A fragment having an empty native hook does not imply that its configuration is unused.

Find a fragment

Use FindFragmentByClass for Blueprint access. In C++, item definitions and instances also provide typed helpers.

#include "Definitions/RicItemDefinition.h"
#include "Fragments/Item/RicItemFragmentText.h"

const URicItemFragmentText* Text =
    Definition ? Definition->FindFragment<URicItemFragmentText>() : nullptr;

Always handle a missing fragment. See the public class catalog for descriptions of individual fragment classes.