Items & Equipment

The Items editor lets you create every type of item in your game. Items are used by the inventory, equipment, crafting, market, loot, and shop systems.

① Item list with search, filtering, and sort options② Multi-tab edit form: Stats, Combat, Crafting③ Live preview of item icon and stat summary

Item Types#

Weapons#

Melee — Sword, Axe, Mace, Dagger, Spear, Katana, Bat. Ranged/magic — Bow, Crossbow, Staff. Firearms — Pistol, Revolver, SMG, Rifle, Shotgun, Sniper Rifle, Assault Rifle, LMG, Rocket Launcher.

Armor#

Head, Chest, Legs, Boots, Cape, Shield, plus Accessory (rings/necklaces).

Tools (8 types)#

Axe (harvesting), Pickaxe, Sickle, Skinning Knife, Fishing Rod, Hammer, Hoe, Watering Can

Other Categories#

• Consumables — potions, food, scrolls, and single-use items
• Materials — raw resources, processed resources, and components
• Housing — furniture, decorations, and plot upgrades
• Pet & Mount — eggs, pet food, taming items, mount gear
• Farming — seeds and farming tools

Filtering the item list#

Database → Items shows one category at a time (Items, Skill Books, Weapons, Armor, Tools, Building, Chests). Inside a category, narrow the list with the two controls above the table:

The type dropdown is a multi-select:

1. Click the filter box (it reads All types when nothing is picked).
2. Type in the search box at the top of the panel to narrow a long type list.
3. Tick each type you want. The panel stays open so you can tick several — for example Food + Potion / Poison to review every consumable at once.
4. The number beside each type is how many items of that type exist in the category, so empty types are obvious before you pick them.
5. Select all ticks everything currently listed (everything matching your panel search, if you typed one); Clear or Clear filters resets it.

The box summarises what's active — one or two picks by name, more as "Food +2 more" with a count badge.

Gotchas

• An empty filter means no filter — every type in the category shows. There's no "All" checkbox to tick.
• Ticking Rune on its own opens the purpose-built Runes editor instead of the item table; same for Upgrade Material. Tick a second type (or clear the filter) to go back to the normal table.
• Runes and upgrade materials authored before those types existed are stored as Component with a rune/upgrade config. They're counted and listed under both, which is why the totals can look larger than the raw type counts.

Item Tiers#

Tier is decided by where an item enters the world, not by the item. You give each item a tier band (Min–Max) that says which tiers it may appear at, and each map a Tier. A drop then rolls a tier at or below the map’s tier. See Zone Tiers for the full system.

Two copies of the same sword can be T3 and T5, and an item never changes tier once it exists — which is why higher-tier gear only comes from higher-tier maps. Base Stats you author are the stats at the band’s Min Tier, and each tier above scales them up.

Items come in 8 tiers (T1–T8) that scale their stats. The scaling is linear with a configurable step — multiplier = 1.0 + (tier − 1) × step. The default step is 0.25, giving:

The per-tier step (weaponTierScaling) is a tunable combat constant, so the whole curve above is just the default — flatten it for a low-power game or steepen it for a big endgame gap without touching any item. See Tuning Constants.

Item Quality (authorable)#

Crafted items roll a quality bucket that further boosts stats. The buckets are creator-defined — managed in the Rarity & Quality editor (in the app sidebar), where you rename, recolor, and reorder them. The engine seeds a default ladder you can keep or replace entirely:

Higher crafting skill and better crafting stations increase the chance of rolling higher quality.

Item Rarity (authorable)#

Separate from craft quality, rarity is set on the item definition — it drives the item's name/label color, glow, and drop presentation — and a copy that drops can roll a different one (see Rolled Rarity below). Rarity tiers are fully creator-defined in the same Rarity & Quality editor:

Add as many rarity tiers as your game needs — from a simple Common/Rare split to a full Common → Mythic ladder.

Rolled Rarity (drops that come out rarer)#

A copy of an item can drop at a different rarity from the one on its definition — kill a bandit and the Iron Sword it drops may come out Exotic, stronger and in the Exotic color. You don't need a separate "Exotic Iron Sword" item for every tier.

Where to author it:

Setting it up:

1. Open Rarity & Quality and give each rarity a Drop weight (Normal 10, Rare 5, Exotic 2.5 …) and a Stat multiplier (Normal 1, Rare 1.5, Exotic 2 …).
2. Set Gear rarity roll chance to how often a gear drop should roll a rarity — 100% means every drop rolls, 0% turns rolling off. Save.
3. Optionally open an item → Stats → Rarity roll to give it its own odds.

Item fields (Rarity roll):

The editor shows the resulting chance of each rarity and the stat scale it gives, computed by the same roller the server uses.

