Skip to content

StrSheet_Item

StrSheet_Item.xml stores player-facing strings (display name and tooltip text).

Most teams define strings inline on items:

strings:
name: "Iron Sword"
toolTip: "A basic training weapon."

But you can also author strings in a standalone itemStrings section.


Entity: itemStrings
Operations: create, update, delete


spec:
version: "1.0"
items:
create:
- id: 99002
name: "iron_sword"
strings:
name: "Iron Sword"
toolTip: "A basic training weapon."
spec:
version: "1.0"
itemStrings:
create:
- id: 99002
name: "Iron Sword"
toolTip: "A basic training weapon."
spec:
version: "1.0"
itemStrings:
update:
- id: 99002
changes:
name: "Tempered Iron Sword"
toolTip: "A better crafted blade."
spec:
version: "1.0"
itemStrings:
delete:
- 99002

PropertyTypeRequiredDescription
idintYesItem ID this string entry belongs to
namestringCreate onlyDisplay name shown to players
toolTipstringNoTooltip text shown on hover

ItemStrings are commonly defined inline within item create operations:

items:
create:
- id: 99001
name: "InternalName"
# ... other item properties
strings:
name: "Display Name"
toolTip: "Item tooltip text"

The inline strings block automatically creates a corresponding entry in StrSheet_Item.xml with the same ID as the item.

For updating existing string entries or defining strings separately:

itemStrings:
update:
- id: 1
changes:
name: "Updated Iron Sword"
toolTip: "A well-crafted iron blade."

  • Don’t confuse internal vs display name: item name (in ItemTemplate.xml) is not the player-facing display string
  • Consistency: treat strings like content — review them, spellcheck them, and keep style consistent