1. Start with Digital Extremes sources
The official PC drop tables are the primary numeric source for current reward entries and percentages. Digital Extremes' Relic Hunting 101 says each Relic has a unique possible reward set, refinement raises the chance of rare rewards, and opening the same Relic with squadmates improves the chance of a rare result. The current Prime path says squad play lets a player choose from squadmates' rewards.
These sources support a target-availability calculation. They do not supply LootCalc with a permanent trading dataset, universal completion time, or an objective value for a player's resources and time.
2. Freeze platform, build, and verification time
Record platform, client build or update, region when relevant, verification date, and local time. “Current” is not a version. Keep a screenshot of the in-game reward screen or the exact official table entry. When an update changes a reward set or percentage, preserve the old record and create a new scenario.
3. Name one exact target
Use the full reward name. “Rare part,” “Prime item,” or a color bucket can contain multiple outcomes and cannot identify the percentage for one target. If you care about two rewards, calculate and log them separately unless you can establish that their events are mutually exclusive and deliberately build a combined model.
4. Record every Relic shown in the same completion
For each participant whose Relic will reveal a selectable reward, record the exact Relic and refinement shown in game. Mixed setups are valid inputs; they simply require separate target probabilities. If one Relic cannot reveal the chosen target, enter zero for that Relic instead of replacing it with another member's chance.
5. Copy one current target probability per Relic
Copy the target's percentage from the official table or current game UI. Do not infer it from the refinement name, rarity color, number of rewards, an old article, or another Relic. Store the source URL or screenshot path beside the value. A percentage without target, Relic, refinement, build, and date is not reusable evidence.
6. Declare the independence assumption
LootCalc combines the entered reveals as independent events. This is a mathematical scenario assumption, not a quoted Digital Extremes claim. If a special event, Relic family, mission rule, or future update links the outcomes, the complement formula is not justified until that dependency is modeled from a suitable source.
7. Audit the one-run complement formula
- convert every entered percentage
pᵢto a probability from zero to one; - the chance that a particular Relic does not reveal the target is
1 − pᵢ; - under independence, the chance that none reveal it is
∏(1 − pᵢ); - the chance that at least one reveals it is
1 − ∏(1 − pᵢ).
This result means the target is available among the displayed rewards. It does not mean multiple copies can be selected in one completion, and it does not describe acquiring the Relics before the Fissure.
8. Keep repeated runs unchanged
For one-run target availability p and r unchanged runs, at-least-one probability is1 − (1 − p)^r. Expected target-available runs are r × p. If any participant, Relic, refinement, target, eligibility, or selection rule changes, split the plan into homogeneous blocks instead of applying one probability to the entire session.
9. Read expectation and thresholds correctly
Expected runs to first availability are 1 ÷ p. This is a long-run mean, not a guarantee. A 90% threshold means nine out of ten comparable hypothetical plans would contain at least one target-available run; it does not make the next run more likely, reset randomness, or create bad-luck protection.
10. Measure the full opening cycle
Start the clock before group assembly or the first setup action you intend to compare. Include recruitment, Relic selection, matchmaking, loading, Reactant collection, mission objectives, reward selection, extraction, inventory work, interruptions, failures, and reset to the same starting boundary. Report completed runs and failed or abandoned attempts separately. A mission-only stopwatch is not a full acquisition clock.
11. Separate Relic acquisition from Relic opening
The official drop tables can also describe where a Relic enters a mission reward table, but that is a different probability stage from opening the Relic. A complete end-to-end model would need the exact source mission, rotation, eligibility conditions, chance of acquiring the required Relic, acquisition time, opening time, and target reveal chance. Do not multiply unrelated percentages until their conditional order and denominators are explicit.
12. Compare one controlled change
Save a baseline URL, duplicate it, and change one factor: a participant's current probability, the number of unchanged runs, or measured full time. If the target, Relics, refinements, group, source, and timing boundary all change, the outputs describe two plans but cannot identify why they differ. Do not label the larger number optimal unless you define the objective and evaluate all relevant costs and alternatives.
13. Keep a real observation log
verified_on,platform,client_build,target_reward,participant_1_setup,target_chance_1,participant_2_setup,target_chance_2,participant_3_setup,target_chance_3,participant_4_setup,target_chance_4,planned_runs,completed_runs,failed_or_abandoned_runs,target_available_runs,full_batch_minutes,source_or_screenshot,share_url,notes YYYY-MM-DD,platform,exact build,target,exact setup,0,exact setup,0,exact setup,0,exact setup,0,0,0,0,0,0,path or URL,URL,record real observations only
This is an empty schema. It is not evidence that LootCalc opened Relics, measured a route, validated a market, or observed any target frequency. Never add illustrative rows to a file presented as collected gameplay data.
14. Preserve correction history
Earlier LootCalc pages embedded a fixed refinement table, assumed reward-slot splits, static currency values, fabricated route observations, prescriptive farming statements, and speculative market cycles. Six overlapping articles and two fake CSV logs were retired. If a future source supports a new mechanic, add one evidence-ledger record per claim and extend the model only to the exact boundary that source establishes.
Use the calculator
Enter the current values in the Warframe Relic Squad Probability Calculator, then save the URL beside the source capture and observation log.