Grow a Garden 2 Stock Tracker

What the stock board shows

Each row is built around the item name, image, stock count, price, rarity, last verified field, status label, and confidence label. The count and price columns give players a fast scan, but the trust fields are the most important part of the row. A high number with no source is less useful than a smaller set of rows that clearly say when and how they were checked.

The first public rows are seed examples: Carrot Seed, Strawberry Seed, Blueberry Seed, Dragon Fruit Seed, and Mango Seed. Dragon Fruit and Mango can act as rare stock candidates for scanning, but their rows remain community-reported reference ranges, not live stock claims. The freshness and conflict rules explain when a report can be reviewed and when it must stay out of public stock rows.

How verification should work

A confirmed stock row should have a clear source, a timestamp, and a short note about how it was checked. That could mean a manual in-game check, a trustworthy community submission, or a maintained data source if one becomes available. The page should keep those source types separate because they do not carry the same confidence.

Community-reported stock can be useful when the game moves fast, but it should not instantly become confirmed. The safer workflow is to accept a report, mark it as community reported, compare it with other evidence when possible, then upgrade it only after a source check. If two reports disagree, the page should show lower confidence instead of hiding the uncertainty.

This is why the current URL stays `/stock` instead of splitting into a separate stock tracker page. The player task is the same: check stock, understand whether the row is current, and decide whether the evidence is strong enough to act on.

Why live claims are dangerous

A fake live tracker is worse than no tracker. Players may spend currency, leave a server, or wait for a restock based on the page. If the site says live while using stale community data, the page breaks trust quickly. The current MVP avoids that by marking Fandom Seed Shop rows as community reported and by sending player reports into manual review first.

This page can still be useful before automation exists. It defines the table structure, item presentation, source language, freshness rules, conflict handling, and player decision flow. That makes the next development step clear: collect timestamped in-game evidence, then gradually move individual rows from community reported to confirmed.

What should happen after the first source review

After the first real source review, the stock page should not simply replace every pending label with confirmed. It should upgrade rows one at a time. A common seed that was checked recently can become confirmed, while a rarer seed with weaker evidence may stay community reported. This row-by-row approach keeps the table useful without overstating the whole page.

The page should also preserve old verification context. If a row was checked yesterday but not today, players should be able to see that age instead of reading a vague status. Staleness is especially important for restock information, because an old confirmed row can become misleading once the next rotation arrives.