• The stats you author are the item at its own rarity. A copy scales by rolled multiplier ÷ own multiplier: a Normal sword (×1) that rolls Mythic (×3) gets triple stats, and one that rolls Normal is unchanged. A copy can even roll below its own rarity and come out weaker.
• Only new loot rolls. Mob and NPC drops, dungeon loot and chest contents roll; shop purchases, crafted items and quest rewards always come as the item's own rarity. An item a player drops on death keeps the rarity it had.
• A rolled copy is its own item. It never stacks with a copy of a different rarity, and it keeps its rarity through trades, mail, the market, the bank and shop buyback.
• Affixes follow the rolled rarity — an affix restricted to Rare-and-up can roll on a copy that came out Rare.
• Rolling runs on the game server, so a live world picks up new odds when you Publish.

Elements (authorable)#

Weapons and abilities can carry an element that feeds an effectiveness matrix (e.g. water beats fire). Elements and their matchup rates are creator-defined in the Elements editor — they're not a fixed list, so you can build whatever affinity system your game needs.

An element applies to a hit from whichever source carries it: the ability's element, or — for a basic weapon attack — the equipped weapon's. Either way the same element drives all three outcomes: the effectiveness multiplier, any status procs bound to that element, and the damage number, which is tinted with the element's authored color and tagged WEAK / RESIST / IMMUNE / ABSORB.

Equipment Slots#

Characters have 11 equipment slots:

An item's Type picks its slot automatically: Armor Head → Head, Armor Chest → Chest, Armor Legs → Legs, Armor Boots → Boots. Legs and Boots are separate slots, so a character wears leg armor and footwear at once.

Handedness — which pose a weapon is held in#

On a weapon's Combat tab, Handedness has three settings:

Set this per item, not per weapon type: a hand axe and a greataxe are both axes, and a rapier and a greatsword are both swords. Without it, every axe in the world would stand and swing two-handed while every sword stayed one-handed.

Handedness only retunes the melee 1H/2H pair. Bows, firearms, staves and polearms keep their own stances — those weapons already have a real grip built into their animations, so marking one "two-handed" changes what it blocks in the off hand but not how it is held.

Use & Equip Requirements#

Any item can gate itself behind what a character has earned. Open the item and find the Use & Equip Requirements section (the 🔒 panel). Blank means no requirement.

Requirements are checked on the server for both equipping gear and using/consuming an item (potions, food, scrolls). The player gets the first unmet requirement back as a message that names the skill and the level they currently have — "Requires Axe Skill level 2. You have 1."

Gotchas

• A requirement pointing at a deleted skill is ignored, not enforced. If you delete or rename a skill after gating an item on it, no player could ever satisfy that gate, so the engine drops it rather than making the item permanently unequippable. The server logs a warning naming the item and the missing skill.
• The editor shows such a stale gate as ⚠ Missing skill: <id> in the Required Skill dropdown. Repoint it at a real skill or set it back to — None — to clear it.
• Skill ids are matched loosely on case, so an item authored against AXE still resolves to a skill called axe. Two skills whose ids differ only by case are ambiguous and won't resolve — give them distinct ids.
• Requirements are a gate, not a hint: the player only learns about them when they try. Say so in the item's description if it matters.

Gathering Tools & Auto-Equip#

A resource node can demand a tool: an axe for a tree, a pickaxe for a rock, a fishing rod for a fishing spot. The tool has to be in the player's Tool slot. With auto-equip on (the default), a player who walks up to a tree with the axe still in their bag doesn't get told off — the game takes the right tool out of the bag, puts it in the Tool slot, says "Equipped Iron Axe." and starts chopping.

Where to author it:

Setting it up:

1. Give each node its Tool Type and Min Tool Tier. A tool works one tier below the minimum (more slowly), so a Min Tool Tier of 4 accepts a Tier 3 tool.
2. Make tool items of the matching type (Tool Axe, Tool Pickaxe, …) — they equip into the Tool slot on their own.
3. Leave Auto-Equip Gathering Tools on, or switch it off in Combat → Itemization and Save & Apply if your world wants players to manage the Tool slot by hand.

Which tool gets picked:

If the tool in the Tool slot already works on the node, nothing changes — auto-equip never swaps a working tool for a "better" one. If a tool breaks halfway through a node, a spare from the bag goes on and the gathering carries on at the spare's speed (the blow in progress starts over). Whatever the player puts in the Tool slot themselves halfway through is their choice and is never undone: another tool that works on the node simply takes over at its own speed, and taking the tool off — or putting on one that can't work the node — stops the gathering.

What the player sees when nothing fits:

The message names what is missing. The tool is named the way your Tool Type reads (a Skinning Knife node says skinning knife), and a tier only appears when the node refuses Tier 1 tools (a Min Tool Tier of 3 or more, since a tool one tier under the minimum still works).

