Live market signal
Recent community price data, cached briefly and still subject to in-game movement and fill risk.
KNOW WHAT EACH NUMBER MEANS
Four evidence levels. One visible standard.
LootPath separates facts by how they are produced. The label beside a tool tells players whether the result comes from a live external feed, a deterministic formula, a reviewed reference set or an illustrative planning model.
Editorial review
Exact formula
A deterministic calculation such as the RuneScape level-to-XP curve; rates layered onto it remain estimates.
Curated or illustrative
A transparent comparison baseline that must be verified against current requirements, prices and player execution.
01
Live market signals
The market tools request latest high and low transaction signals from the OSRS Wiki real-time prices service. LootPath revalidates the selected watchlist on a five-minute server cache. These values are community-collected observations, not an official Jagex order book and not a guarantee that an offer will fill at the displayed level.
Market calculators show the visible gross spread and a tax-aware estimate. Position sizing remains the player's decision. One-item tests, current buy limits, trading volume and available bank liquidity belong in the final check.
- Every row is labelled live, stale or unavailable.
- The in-game Grand Exchange remains the final execution source.
- A cached transaction can be newer or older than the next available offer.
02
Official Hiscores lookups
The Hiscores tool sends a player name to LootPath's server route, which requests the official Jagex Old School RuneScape Hiscores JSON endpoint. Successful responses are displayed as returned skill ranks, levels, XP and activity scores; LootPath does not invent a profile when the upstream service has no result.
Player lookups remain dynamic tool results rather than crawlable profile pages. This prevents arbitrary names and thin result pages from entering the sitemap while keeping the evergreen Hiscores guides indexable.
- No game login or account link is required.
- Unranked activities can be absent from the visible table.
- Temporary Jagex errors are shown as errors, not replaced with sample values.
03
Exact XP and estimated training pace
XP between whole levels is calculated with the standard RuneScape experience formula. That part is deterministic. XP per hour, cost per hour and completion time are scenario inputs based on selected training methods.
Real training differs because of gear, attention, banking, travel, mistakes and current material prices. LootPath therefore labels the XP gap as exact while describing pace and cost as estimates.
- Whole levels are supported in the current calculator.
- Training rates describe scenarios, not personal guarantees.
- Live material pricing and exact current-XP input remain future data work.
04
Exact calculator boundaries
The combat-level calculator applies the published floor operations to the seven combat skills. The melee max-hit calculator covers standard base damage from Strength, potion, Prayer, attack style, Void and equipment Strength bonus.
Special attacks, Slayer, Salve, raid modifiers, target effects, accuracy and DPS are outside the max-hit result. Skill action calculators use the exact level-to-XP curve and cited XP per successful action, then round up to a whole action.
- Inputs and formula scope remain visible.
- Material prices are not mixed into exact action counts.
- Each calculator links to the mechanic or XP table it uses.
05
Curated progression references
Quest, gear and boss pages organise a limited reviewed set around common account decisions. They explain why an entry matters and link to current reference material for exact requirements, walkthroughs, mechanics and item bonuses.
Curated means selected and interpreted, not complete. A readiness score cannot replace individual combat stats, quest access, target defence or player experience. Gear paths are not target-specific DPS simulations.
06
Illustrative profit models
Boss and money-making rates start from visible comparison baselines. They are reduced or expanded by user-controlled time and efficiency, but they are not live net-profit feeds. A production profit model must store item quantities, actions per hour, supply costs, tax and current input/output prices.
Until those data connections are complete, each method page provides the variables a player should measure and links to a relevant external reference. The model is useful for scenario planning, not for promising income.
- Gross value and net profit are different.
- Learning attempts should be separated from mature rates.
- Small live-market test batches reduce working-capital risk.
07
Reviews, dates and corrections
A page's reviewed date changes only after its facts, source links, model or recommendation are materially checked. Sitemap modification dates use the same stable content date rather than the time of every deployment.
Sources are selected for relevance and current utility. Jagex support and policy pages are preferred for account and legal guidance; the Old School RuneScape Wiki is used for community-maintained game and price references. LootPath adds interpretation rather than copying walkthrough text.
HOW TO READ THIS PAGE
Use the policy at the point where a decision is made
OSRS calculator methodology — This methodology explains how OSRS DPS Calc separates live data, exact calculations, reviewed references and planning estimates. The classification is attached to the result so a player can see what changed, what remains an assumption and what must be checked in game.
Use it when two numbers appear equally precise but come from different evidence. Exact XP between levels can be reproduced from a formula, while XP per hour depends on method, attention and execution. A recent GE transaction is observable, but it is not a guaranteed open offer. Live market signal, Exact formula, Curated or illustrative.
Evidence quality is not a single score for the whole site. Status, source, reviewed date, inputs and exclusions must be evaluated at the individual calculator, item, boss, money-making or Hiscores page.
Reproduce deterministic results with the visible inputs and cited formula before reporting a calculator defect.
For live market data, compare both transaction timestamps, tax, volume, buy limit and the price available in the in-game Grand Exchange.
For curated progression, verify current requirements and mechanics in the linked detailed reference, then adapt the route to the account rather than treating it as an optimal universal order.
For an illustrative rate or readiness model, replace the default scenario with a measured personal sample before committing a long session, expensive setup or large amount of capital.
OPERATIONAL PROMISES
What each principle requires in a working OSRS tool
A principle matters only when its effect is visible in the interface, evidence trail or missing-data behaviour.
Live market signal
Recent community price data, cached briefly and still subject to in-game movement and fill risk.
Apply this principle to the nearby result, reviewed date, status and source. If the page cannot show how the promise works, clarify the claim before it influences an account decision.
Exact formula
A deterministic calculation such as the RuneScape level-to-XP curve; rates layered onto it remain estimates.
Apply this principle to the nearby result, reviewed date, status and source. If the page cannot show how the promise works, clarify the claim before it influences an account decision.
Curated or illustrative
A transparent comparison baseline that must be verified against current requirements, prices and player execution.
Apply this principle to the nearby result, reviewed date, status and source. If the page cannot show how the promise works, clarify the claim before it influences an account decision.
REVIEW CHECKPOINTS
Four questions to ask before trusting a result
The answer should be visible on the landing page or one clearly linked methodology or source page.
Identify Jagex data, community market signals, a deterministic formula, reviewed reference or illustrative model.
Read inputs and exclusions. A bounded correct answer can still be wrong when applied to a different question.
Separate live request time from editorial review. Market signals age faster than stable formulas.
Use the in-game GE for fills, official services for accounts and current references before risking GP or time.
PAGE GOVERNANCE
A published policy needs an owner, a trigger and a visible correction path
This page is reviewed as part of the same system as the calculators and guides. The review is not complete merely because the page renders, contains a recent date or reaches a target word count. It must still describe the current implementation, use language a player can understand and lead to a practical action when the statement is wrong.
Search engines and AI systems should be able to identify the same relationship a player sees: this page states a defined policy or editorial process; linked tools apply it; page-specific evidence supports it; and the Contact and Changelog pages provide a correction trail. That structure is more useful than repeating a brand or keyword without operational detail.
The review outcome for “Four evidence levels. One visible standard.” must stay consistent across five places: the title promise, the H1 topic, the search description, the sections Live market signals, Official Hiscores lookups, Exact XP and estimated training pace, and the related-page links. If one changes without the others, the page can mislead a player or compete with another landing page. A correction should update the shared source of truth, preserve the change history and request a new Google crawl only after the published version is verified.
Scope owner
The page owner checks that the title, main heading, description and body describe one primary topic. Related subjects can be linked, but they should not quietly expand the promise beyond what the current product, data source or contact process can support.
Reproduce deterministic results with the visible inputs and cited formula before reporting a calculator defect.
Material review trigger
A review is required when a data provider, formula, analytics configuration, hosting behaviour, account-link process, legal purpose or public contact route changes. Styling, dependency updates and routine deployments do not by themselves prove that the policy content was rechecked.
For live market data, compare both transaction timestamps, tax, volume, buy limit and the price available in the in-game Grand Exchange.
Evidence record
The reviewed date, linked source, visible interface state and changelog entry should agree. If a live implementation differs from this text, the discrepancy is treated as a correction task rather than hidden behind a broad disclaimer or an automatically refreshed timestamp.
For curated progression, verify current requirements and mechanics in the linked detailed reference, then adapt the route to the account rather than treating it as an optimal universal order.
Localized parity
English, Brazilian Portuguese and Latin American Spanish pages share the same product boundary but are reviewed as separate landing pages. Each version keeps official OSRS terminology where players need it and explains the surrounding obligation, risk and next step in locally natural language.
For an illustrative rate or readiness model, replace the default scenario with a measured personal sample before committing a long session, expensive setup or large amount of capital.
TRACE THE CLAIM
Move from summary to supporting detail
These sections establish the page-specific scope. Continue into the full text whenever an exception matters.
Live market signals
What it establishes: The market tools request latest high and low transaction signals from the OSRS Wiki real-time prices service. LootPath revalidates the selected watchlist on a five-minute server cache. These values are community-collected observations, not an official Jagex order book and not a guarantee that an offer will fill at the displayed level.
How to use it: Reproduce deterministic results with the visible inputs and cited formula before reporting a calculator defect.
Official Hiscores lookups
What it establishes: The Hiscores tool sends a player name to LootPath's server route, which requests the official Jagex Old School RuneScape Hiscores JSON endpoint. Successful responses are displayed as returned skill ranks, levels, XP and activity scores; LootPath does not invent a profile when the upstream service has no result.
How to use it: For live market data, compare both transaction timestamps, tax, volume, buy limit and the price available in the in-game Grand Exchange.
Exact XP and estimated training pace
What it establishes: XP between whole levels is calculated with the standard RuneScape experience formula. That part is deterministic. XP per hour, cost per hour and completion time are scenario inputs based on selected training methods.
How to use it: For curated progression, verify current requirements and mechanics in the linked detailed reference, then adapt the route to the account rather than treating it as an optimal universal order.