1. Begin with a primary file or official document
Microsoft's Bedrock creator tutorial explains basic pools, entries, weights, fixed or range rolls, conditions, functions, and referenced tables. Mojang's public Bedrock samples provide inspectable vanilla files. Use these as the source boundary for Bedrock behavior-pack work. For another edition or version, record that edition's exact distributed data or another suitable primary source rather than transferring a Bedrock value.
Microsoft: Creating a Loot Table
Mojang: Bedrock sample loot tables
2. Freeze the version and table identity
Record enough information for another person to inspect the same input:
- Java or Bedrock, exact release/snapshot/preview version, and platform if behavior differs;
- source archive or repository commit and verification date;
- namespace and full table path;
- vanilla, data pack, behavior pack, add-on, mod, plug-in, or server override state;
- the gameplay event that invokes the table.
3. Isolate the exact pool and eligible entries
A table may contain several pools. Identify the pool that can select the tracked entry and list every entry eligible under the stated conditions, including an explicit empty entry. Sum only the weights that compete in that same selection. A weight is relative, not a percentage by itself. If eligibility changes with context, create separate scenarios or derive the full branch probability.
4. Read rolls before applying weight math
For one fixed-roll pool with unchanged entries and selection with replacement, per-roll probability isw/W and at-least-one probability across r rolls is1 - (1-w/W)^r. This is the calculator's weighted mode. A range roll is a distribution, not merely a label: cumulative probability must average the conditional no-success probability over the actual roll-count distribution. If that derivation is not available, use a direct what-if value or separate minimum/maximum bounds.
5. Trace conditions, functions, and references
Conditions can gate a pool, an entry, or a function. Count functions can yield a range; enchantment functions can depend on the tool or context; a referenced-table entry triggers another table. These layers change either the selection probability, the resulting quantity, or both. Do not treat the visible entry weight as the final item probability until every applicable branch has been followed.
6. Separate selection, success, and quantity
“The entry was selected,” “the table call produced at least one,” and “the number of items produced” are different random variables. The calculator's success chance concerns at least one selection in a call. Its quantity field is a separate expected quantity per selection. Use 1 when you only need event probability; use a derived mean only when the exact function supports it.
7. Keep availability and route time outside the table
The table begins after its invoking event occurs. World generation, finding a structure, spawning a mob, reaching a location, combat, fishing cadence, collection, reset, and travel are separate processes. Measure a complete repeatable cycle for the same version, seed/server rules, route, gear, and player boundary. The calculator then combines that measured time with the scenario; it does not claim a universal best route.
8. Compare only compatible scenarios
Hold the table source, tracked event, quantity definition, and time boundary constant. Change one variable at a time and preserve each shared URL with its source note. If an update changes the file, start a new versioned scenario and keep the correction history instead of silently relabeling old numbers.
9. Keep a real review log
verified_on,edition,version,source_commit,table_path,pool,entry,eligible_weight,target_weight,rolls,conditions,functions,planned_calls,observed_successes,cycle_minutes,notes YYYY-MM-DD,edition,exact version,commit or archive,path,pool id,entry id,0,0,fixed or derived,describe,describe,0,0,0,record actual review
This is an empty schema, not evidence that LootCalc opened containers or reproduced a vanilla table. Never add invented observations to make a tool look tested.
Use the calculator
Enter a valid simple pool or a complete per-call probability in the Minecraft Loot-Pool Scenario Calculator, then save the URL beside the versioned source note.