Checked against the current site data and kept only when the claim is stable enough to use in tools.
Use for code rewards, calculator thresholds, or page claims that should be safe for a player decision.
Wizard Alchemy updates and source log
Track how this site handles Wizard Alchemy data before it becomes a guide recommendation, calculator assumption, or long-tail page.
Codes, race passives, potion thresholds, material drops, and boss routes can change or conflict across public guides. This log keeps uncertainty visible so new pages do not publish unverified values as final facts.
1 Verified items
3 Tracked items
1 Watchlist items
1 Conflict items
Labels
How to read data confidence labels
These labels are not decoration. They decide whether a claim can be used in a calculator, written as a guide rule, or kept only as a watchlist note.
Useful data that appears in our pages, but still needs rechecking after major game updates.
Use for race odds, potion thresholds, material roles, and farming route advice.
A searched topic or reported claim that is worth monitoring before becoming a firm guide recommendation.
Use for new codes, newly reported drops, new bosses, or update rumors.
Sources disagree or the exact value is not safe enough to publish as a final fact.
Use when a reward, drop chance, passive value, or unlock path needs a visible warning.
Log
Current update and source notes
This log explains the current site assumptions and what needs to be rechecked before new claims are promoted.
Added Furnace Core and Copper Earring long-tail guides
The new material pages answer high-intent search questions with conservative route, use, and save advice instead of unverified drop rates.
Recheck exact drop sources and rates before adding database-style enemy tables.Added Source Log and data confidence labels
The site now explains how verified, tracked, watchlist, and conflict claims should be handled before they appear in player-facing guides.
Apply the same labels to future code, material, spell, and route updates.Spell page uses conservative potion threshold data
The spells page keeps Magic requirements and race-fit language as planning guidance instead of exact passive-stat claims.
Recheck potion names, Magic gates, and race compatibility after each major update.Race page focuses on keep-or-reroll decisions
Race odds and role notes are useful for reroll planning, but exact passive text can change after balance patches.
Confirm exact passive wording before adding stronger database-style claims.Material-specific long-tail pages are planned
Furnace Core and Copper Earring have strong search intent, but exact drops and rates should not be expanded until checked.
Build individual material pages only with cautious source notes or verified in-game evidence.Code rewards should keep visible notes when sources disagree
Some public guide pages can disagree on rewards or active status. Conflicting code data should stay labeled instead of being silently merged.
Add per-code confidence fields if new code conflicts appear. Watchlist
Next pages and checks to prioritize
These topics have search value, but they should be handled with clear verification notes before becoming database-style pages.
High Furnace Core guide
The first conservative guide is live, but exact drop sources still need confirmation.
Recheck source wording and add enemy-specific data only after reliable verification. High Copper Earring guide
The first conservative guide is live for potion planning and farming route queries.
Confirm singular/plural naming, drop sources, and exact rates before expanding the page. Medium Potion planner improvements
Players benefit from next-target and short-by-Magic feedback.
Add material filtering and next threshold feedback to the calculator. Medium Code conflict labels
Code pages can change quickly and copied lists often drift.
Store confidence status with each code when a conflict is found. Decision rules
What gets published as a fact?
Use cautious language first
New material drops, exact rates, and passive values stay conservative until checked.
Separate planning from database claims
A route can be useful even when exact drop rates are not ready for publication.
Keep conflicts visible
If sources disagree, the page should explain the conflict instead of hiding it.
Link tools to checked assumptions
Calculators should use the most stable values and point players to recheck notes.
FAQ
Source log FAQ
Why does Wizard Alchemy Tools use source labels?
Wizard Alchemy changes quickly, and copied guide data can drift. Source labels make it clear whether a claim is verified, tracked, on the watchlist, or conflicting.
Does tracked mean confirmed forever?
No. Tracked means the data is useful enough for the current site, but it should be rechecked after major game updates or balance changes.
When do you use a conflict label?
A conflict label is used when sources disagree about a code reward, drop value, passive effect, unlock path, or other player-facing detail.
What pages should be added next?
The current watchlist prioritizes Furnace Core, Copper Earring, potion planner improvements, and code conflict labels.