Independent Bronzeman field guide

Less-obvious Bronzeman behavior

Plain-English notes about rules and limitations that may not be obvious while playing.

Released Bronzeman 0.3.3 has newer ownership and Beta-card handling.

Its distributed source was checked at revision adef54b9 on September 17. The website's older rule data remains pinned separately; the notes below state the revision each claim was checked against. A source check is not proof that every in-game interaction works.

Why this page exists

OSRS TCG Tools is built to reflect Bronzeman's observed card logic as accurately as possible. Some rules depend on a specific setting, action path, quest state, or item you are carrying. This page explains those details without treating every strict rule or missing entry as a confirmed bug.

Verified behavior

What the reviewed build does

Known limitations and gaps

Where the result may be surprising

Released V1 rule update

What changed in Bronzeman 0.3.1

Version 0.3.1 moved restrictions to live V1 parent-card identities, corrected Coins ownership, changed Cooking and Thieving filters, exempted Veos and the Ironman tutor from onboarding locks, and added the missing Crashed Star / Mine → Stardust rule. Version 0.3.3 retains that rule baseline but changes how some owned and Beta cards are matched.

Read the plain-English V1 and Bronzeman update · Open the historical 0.3.1 compatibility audit

Released update

What Bronzeman 0.3.3 changes

The old Beta-save import, wipe and restore controls from 0.3.2 were removed. Refresh Beta Cards now classifies cards OSRS TCG currently reports as owned, using the public album only when the separate lookup setting is enabled. Clear Cached Beta Cards clears that classification; neither control changes the official collection.

Reviewed older Beta names and noted items have narrower ownership fixes in the released code. An enabled live-catalogue download can still fail and remain on fallback data until a restart or disable/re-enable. If a card you own stays locked, check the exact card, profile and settings before reporting it; do not reset the collection as a first step.

Version-pinned review

Ground actions that may not re-check a card

These cards remain requirements in OSRS TCG Tools. The exact ground actions below could bypass a restriction in the last fully checked interaction review. The site has not reproduced each action in-game on Bronzeman 0.3.3, so treat this as a specific warning to check, not proof that every route still bypasses a card.

Bury

The inventory Bury route can be stopped by Item Usage, but choosing Bury on the dropped card is not checked.

Bull bones

Crush

The inventory Crush route can be stopped by Item Usage, but choosing Crush on the dropped card is not checked.

Smouldering heartSmouldering gland

Eat-from

The inventory Eat-from route can be stopped by Item Usage, but choosing Eat-from on the dropped card is not checked.

Smouldering pile of flesh

Lay

The normal trap or Item Usage check can require the card, but dropping the trap and choosing Lay is not checked.

Bird snareBox trapRabbit snare

Light

The inventory route can require the locked log card through Item Usage, but dropping the log and choosing Light is not checked. The Tinderbox rule still applies where Bronzeman has a covered recipe.

White logsPurple logsLogsMagic logsYew logsMaple logsWillow logsOak logsRedwood logsCamphor logsIronwood logsRosewood logsMahogany logsTeak logsRed logsGreen logsBlue logs

Item actions came from game cache 2655; the bypass condition was last checked against Bronzeman 0.3.2 on September 5, 2026.

A note from the site owner

Observed behavior is not proof of intent

I built these tools to support my own Bronzeman playthrough with my GIM. When testing reveals a reproducible issue, I make my best effort to share the evidence I collected with the developers.

Because I am not affiliated with Bronzeman TCG or OSRS TCG, I am never completely certain whether an inconsistency is a bug, an accepted limitation, or an intentional rule unless the developer has said so. Where this site calls something a possible bug, that is my evidence-based interpretation when the behavior appears to conflict with other plugin handling or developer documentation—not a statement of developer intent. I also cannot promise that anything I report will be changed or fixed.

Reviewed sources

The claims above are tied to exact source snapshots so they can be checked again when the plugins change.

Found something different in your installed build? Send a reproducible report.