All of these are server messages, so you can reword or translate them on the Localization page: filter the Server Messages namespace for keys starting harvest..

Gotchas

• The game picks the tool, never the player's client. The client can only say "don't auto-equip for me"; it never names a tool, so a modified client can't make the server equip something else, or anything the player couldn't equip by hand.
• Equipping in combat follows the normal rule. Equipping by hand isn't blocked in combat, so auto-equip isn't either.
• A player can only switch it off, never on. The player setting has no effect in a world where Auto-Equip Gathering Tools is off. If your world turns it off, hide the player row in Settings → UI / HUD → Panels → Settings so it doesn't promise something the world won't do.
• The player's choice follows their account. Settings → Gameplay → Auto-equip gathering tools is saved with the player's other preferences, so it is the same on every device they play on.
• Needs an up-to-date game server. An older server still equips a tool from the bag, but only the highest tier (not the freshest), only when the Tool slot is empty, broken or holds the wrong kind (not when it is too low a tier), never mid-node, and it ignores the player setting. Managed servers pick up the new version when they next restart while empty.

Creating a Weapon#

When creating a weapon in the editor, you configure:

• Name, description, icon — what the player sees
• Type — sword, bow, staff, etc.
• Tier — a minimum and a maximum tier
• Weapon type — ties the weapon to its basic attack, its Q / W abilities and its attack animation (see below)
• Handedness — one-handed, two-handed, or inherited from the weapon type
• Stat bonuses — additional stats when equipped
• Weapon Unique Ability and passive options — the ability on E and the passives this weapon offers (Advanced tab)

A weapon has no damage type, base damage or scaling of its own. Those belong to the abilities it uses: every ability sets its own Damage Type, Base Damage, Scaling Stat and Scaling Ratio (see Abilities & Skills). A weapon makes those hits stronger through its stat bonuses — a sword with +20 Attack raises every ability that scales with Attack. To make a staff deal magic damage, give its weapon type a normal attack ability whose Damage Type is Magic.

Weapon Types & the Unarmed default#

Weapons are linked to a weapon type (managed under Items → Weapon Types) that defines how the weapon behaves and animates, separate from the weapon item's own stats. Each weapon type carries:

• Animation category — which attack animation plays (slash, thrust, crush, bow, sidearm, rifle, cast, or unarmed)
• Normal attack ability — the basic left-click attack
• Q / W abilities — the two weapon-bound abilities on the action bar
• Base attack speed and grip

Attack range and damage type are not set on the weapon type: both come from its normal attack ability.

Point a weapon item at a type via its Weapon Type field; when equipped, the weapon contributes its type's normal attack + Q/W abilities and animation to the character.

Unarmed (the default fighting style)#

There is a built-in Unarmed weapon type that can't be deleted — only edited. It's the empty-handed default: when a character has no weapon equipped, the Unarmed type drives their basic attack (left-click), Q/W abilities, and attack animation, exactly like an equipped weapon. Set the fists animation and a punch ability on it under Items → Weapon Types → Unarmed. (Leave its normal attack blank and players fall back to a built-in punch, so they always have a basic attack.)

Creating Armor#

• Weight class — Light, Medium, or Heavy
• Base defense / magic resist — flat damage reduction
• Stat bonuses — additional stats when equipped

Ability & Passive Choices (player loadout)#

A weapon, armor piece, shield or cape can offer several abilities per slot and several passives, and each player slots the ones they want — one sword type can give a choice of three Q abilities, a helmet a choice of two, a cape a choice of passives. A slot with a single option works exactly like a fixed ability, so nothing changes until you add a second option.

Where to author it:

Setting it up:

1. Open Items → Weapon Types and edit a type (for example your Blade type).
2. Under Ability Slots, add abilities to Weapon Ability 1 — the first one you add is the default a player has until they choose. Add a second (and third…) to give players a choice.
3. Optionally add passives under Passive Options — one is always held while the weapon is worn; two or more become a choice.
4. Do the same for armor under Items → Armor Types: each piece (Head, Body, Boots, Off-hand, Cape) has an ability list and a passive list.
5. To give one specific item its own options, open the item → Advanced and fill its Weapon Unique Ability (E) or Slot Ability list — an item's own list replaces its type's list for that slot.
6. Save, then publish. In game, players open the item's details (click it in the bag or on the paper doll) → Abilities tab and click the option they want.

Fields:

In game: the item window's Abilities tab shows one row per slot with every option (icon, name, description on hover) and the one in effect highlighted. Clicking another option slots it straight away and the ability bar updates. The choice is remembered for the weapon type or armor type (or for the item, when the item has its own list), so picking a Q ability on one sword applies to every sword of that type.

Earning stronger options (unlocks)#

