2 loot table authoring and drop audits
forgejo-actions edited this page 2026-07-14 17:23:30 +00:00

Loot Table Authoring And Drop Audits

What This System Is

Loot table authoring defines guaranteed and weighted drops for defeated actors, while drop audits make deterministic combat rewards explainable.

How Authors Use It

Authors define loot tables with guaranteed drops and weighted drop pools. Rolls, weights, chance percent, min count, and max count determine expected output. Combat authority resolves drops deterministically and turns accepted drops into inventory grants.

Named encounters resolve the same tables through Encounter Reward Eligibility, Lockouts, And Pity. Difficulty quality may add rolls, while eligibility, pity, and owned-item conversion remain outside the canonical table so the table is not duplicated per encounter mode.

Rules And Invariants

Guaranteed drops should always resolve when the actor qualifies. Weighted drops require positive weights and sensible roll counts. Chance percent should stay within expected bounds. Count ranges must not invert. Empty item ids are invalid.

Validation And Debugging

Use loot math tests and combat reward tests when changing drop behavior. If loot appears missing, inspect the deterministic seed, table id, actor defeat record, resolved drops, and inventory grant policy.

Examples

A slime can guarantee one gel and roll twice on a weighted pool for rare drops. If the expected value is too high, lower the roll count or weight rather than adding a hidden server-side cap.