What ReplayCore renders
The authenticated dashboard viewer applies your uploaded resource pack to recorded items. It supports item model parents, cuboid elements, generated-item extrusion, textures, display transforms, legacy custom-model-data overrides and modern item definitions. The same item-model path is used for held, first-person, dropped, framed and displayed items, including captured carrier items.
Vanilla items remain the baseline. Shields and banners use their recorded patterns, player heads use their recorded skin where available, decorated pots use their recorded face decorations, and supported special items use their vanilla 3D models.
ItemsAdder, Oraxen and Nexo
Upload the same resource pack that your server distributes under Settings, then Resource pack. ReplayCore uses the recorded item id and model selectors to resolve the matching pack model, including a captured plugin item id as the modern item-definition key when no explicit item-model selector exists. Plugin-generated custom-model-data items therefore need no separate ReplayCore configuration.
Legacy plugin items must still carry the custom-model-data value used by their generated pack. Recordings that predate that capture, including the 1.8.8 lane, fall back to the base carrier item.
Keep the pack's model JSON, parent models and referenced textures together. A malformed or unavailable custom definition falls back to the base item so playback remains usable instead of failing the whole replay.
MythicMobs and ModelEngine
ReplayCore reads supported plugin APIs rather than parsing private plugin configuration. MythicMobs identities are recorded alongside the visible vanilla entity state, equipment, movement, damage and death. The uploaded resource pack supplies any item or texture models referenced by that visible state.
Supported ModelEngine versions can supply a bounded snapshot of the visible model, bones, item-model fragments, transforms, billboards, lighting and base-entity visibility. ReplayCore records those snapshots and interpolates their animation in the dashboard viewer. Older carrier-based models continue to use their captured armour-stand or display items.
If a plugin API is absent or incompatible, ReplayCore keeps recording the vanilla entity instead of inventing custom geometry or preventing the server from starting. Validated custom blockstate variants and multipart models from the uploaded pack can replace recorded carrier blocks.
Check your result
Open a replay from the signed-in dashboard and inspect the item while held, in first-person view and from an external camera. The dashboard viewer is the supported acceptance surface for resource-pack model playback.
If an item falls back to its base appearance, confirm that the active replay scope has the intended pack, processing completed successfully, the recorded stack contains the selector your pack expects, and every referenced model and texture is present in the uploaded archive.