Stock Board





A stock board layout for seeds and shop items with last verified, confidence, and source status fields.





The MVP will not label any seed as live or confirmed until a source review process is running.
All stock rowsCarrot, Strawberry, Blueberry, Dragon Fruit, and Mango Seed were queued before the first community source pass.
Carrot Seed, Strawberry Seed, Blueberry Seed, Dragon Fruit Seed, Mango SeedFandom Seed Shop lists costs, stock ranges, stock chances, and 5-minute restock behavior; rows remain non-live until timestamped in-game checks exist.
Carrot Seed, Strawberry Seed, Blueberry Seed, Dragon Fruit Seed, Mango SeedLocal Fandom-sourced item images help players recognize items, but they do not verify stock availability or price.
Seed iconsSeed, gear, crate, or event item name.
Exact count or sold-out state shown in-game.
Only required when a price is visible.
Screenshot, short clip, or trusted report link.
Timestamp with timezone when possible.
Helps diagnose conflicting reports.
The stock board is the most trust-sensitive part of the site. Players use stock information to decide whether to buy a seed, wait for restock, switch servers, or save currency. For that reason, this page is designed around verification fields first and visual polish second. A row is not treated as live simply because it appears in the table.
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. They use local item images so players can recognize the object quickly. The values are not presented as a live source of truth yet. The current status is intentionally pending while the site prepares a source and verification workflow.
A future 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.
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 disabling the submit flow until validation rules are ready.
This page can still be useful before automation exists. It defines the table structure, item presentation, source language, and player decision flow. That makes the next development step clear: connect timestamped verification inputs, then gradually move individual rows from community reported to confirmed.
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.
No. The MVP stock board uses community source ranges and does not claim live restock detection until a reliable source chain is connected.
Community source rows make the tool useful for early reference while still showing players how source status and confidence work.
The page needs source notes, last verified timestamps, and a real process for moving rows between pending, community reported, and confirmed.
Not yet. The submit flow should stay disabled until duplicate handling, source labels, abuse protection, and moderation rules are defined.