Reusing core equipment

The built-in content owner is core. Declare a core dependency in your manifest before referring to its items or assets.

Look up an existing item

local katana = sf2.items.get("core:items/weapon/weapon_katana")

The handle can be used where an item handle is expected, such as a reward, equipment rule, or item-set member. Looking up an item does not copy it or change its price, stats, or ownership.

IDs follow core:items/<category>/<item-name>. Categories are weapon, armor, helm, ranged, and magic. The registry also contains hidden/default definitions; existence in the registry does not imply that an item is normally sold.

Keep items and assets separate

Reference	What it identifies
core:items/weapon/weapon_katana	A complete equipment definition.
core:gamedata/models/mdl_weapon_katana_ritual	A model usable by a compatible new weapon.
core:ui/items/armor12.img_armor_mantle_of_night	A sprite in an existing atlas, usable as an icon.

Use sf2.items.get for items, sf2.assets.model for models, and sf2.assets.sprite for sprites. These handles are not interchangeable. See Assets and Equipment for their requirements.

Find suitable references

Every core item, model and icon ID is listed in the core catalog: Items for equipment with English names and subtypes, and Art for models and icons. Search by English name, then click an ID to copy it. Finding core content explains which lookup takes which ID.

When pairing a new item with a core model, pick a model used by core items of the same subtype, so the weapon fights with a matching moveset. Display names are translated text and are not reliable IDs; always copy the ID.

Duplicate legacy names have disambiguated IDs. The two ranged definitions named GlaivebowArrow resolve to core:items/ranged/glaivebowarrow and core:items/ranged/glaivebowarrow/riflebullet. Copy these from the catalog rather than lowercasing a legacy name yourself.