Official account guidance
Jagex support and legal pages are the primary source for account linking, security, rules and fan-content requirements.
SOURCE REGISTER
References that remain visible at the decision point.
Source links are shown where a player needs to verify a claim. This register explains why each publisher is used and what LootPath does—and does not—derive from it.
Editorial review
Community game reference
The OSRS Wiki provides maintained item, quest, boss, equipment, method and real-time price documentation.
Final execution check
Current in-game requirements, available offers and personal results always override a planning estimate.
01
Jagex and Steam
The Steam setup guide links directly to the official Old School RuneScape Steam listing, Jagex's Steam login FAQ and Jagex linked-account settings. Account actions should be completed only on official services.
The site-wide legal notice follows the Jagex Fan Content Policy. LootPath does not claim endorsement, ownership of the game or privileged access to Jagex systems.
02
OSRS Wiki real-time prices
Selected Grand Exchange pages use the OSRS Wiki real-time prices service. The feed reflects community-collected transaction signals and differs from an official order book. LootPath stores stable item IDs, requests the latest high and low observations and uses a short server cache.
Each tracked item page links both to the real-time price documentation and the relevant item reference. If the service omits a required value or cannot be reached, the affected price is marked unavailable instead of being replaced by a static snapshot.
03
Official OSRS Hiscores
Player lookups are requested from the official Jagex Regular, Ironman, Hardcore Ironman or Ultimate Ironman Hiscores service selected in the tool. LootPath parses the returned skills and activities for presentation without requiring a game login.
A missing player, wrong account mode, rate limit or upstream failure remains visible as an error. Search results are live responses and are not converted into permanent profile pages.
04
Calculator formula references
Combat, max-hit and skill-action tools cite the specific mechanic or experience table used by the visible calculation. These pages calculate a bounded result rather than claiming to simulate every combat or training variable.
Formula pages should be reviewed after relevant game updates. A changed method value must be corrected in the shared calculator profile so its tool page, evidence and sitemap date remain aligned.
05
Game reference pages
Quest pages link to their current OSRS Wiki entries for requirements, items, dangerous sections and rewards. Boss pages link to mechanics, access and strategy references. Gear pages link to equipment categories and the Wiki DPS tool, while money pages link to the method or calculator most relevant to the scenario.
References do not make LootPath's estimate automatically correct. Their purpose is traceability: a player and a crawler can identify the underlying game information and distinguish it from LootPath's interpretation.
06
Selection and attribution rules
A source must directly support the nearby statement or provide the current details that the page tells the player to verify. Generic home-page links are avoided when a specific item, quest, boss or calculator page exists.
LootPath paraphrases and adds original decision guidance. It does not reproduce complete Wiki walkthroughs, proprietary game assets or long passages from external publications.
HOW TO READ THIS PAGE
Use the policy at the point where a decision is made
OSRS data sources — The source register identifies the publishers and interfaces used for official account guidance, public Hiscores records, community market signals, stable game mechanics and editorial cross-checks. It exists so a claim can be traced beyond a decorative citation badge.
Use the most specific available reference. An item page should cite the item or price service, a boss page should cite the encounter, and a Steam account statement should lead to current Jagex guidance rather than a general home page. Official account guidance, Community game reference, Final execution check.
A link establishes traceability, not automatic correctness. OSRS DPS Calc remains responsible for the formula, selection, interpretation and wording that it builds on top of an external source.
Match the source type to the claim: Jagex for account and Hiscores services, the OSRS Wiki price service for community transaction signals, and current reference pages for mechanics and requirements.
Check whether the source is live, versioned or editorial. A live response can fail temporarily; a stable reference can become outdated after a game update.
Prefer page-level citations over a single site-wide source list. The relevant evidence should be reachable from the same landing page that presents the conclusion.
Report a mismatch with the exact URL, observed value, expected result, date and supporting source so the underlying shared data can be corrected instead of patched only in visible copy.
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.
Official account guidance
Jagex support and legal pages are the primary source for account linking, security, rules and fan-content requirements.
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.
Community game reference
The OSRS Wiki provides maintained item, quest, boss, equipment, method and real-time price documentation.
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.
Final execution check
Current in-game requirements, available offers and personal results always override a planning estimate.
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 “References that remain visible at the decision point.” must stay consistent across five places: the title promise, the H1 topic, the search description, the sections Jagex and Steam, OSRS Wiki real-time prices, Official OSRS Hiscores, 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.
Match the source type to the claim: Jagex for account and Hiscores services, the OSRS Wiki price service for community transaction signals, and current reference pages for mechanics and requirements.
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.
Check whether the source is live, versioned or editorial. A live response can fail temporarily; a stable reference can become outdated after a game update.
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.
Prefer page-level citations over a single site-wide source list. The relevant evidence should be reachable from the same landing page that presents the conclusion.
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.
Report a mismatch with the exact URL, observed value, expected result, date and supporting source so the underlying shared data can be corrected instead of patched only in visible copy.
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.
Jagex and Steam
What it establishes: The Steam setup guide links directly to the official Old School RuneScape Steam listing, Jagex's Steam login FAQ and Jagex linked-account settings. Account actions should be completed only on official services.
How to use it: Match the source type to the claim: Jagex for account and Hiscores services, the OSRS Wiki price service for community transaction signals, and current reference pages for mechanics and requirements.
OSRS Wiki real-time prices
What it establishes: Selected Grand Exchange pages use the OSRS Wiki real-time prices service. The feed reflects community-collected transaction signals and differs from an official order book. LootPath stores stable item IDs, requests the latest high and low observations and uses a short server cache.
How to use it: Check whether the source is live, versioned or editorial. A live response can fail temporarily; a stable reference can become outdated after a game update.
Official OSRS Hiscores
What it establishes: Player lookups are requested from the official Jagex Regular, Ironman, Hardcore Ironman or Ultimate Ironman Hiscores service selected in the tool. LootPath parses the returned skills and activities for presentation without requiring a game login.
How to use it: Prefer page-level citations over a single site-wide source list. The relevant evidence should be reachable from the same landing page that presents the conclusion.