Player-first scope
Every page should help complete a real account decision, not exist only to target a search phrase.
INDEPENDENT OSRS DECISION TOOLS
Less tab switching. More confident OSRS decisions.
LootPath is an independent, English-first collection of Old School RuneScape tools for players deciding what to train, buy, unlock, fight or fund next. It combines focused calculators with transparent limitations so a useful estimate never pretends to be an in-game guarantee.
Editorial review
No account credentials
LootPath does not request a Jagex password, Steam password, Bank PIN, authenticator code or game session.
Independent publication
LootPath is not endorsed by Jagex. Game intellectual property is used under the Jagex Fan Content Policy.
01
What LootPath is building
The site connects eight common decisions: Grand Exchange price checks, XP planning, quest order, gear progression, boss readiness, money-making selection, Achievement Diary progress and official Hiscores lookup. Separate pages make each question searchable, while internal links preserve the connection between them. A diary requirement can become an XP target; that target can create a cost; the cost can become a money-making goal.
The first public version deliberately covers a limited set of items, skills, quests, equipment routes, bosses and methods. Narrow coverage makes it possible to label data honestly and improve the underlying model before expanding to the full game.
02
What LootPath is not
LootPath is not a RuneLite client, an automated player, a gold-trading service or a replacement for the complete Old School RuneScape Wiki. It does not perform actions in game, connect to a character session or promise profit. Detailed walkthroughs and current game mechanics remain linked to their source references.
The site's advantage is the decision layer: calculators, filters, scenario controls and concise comparisons that help a player turn reference information into a next step.
03
How trust should work
A live market signal is labelled differently from an exact XP formula, a curated progression recommendation and an illustrative profit estimate. Every enhanced detail page includes a reviewed date, data status, page-specific interpretation and external references. The methodology page explains these labels in full.
Corrections should change the underlying page data and appear in the changelog when they materially affect a recommendation or calculation. Cosmetic rebuilds do not reset every page's content date.
HOW TO READ THIS PAGE
Use the policy at the point where a decision is made
about OSRS DPS Calc — This page defines OSRS DPS Calc as an independent Old School RuneScape decision toolkit. Its scope covers DPS calculations, Grand Exchange signals, XP planning, quests, gear, bosses, money making, Achievement Diaries and public Hiscores without pretending to be Jagex, RuneLite or the complete OSRS Wiki.
Use the About page to identify who the tools are for, which player decisions they support and where responsibility remains with the player. A useful page must answer a real account question and show its inputs, evidence status, source and limitation near the result. Player-first scope, No account credentials, Independent publication.
No page on this site should request a Jagex password, Steam password, Bank PIN, authenticator code or live game session. Public Hiscores names and calculator inputs are not proof of account ownership.
Start with the decision, not the feature list. A player comparing two combat setups needs the DPS calculator; a player estimating a level target needs an XP calculator; a player checking a trade needs the GE tracker and an in-game test.
Check the evidence label before accepting a number. Live market observations, deterministic formulas, curated guides and illustrative models have different freshness and verification requirements.
Follow the page-specific source when the decision involves current mechanics, account access or substantial GP. The narrower source and limitation take priority over a broad site description.
Treat localization as product work. Brazilian Portuguese and Latin American Spanish pages preserve official item, quest, boss and skill names while explaining the decision in the language and conventions players actually use.
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.
Player-first scope
Every page should help complete a real account decision, not exist only to target a search phrase.
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.
No account credentials
LootPath does not request a Jagex password, Steam password, Bank PIN, authenticator code or game session.
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.
Independent publication
LootPath is not endorsed by Jagex. Game intellectual property is used under the Jagex Fan Content Policy.
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 “Less tab switching. More confident OSRS decisions.” must stay consistent across five places: the title promise, the H1 topic, the search description, the sections What LootPath is building, What LootPath is not, How trust should work, 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.
Start with the decision, not the feature list. A player comparing two combat setups needs the DPS calculator; a player estimating a level target needs an XP calculator; a player checking a trade needs the GE tracker and an in-game test.
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 the evidence label before accepting a number. Live market observations, deterministic formulas, curated guides and illustrative models have different freshness and verification requirements.
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.
Follow the page-specific source when the decision involves current mechanics, account access or substantial GP. The narrower source and limitation take priority over a broad site description.
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.
Treat localization as product work. Brazilian Portuguese and Latin American Spanish pages preserve official item, quest, boss and skill names while explaining the decision in the language and conventions players actually use.
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.
What LootPath is building
What it establishes: The site connects eight common decisions: Grand Exchange price checks, XP planning, quest order, gear progression, boss readiness, money-making selection, Achievement Diary progress and official Hiscores lookup. Separate pages make each question searchable, while internal links preserve the connection between them. A diary requirement can become an XP target; that target can create a cost; the cost can become a money-making goal.
How to use it: Start with the decision, not the feature list. A player comparing two combat setups needs the DPS calculator; a player estimating a level target needs an XP calculator; a player checking a trade needs the GE tracker and an in-game test.
What LootPath is not
What it establishes: LootPath is not a RuneLite client, an automated player, a gold-trading service or a replacement for the complete Old School RuneScape Wiki. It does not perform actions in game, connect to a character session or promise profit. Detailed walkthroughs and current game mechanics remain linked to their source references.
How to use it: Check the evidence label before accepting a number. Live market observations, deterministic formulas, curated guides and illustrative models have different freshness and verification requirements.
How trust should work
What it establishes: A live market signal is labelled differently from an exact XP formula, a curated progression recommendation and an illustrative profit estimate. Every enhanced detail page includes a reviewed date, data status, page-specific interpretation and external references. The methodology page explains these labels in full.
How to use it: Follow the page-specific source when the decision involves current mechanics, account access or substantial GP. The narrower source and limitation take priority over a broad site description.