How our drop tables work

The rates on this wiki are calculated from the PrivatePS source tables and the server's TOML parser rules. They are not copied OSRS rates and they are not a measurement of a particular player's current live drop chance.

The reference profile uses the source default rate multiplier of 1.5, the general TOML chance cap of 1/2,000 and the enabled pet cap of 1/800 before the multiplier. These are distinct rules. The server rounds adjusted denominators to integers, so a rate is not always exactly its original probability multiplied by 1.5. Quantities are not multiplied by this rate setting. Code-defined drops outside these TOML tables are outside this catalogue's coverage.

A main table selects among weighted entries, including Nothing. Rare main entries receive additional weight funded by Nothing and then common entries according to the server's weighting algorithm. This differs from multiplying every displayed row by 1.5. An explicit main pool must match the resulting weights; inconsistent source pools are reported instead of silently normalized.

Separate rolls, pre-rolls, guaranteed awards and tertiary rolls are independent channels. Two independent 1/2 chances to receive the same item give a 3/4 chance of receiving it at least once, and an expected one successful award per kill. Entries within a single weighted channel are mutually exclusive and their probabilities can be added. This distinction matters for monsters with multiple rolls, such as Vorkath.

“Chance” means at least one positive-quantity award for the displayed item, quantity distribution and condition. “Expected quantity” includes every successful independent roll and its quantity distribution; expected value uses that quantity multiplied by the listed price. It is not chance multiplied by a single average quantity when more than one award is possible. A list such as 8, 10 or 12 means three discrete choices, not every integer from 8 to 12. Repeated choices retain their frequency.

Quest states, areas, Wilderness requirements, ring requirements, clue boosts and other dynamic boosts are kept as conditions. Shared gem-table results also depend on ring and NPC location filtering. Conditional nominal rates show the source route under the reference assumptions; they do not guarantee the condition is satisfied. Rows with different conditions or quantity distributions remain separate, so their displayed chances must not simply be added to obtain an overall item probability. Ring, clue and runtime configuration changes can alter actual live outcomes.

Shared tables are expanded from their Kotlin source, with their shared origin retained. Unknown shared syntax is reported rather than replaced with guessed items or rates. A Brimstone-key flag alone does not establish a key chance: the current content resolver's corresponding hook is a no-op, and the wiki therefore does not fabricate a key row from that flag.

The raw configured probability is available as a comparison with the source configuration before the house rules. It is not labelled an OSRS probability. This catalogue does not prove ground-item delivery, inventory availability, quest completion, live configuration, special code-defined loot or gameplay execution. A source-only calculation and a completed gameplay test are different evidence.