Example decision
Example decision: if a player asks whether a Rainbow crop plus a pet modifier changes a trade, start with the value list for the base row, check mutation values for the multiplier, then use the calculator only when quantity or pet context changes the math.
Data boundary: this hub does not track live private inventories or guarantee current shop stock. The stock tracker is a manual reference until a stable live source is connected and labeled.
When to leave this hub: use the live game, official update notes, or a direct source when the decision depends on current server stock, newly released mechanics, or a trade that changed after the last LootKit update and review window.
- First choose whether the item is a crop, pet, mutation, stock question, or trade question. That choice decides whether the value list, pet list, mutation page, stock reference, or trading values page should come first.
- Then check the confidence label and update date before using a number. A cross-checked crop row is stronger than a community-reported pet note, and an old stock note should not be treated like live inventory.
- Finally move to calculator math only when the decision combines base value, quantity, mutation, and pet context. If the question is about demand or fairness, use trading values instead of a raw multiplied number.
Scenario: a player asks if a base crop is worth using after a patch. Start with the value list and update date, not the calculator, because the calculator only helps after the base row is trusted.
Scenario: a player asks if Gold or Rainbow changes the answer. Open mutation values first, then calculator math. Keep the stock tracker separate unless the question is about current shop access.
Scenario: a player asks if a trade is fair. Use trading values after the lookup step, because demand and trend can make two similar reference values behave differently in a real offer.
Scenario: a player sends a screenshot with no item context. Ask for the item name, mutation, pet effect, update timing, and confidence source before treating the screenshot as evidence.
When to use calculator math: use it only after the base crop, pet, or mutation row is identified. Calculator math is strongest when the player has a quantity, mutation, pet effect, and a rough comparison target. If those inputs are missing, the calculator can create a confident-looking number from weak assumptions.
When to use the stock reference: use it when the player asks whether a seed, gear item, or limited event item is available or recently seen. Keep stock questions separate from value questions because stock can change by time, server, event window, and manual reporting delay.
When to use trading values: use them when the player asks whether an offer is fair, whether demand changes a row, or whether two bundles behave differently in a real trade. Trading values should come after lookup and calculator steps, not before the item context is clear.
Use the value list when the decision starts with a crop or item name. Use mutation values when the decision starts with a multiplier. Use the calculator when the player has enough inputs to estimate a changed result.
Do not merge stock questions into value questions. Stock availability changes by time and server context, while value rows are slower editorial references that need review before they change.
Do not use one player screenshot as a stable value update unless it can be connected to the exact item, mutation, source timing, and a second signal that explains why the row should change.
If a player asks what to do first, choose the path by decision risk. Low-risk lookup starts on the value list. Math-heavy comparison moves to the calculator. Time-sensitive availability moves to the stock reference. Offer fairness moves to trading values after the base rows are known.
If a new update changes crops, pets, or mutation behavior, treat the hub as a routing map rather than a final answer. Open the page closest to the changed mechanic, check its update date, and leave a correction note if the page needs review.