Useful before impressive
A result should answer a player's question clearly. I would rather show exactly what is missing than claim a method is available because most of its requirements happen to match.
About this project
I built the tools I wanted for my own playthrough
OSRS TCG Tools is an independent community companion for people using their RuneLite TCG collections. It is not an official website for Jagex, RuneLite, OSRS TCG, Bronzeman TCG, Quest Helper, Wise Old Man, or the Old School RuneScape Wiki.
Why it exists
A practical solution to an immediate problem
I started this website to support my own Bronzeman playthrough with my GIM. I wanted to search the cards my group had collected, find possible trades, and answer practical questions such as which quests I could start, which training methods were open, what equipment I could use, and what I could fight.
Those answers were not available in one place, and they could not be produced by simply displaying the OSRS TCG catalogue. The tools need to combine cards with levels, completed quests, Bronzeman settings, access requirements, Wiki facts, RuneLite data, and the difference between a card I own and a card a teammate might trade to me.
How I review information
Source facts, observed behavior, and my decisions stay separate
I do my best to make every result explainable. Upstream code is tied to exact revisions, Wiki facts are stored with reviewed page revisions, generated datasets include their source records, and uncertain mappings remain labelled instead of being filled in with a guess. The public Data & Methodology page links the machine-readable datasets used by the live tools.
Bronzeman behavior can be especially difficult to summarize because a restriction may depend on the selected setting, the exact menu action, quest state, or whether an item is used from the inventory or the ground. I document behavior I can reproduce or prove from source, but I cannot claim that an inconsistency is definitely a bug or describe a developer's intent unless the developer has said so.
Editorial principles
What I try to protect when the site changes
No hidden ownership assumptions
Personal cards, universal whitelist entries, and teammate cards remain separate. A possible GIM trade is useful information, but it is not the same as owning the card.
Uncertainty remains visible
Beta tools may have incomplete sources. If a required fact cannot be verified, the result stays blocked or clearly labelled for review instead of silently inventing an answer.
Corrections are part of the work
Players will find edge cases I missed. I review reproducible reports, update the evidence when needed, and explain meaningful changes on the public What's New page.
Accounts and privacy
Google confirms a returning account; it does not provide collection data
Google sign-in currently lets the site recognize which RuneScape profiles a returning visitor controls. The site receives a stable Google account identifier, not an email address, password, Gmail, Drive files, contacts, profile photo, or offline access. RuneLite save files are decoded locally in the browser, and only normalized collection data is stored when an authorized player deliberately saves or updates a collection.
The full list of stored data, analytics boundaries, group behavior, and private-link protections is available in the Privacy notice.
Corrections and feedback
If something is wrong, I want enough information to investigate it
The tools are still evolving, and some features are explicitly labelled Beta. If an item, NPC, quest, method, access requirement, or Bronzeman interaction looks wrong, please include the name of the result, what the page reported, what you expected, and any exact in-game step that reproduces the difference. That gives me something concrete to check against the relevant source.