Options after the first are earned, weapon-mastery style. Each ability option unlocks when the player meets that ability's own requirements — the same ones that gate learning it from a trainer or a skill book. Each passive option unlocks at that passive's Gear Unlock skill level. You build the ladder in the ability or passive itself, not in the item.

1. Open Abilities → (the stronger ability), and under Learning Prerequisites set Required Skill and Required Skill Level (for example Swordsmanship 10). Optionally set Required Ability / Additional Prerequisites — abilities that must be learned first.

   For a passive, open Status Effects → Passives → (the stronger passive) → Basics, and under Gear Unlock set Required Skill and Required Level.

2. In the weapon type / armor type / item option list, put the ungated ability or passive first and the gated ones after it. Each gated option shows "unlocks at Swordsmanship 10" under the list so you can see the ladder.
3. Publish. In game, locked options appear greyed out with a padlock and "Requires Swordsmanship 10"; they become choosable the moment the player reaches that level (the Abilities tab refreshes on level-up).

Gotchas

• A gated ability or passive as the first option is handed out for free. The content check warns "the first option … requires …" and the option list shows it in amber — move an ungated option to the top.
• A passive's Gear Unlock only gates the gear picker. The same passive granted by a skill level, a skill book, a quest or an event command is granted as usual.
• A slotted option that becomes locked (you raised its requirement, or the player's skill dropped) quietly falls back to the first option; the player's choice is remembered and comes back once they meet the requirement again.
• Choosing a locked option is refused by the server with "Locked — requires Skill level." — the picker can never be used to skip a requirement.
• Choices can only change out of combat. In combat the Abilities tab is greyed out and the server refuses the change with a message.
• Only worn items show their options. A weapon or armor piece in the bag shows "Wear this item to see and choose its abilities" — equip it first.
• Items offering a single option are unchanged. The editor stores a one-entry list as the plain ability it always was.
• An option naming a deleted ability or passive is refused on save, and flagged by the content check; while it is the one in effect the slot is empty.
• A slot may offer at most 8 options.
• A chosen passive is held only while the item is worn — unequip it (or pick another) and the passive, with any status effects it holds open, comes off.
• Item power and skill XP still come from the item that grants the chosen ability.
• Feature flag: Ability Loadout Choice (on by default). Off: every slot uses its first option and the Abilities tab is hidden.

Equipped Appearance (Visuals tab)#

Weapons and armor show on the character exactly like characters, mobs, and NPCs do — through a saved sprite asset. On the item's Visuals tab, the Equipped Sprite Asset field shows a live preview of the current sprite and opens a visual gallery instead of a name list:

The Avatar & Sprite Editor sits right under that field, in the item form — the same editor the character, mob, pet and mount editors use. Import a sheet, set the frame grid, add animations, map directions and recolor, all without leaving the item. Its Use a saved sprite… list does the same thing as Choose above: pick a row and the item uses that saved sheet straight away — there is no Load button on an item — and the editor edits it in place. The list always shows the sprite the item is using, so it is not empty when you reopen the item.

Sheet edits are written when you press the item's Save Changes, so one save covers both the item and its sheet; the Save sheet button next to the sheet name writes it immediately if you'd rather. An Unsaved marker appears while the sheet has pending edits. Editing a sprite asset changes it everywhere it's used, so duplicate it first if only one item should change.

The Unsaved marker only appears when saving will really write the sheet. A sheet with no image is never saved, so if you name it or pick a layer before choosing a sprite the marker reads Not saved yet — pick a sprite or a sprite sheet first. If the sheet has unsaved changes and you choose a different sprite (gallery, list or ✕), the editor asks before dropping them.

While the tab loads: the field reads Loading sprite… until your sprite library has been read, and the sheet editor appears once it has. If the library can't be read you see Sprite not shown and a Retry button — the item's sprite is still set and nothing was lost.

The item editor counts those sheet edits as unsaved changes too: its footer reads Unsaved sprite sheet changes, and it asks before you close it, switch to another item or leave the Database section. If you choose to discard and switch, the sheet edits are thrown away with the rest.

Gotcha: equipment overlays must be authored against the same frame size and animation layout as the player sprite — the engine drives the overlay with the body's current frame, so a mismatched grid will look misaligned.

Worn gear has no size setting. It is drawn at its wearer's size, each frame fitted over the body's frame, so on an item the editor shows a note where characters and mobs have In-World Scale. To make a piece look bigger or smaller on the character, draw it bigger or smaller inside the sheet's cells.

Body Type, Race & Character Variants#

Armor and weapon sheets are cut against a specific body — a chestplate drawn for a male frame won't sit right on a female, kid or non-human frame. When your world has more than one playable body, give the item variants instead of forcing one sheet to fit everyone.

Below the Equipped Sprite Asset field, use Body Type, Race & Character Variants:

1. Click + Add variant.
2. Choose who the row is for — any mix of Body type, Race and Character. Leave a field on Any to not care about it.
3. Pick the sprite asset those wearers should see — the same visual gallery and embedded sprite editor as the default field, including None — hidden to hide the item on them only.
4. Save the item. Add a row for each body that needs its own cut.

How it resolves in-game, per wearer: every field a row sets must match the wearer, and the most specific matching row wins — a Character match beats a Race match, which beats a Body type match, and a row combining fields beats each of its parts. So adult-fem alone dresses every female hero, while Elf + adult-fem overrides it for elven women only. No match → the Equipped Sprite Asset → nothing on the body for worn gear, or the item's icon as a held prop for a weapon, shield or tool.

Gotchas: rows that name no body type, race or character — or have no sprite — are drafts and aren't saved; two rows with the same match keep the first. Body type and race come from the character creator, so they only match heroes built there. NPCs wearing gear use the default sprite. The character select screen dresses heroes with the same rules.

Worn as a Generator Piece#

If your heroes are built from a character creator pack (for example the RPG Maker MZ generator) and your armor is cut from that same generator's parts, a plain overlay looks wrong: it covers the hair, and the outfit the player picked in the creator shows through underneath. Mark the equipment sprite as a generator piece instead.

1. Open the item's Visuals tab and edit its equipped sprite (or open it in Sprites).
2. In the sprite editor, set Worn as generator piece to the part the sheet was cut from.
3. For a Cloak, also pick the Behind-body sheet — the generator ships a cape as two sheets, one drawn in front of the body and one behind it.
4. Save. Add body-type variants (above) so each body wears the sheet cut for it.

Gotchas: the sheet must use the same grid as your heroes' bodies (an MZ part is 3 × 4 frames of 48 px) — leave its animation list empty and it follows the body frame for frame. Accessory items only draw when they have an equipped sprite, so rings and necklaces never show their icon on the character. Heroes not built from a creator pack still draw the item over the whole character.

Cosmetics (Wardrobe)#

A cosmetic changes how a slot looks without touching stats — the classic item-shop outfit. A player equips it like any gear, but it goes into their wardrobe instead: their real armour stays on and keeps giving its stats, and the cosmetic's look is drawn in its place.

1. Open Items, pick (or create) a head, chest, legs, boots, cape or accessory item.
2. On the Visuals tab, tick Cosmetic.
3. Give it an Equipped Sprite Asset (and body-type variants if it's body-cut) — that sprite is the whole point of the item.
4. Leave its stats empty; cosmetics never add any.
5. Save, then sell it in the Premium Shop or hand it out as a reward.

In game, players wear cosmetics from the Cosmetics row of the Character window (and the Wardrobe row under the equipment in the Inventory — the same six slots):

1. Open the Character window. Under the equipment is Cosmetics: Head, Chest, Legs, Boots, Cape and Accessory.
2. Click a slot. It lists the cosmetics in the bag that fit it.
3. Click one to wear it. The gear underneath stays on and keeps its stats.
4. Double-click a worn cosmetic, or click it and choose Take off, to return it to the bag.

Equipping a cosmetic straight from the bag still works and lands in the same slot. The character's portrait in the window, the character in the world and the character select screen all show cosmetics.

The row is a section of the Character window like any other: UI / HUD Editor → Panels → Character → Sections → Cosmetics (wardrobe) hides it, moves it or gives it a background. In a world with no cosmetic items the row is not drawn at all.

Gotchas: weapons, tools, pets and mounts can't be cosmetics — their look drives stances and swings. A cosmetic with no equipped sprite hides nothing and draws its icon, so always give it a sprite. Taking one off needs a free bag slot.

Common Item Settings#

Every item also supports:

• Max stack — how many can stack in one inventory slot
• Tradeable — whether players can sell or trade it
• Light emission — optional glow effect (color, radius, intensity)
• Sell price — gold value when sold to NPC shops

Status Effects & Procs (Skills & Effects tab)#

Items → (an item) → Skills & Effects → Status Effects & Procs. Each row puts a status somewhere at a chance, and its When column decides when:

1. + Add Effect, pick the status (or leave it blank for a rule-only row).
2. Set When: On hit (on your target), On use (on you, when consumed),

   While equipped (held on you while worn), or any combat event — I am hit, I kill something, A hit would kill me…

3. Set the Chance (1 = always).
4. Optional: Rule adds every-Nth, an internal cooldown, filters and more

   actions — cast an ability, reset a cooldown, change the hit, cheat death.

Capes, off-hands and trinkets use this for their procs. See Triggers for every event and action, and the Combat Triggers feature flag.

Throwing (potions, bombs, poisons)#

Items → (pick an item) → Throwing.

A consumable with a Throw Range can be thrown instead of drunk. There are two kinds of throw:

• At a unit (the classic throw): the potion's own restore values land on the unit

  you have selected — heal an ally, poison a wolf.

• At a spot — a thrown potion: pick On landing, cast ability and the item

  flies to where you aim and casts that ability from the spot it lands, with you as the caster. A firebomb that leaves a burning patch, a flask that bursts into a healing circle.

Making a thrown potion#

1. Create the landing ability first. For a healing circle: Database → Abilities →

   Healing Spring, and on Costs & Effects → + Add action → Spawn area set At to Landing, a radius, a duration and a Pulse ability that heals.

2. Open the potion item → Throwing.
3. Set Throw Range (tiles) above 0.
4. Pick On landing, cast ability → Healing Spring.
5. Save, put the potion on the hotbar, and in game press its key with the cursor where

   it should land.

Gotchas#

• Throw it from the hotbar. The throw goes where your cursor is; used from the

  inventory window (where there is no aim) it goes to your selected unit's spot, and with nothing selected it is refused and stays in your bag.

• A thrown potion is never drunk. Its restore values (HP, MP, hunger…) do nothing —

  the landing ability is its whole effect.

• The landing ability must exist. The editor refuses a save naming a missing

  ability, and the game refuses the throw if one goes missing later.

• Needs a Throw Range above 0 (the tab warns you) and the Ability Stages flag

  (on by default). Off, the item throws at a unit the classic way.

Item Affixes#

Base items can roll prefix/suffix affixes — think "Superior Iron Sword of Health" — so the same base item drops with meaningful variation. Affixes are authored in the dedicated Affixes editor (in the app sidebar), separate from items, and applied per-item through the item editor's Affixes tab.

Affix definitions#

Each affix is a reusable definition:

Per-item roll config#

On each item you enable affixes and set the roll rules:

• Allowed affix IDs — the pool this item can draw from
• Max prefixes / max suffixes — how many of each can roll
• Roll chance — probability (0–1) that any affixes roll at all
• Roll timing — roll on drop (baked into the loot) or on pickup

The rolled affixes are stored on the item instance and become the source of truth for its display name and tooltip. The same deterministic roller runs server-side (real drops) and in the editor's "possible outcomes" preview, so what you preview is exactly what players get.

Nothing is rolling affixes?#

A new world ships with no affix definitions at all — until you author some in Items → Affixes, every drop is plain, no matter what an item's roll config says. An item's settings choose from a pool; they can't create one.

Once affixes exist, four things can still empty the pool for a given item. The server names the one it hit, once per reason, in its log:

An affixed item on the ground still shows its base name — the prefix/suffix appears once it's in a bag, because that's where the instance lives.

Running locally? The local game server keeps its own copy of the database, cloned from the editor's the first time it starts. After that it only learns about new content through a live sync — which needs the server to be running when you press Save. Author affixes with the server stopped, then launch it, and it starts with the pool it had before. Either keep the server running while you author, or start it once with PGLITE_SERVER_FORCE_RECLONE=1 to re-clone the editor's database. Its boot log states what it actually loaded:

Copy

[GameData] Loaded … 9 affixes @ 1 gear-drop chance

Loot Tables#

A loot table is a named list of possible drops that mobs, chests and resource nodes point at, so "what a wolf drops" is authored once and reused everywhere.

Where to author them: Items → Loot Tables. The same editor appears inline on Mobs → (a mob) → Loot for drops unique to one creature.

Building a table#

1. Open Items → Loot Tables and click New Loot Table.
2. Give it a Name and Description — the id is generated from the name.
3. Fill it with drops. Four ways, covered below: Add Items…, Blank Row, Paste list…, Copy from….
4. Tune the rates — each row has a slider and a percent box, or select rows and use the bulk bar above the list.
5. Check the Roll preview at the bottom. It rolls the table exactly the way the server does, so what you see is what players get.
6. Save, then Publish so the live server picks the table up.

One drop out of many (pick groups)#

Every row normally rolls its own chance, so a table can drop several items at once — or nothing. To make a set of rows drop exactly one of them, give them the same Pick group name:

1. Tick the rows (or type into each row's Pick group box).
2. Type a name such as gear into the bulk bar's Pick group and press Apply.

Rows sharing a group are one roll: the group drops with a chance equal to its rows' chances added up (capped at 100%), and then gives one of them, weighted by those chances. Two hundred rows of 0.5% each drop one random item every time; the same rows at 0.25% drop one half the time.

• Rows without a group keep rolling on their own, next to the group.
• A table can hold several groups — gear and gem each give their one item.
• On a mob, a loot table's groups stay that table's own, so two assigned tables that both use gear still roll separately.
• Loot find (the passive) gives its extra look to ungrouped rows only; a group has already chosen its item.
• Works on mob loot, loot tables and treasure chests alike.

Adding a lot of drops at once#

A project with hundreds of items makes one-at-a-time picking painful, so the editor has three bulk routes:

+ Blank Row is still there for adding a single drop by hand.

Tuning a lot of rows at once#

Every row has a tick box. Tick some to target them — with nothing ticked, the bulk bar applies to the whole table.

Fields on a row#

Gotchas#

• Chances are not shares of a pie. Every row rolls independently, so they do not need to add up to 100% — a table of ten 50% rows drops about five items every kill.
• The same item on two rows rolls twice. The real drop rate is higher than either row reads. The editor warns you when it spots a duplicate.
• A 0% row can never drop, and a row whose max is below its min quietly drops the min only. Both are flagged above the list.
• Fill by rarity needs rarities to be worth filling. An item with no explicit rarity falls back to the one its tier implies, exactly as the game does — and if that tier points at a rarity you never authored, the row is treated as your most common one. If every rarity has the same Drop weight, every row gets the same chance, so tune the weights under Items → Rarity first. With no rarities at all the control is replaced by a note telling you where to author them.
• Row ticks are positional. Reordering, deleting or adding a row clears the selection, so a bulk edit can never land on rows you did not mean.
• Pasting never silently drops a line. Unmatched lines are listed under the box before you commit. Check that count — a typo'd name is the one way a table ships missing a drop nobody notices.
• Chance columns accept 5%, 5 or 0.05 — all the same 5%. Rows pasted with no chance column land at 25%.
• Publish after saving. A saved table is not a live table until the world is published.

Equipment Loadouts#

Players can save named equipment builds and swap to them in one action instead of hunting through the bag. A loadout records the definition for each slot (plus consumables), and equipping it resolves the best copy the player actually owns — ranked by equipment level, then equipment XP, then quality and affix strength, then newest. Swaps go through the normal equip pipeline (so restrictions, requirements and stat recalculation all still apply) and report per-slot results plus any consumables the player is short of. Equipping is locked during combat.

Buying the missing pieces#

A build is only half-useful if the player doesn't own it yet, so the Loadouts panel can shop for them. Buy missing prices every piece the build calls for that isn't worn and isn't in the bag, shows a per-piece breakdown and a total, and buys them all on Buy all.

Where each price comes from, in order:

Consumable picks are quoted by shortfall: a build asking for 10 potions when the player has 4 quotes 6.

Nothing about this is authored — it works from the shops and market you already have. What you author changes what it finds:

1. Give vendors stock for the gear your builds use (NPCs → Shops → Stock). Only a shop the player is actually standing at and has open can be quoted from — a closed shop, or one they walked away from, drops back to the market.
2. Shop opening hours and stock sets apply as normal; a piece a shop only sells in winter quotes from the market in summer.
3. Everything else comes from live player listings, so a healthy market is what makes rarer builds buyable.

Things worth knowing:

• Quotes reserve nothing. Prices are re-checked the moment the player confirms, so nobody can quote-and-hold to lock a listing away from other buyers.
• Prices that move are refused, not absorbed. If the true total comes back more than 5% over what the player was shown, nothing is bought and they get a fresh quote to confirm again. Their silver never leaves without goods.
• Partial success is normal. Each piece is bought on its own through the ordinary shop/market purchase — a listing sniped mid-purchase fails that piece and the rest still complete. The result lists what was bought and what wasn't.
• Buying is not the same as equipping: the pieces land in the bag, then Equip puts the build on.
• Turning the Equipment Loadouts flag off hides the whole panel and rejects both the quote and the purchase.

Loadout Kits#

A loadout kit is a named gear bundle you author once and any NPC vendor can sell as a single purchase — "Recruit's Kit", "Miner's Starter", "Arena Loaner". The buyer pays one price, receives every piece at once, and can put the whole build on with a second click. It is the fastest way to get a new player dressed, and the cleanest way to hand out a fixed set for arena or tutorial play.

Where to author them: Items → Loadout Kits. Where to sell them: NPCs → Shops → (a shop) → Stock.

Building a kit#

1. Open Items → Loadout Kits and click New Kit.
2. Give it a Kit name — this is what the shop card says, so write it for players ("Recruit's Kit", not "kit_01"). The id is generated from the name.
3. Add a Description and Bundle art. Both appear on the shop's kit card.
4. Under Gear, click Add slot, choose the equipment slot, then choose the piece. The item picker only offers items that actually equip into that slot, so you cannot file a helmet under boots.
5. Optionally add Consumables — potions, food, ammo. Each row is an item plus how many of it the buyer receives.
6. Optionally fill the Hotbar preset. When the buyer equips the kit, these abilities are placed on their hotbar.
7. Click Validate to dry-run the kit (below), then Create Kit.
8. Go to NPCs → Shops, open the vendor that should sell it, switch to the Stock tab, set Sells to Loadout kit, pick your kit, and add it.
9. Publish, so the live game server receives both the kit and the stock row.

Fields#

On the shop's stock row the ordinary stock fields all still apply to a kit:

Validate before you ship#

Validate checks the kit against your live data and writes nothing. It reports:

Saving runs the same check, so a kit that can never be worn never reaches a shop.

Things worth knowing#

• Buying is all-or-nothing. The server proves the buyer has room for every piece before charging them, so a full bag refuses the purchase instead of voiding half a kit.
• A broken bundle refuses to sell. If any piece has been deleted since you published, the vendor turns the purchase down rather than handing over less than the card advertises.
• Deleting a kit removes it from every shop that sold it — no vendor is left with an unbuyable shelf entry.
• Auto pricing is a sum, never a discount. If the bundle should be cheaper than its parts, set Fixed.
• Buying is not equipping. The pieces land in the bag; equipping the kit runs the ordinary loadout equip path, which re-validates every piece and is still locked during combat.
• Publish is required. A kit authored while your game server was offline reaches it on the next Publish, along with the shop that sells it.
• Turning the Equipment Loadouts flag off stops kits being sold.

Item Timeline#

Item instances carry a history, not just stats. The timeline records:

This is what makes a specific sword that sword — a piece with a history reads differently on the market than a freshly crafted one.

Rarity & Quality#

Rarity and quality are two independent, fully authorable axes, edited from tabs on the Items page:

A quality's stat multiplier actually scales the item's stats when equipped, so a Masterpiece sword really is stronger than a Normal one. Both lists are ordinary authored data — add, rename, recolor, or delete tiers freely; the crafting roll, inventory sorting, and item tooltips all read your rows.

How Loot Looks on the Ground#

Drops are readable from across the screen without opening anything:

• Floor items are tinted by rarity, and rare-and-above tiers raise a rarity-colored light beam
• Light-emitting items (torches, glowing gear) cast their light where they land
• Killed mobs scatter their drops in a spiral around the corpse instead of stacking on one tile
• Mob silver drops as a physical coin pile the killer can pick up (with their premium multiplier applied), not a silent wallet credit
• Inventory slots draw a rarity ring and glow so the tier reads at a glance

What happens to items players already own when you delete or restore an item#

Deleting an item takes it out of your game, but it does not destroy the copies your players already own. Their copies are put aside, untouched, and come back by themselves if you restore the item. You do not have to do anything, and neither do they.

Where: Database → Items to delete (the confirm tells you what will happen in your project, see below), and Database → System → Trash to restore.

What the delete confirm tells you#

Every time you delete an item, the confirm first checks your project's game server and database, then tells you what happens to the copies players hold. You will see one of these lines:

What players see#

1. You delete the item. Nothing is removed from the saved game: each copy keeps its place, its quantity, its upgrade level, its runes and its affixes. Players who are offline simply do not find it in their bag, equipment or wardrobe at their next login.
2. Players who are online at that moment still see the item until they log out; from their next login it is put aside like everyone else's. A chest keeps listing it until the server next restarts.
3. Players carry on. Once the item is put aside, the slot it was in looks empty and they can use it for something else.
4. You restore the item from the Trash. Players who are online get their copies back straight away; everyone else gets them at their next login. Chests get theirs back at the same moment.

Where a returning item goes#

Gotchas#

• The Trash keeps a deleted item for 30 days. After that you cannot restore it, and the copies players hold stay put aside for good. Re-create the item with the same ID to bring them back.
• Two stacks are not merged. If a player earned more of the item after you restored it but before they logged in again, they end up with two stacks.
• A chest that still holds put-aside items cannot be picked up. The chest looks empty, but the player is told it still holds items that are unavailable. Restore the item, then pick it up.
• Mail still expires. A mail holding a deleted item runs out on its normal timer like any other mail, attachment included.
• This is about deleting an item. Deleting a character still deletes everything it owns.
• The item does not vanish from a bag that is open. A player who is online when you delete it keeps seeing it until they log out, and a chest keeps listing it until the server restarts. Nothing is lost either way: the copy is put aside at the next login or restart.
• Your live server has to be up to date. A game server that has not yet updated to the release that introduced this still removes players' copies when it receives the delete. The confirm checks this for you and says so before you delete. Managed servers update by themselves when nobody is online; if you host your own, update it before you delete an item players may hold.
• Read the confirm each time. The line can change between two deletes: it is checked again whenever the confirm opens, so it turns into "players keep their copies" as soon as your server has updated.
• The server counts what it kept. Your server's /status address has a keptItems entry — see Content Checks.
• There is no feature flag — this is always on.