The primary Steam source was reviewed on 2026-08-08. Exact values or steps that source does not confirm remain labeled unknown until reproduced in the current version.
Use the interface's property names
Record a plant's displayed name, then copy each relevant property label and value exactly as the current game presents them. Size and moisture are confirmed examples for this guide's scope. Do not replace the game's terminology with a real-world botanical interpretation, and do not assume additional categories merely because another plant game uses them.
The purpose of the record is practical: connect a customer's visible condition with the same property field on a candidate plant. A property that is not relevant to the current request can remain outside the comparison. This keeps the note small enough to audit and avoids turning a few verified observations into an unsupported full compendium.
- Copy the plant name as displayed
- Copy size and moisture wording as displayed
- Record another field only when the current interface shows it
- Link each recorded property to a current request condition
Make every entry version-aware
Leafy Corner's full release arrived on July 30, 2026. An older image, discussion, or undated plant sheet may use different labels or behavior. Add the visible game version when available and always add the check date. If a future observation changes, keep both records rather than silently rewriting the older one as though it never existed.
A current interface observation still needs careful wording. Record what the field displays and how it was used in one request; do not infer sale price, growth duration, reward, unlock condition, or a hidden property interaction. Those are separate claims, and the official evidence used for this site does not verify them.
- Mark the current version when visible
- Record the verification date
- Keep older and newer observations distinguishable
- Do not attach unrelated numeric claims to a property entry
Record mismatches without declaring a bug fixed
The research requires known interface or property anomalies to be tracked, but it does not provide a verified explanation or current repair status. When the displayed property and the request outcome appear inconsistent, capture both exactly and call the result an observed mismatch. That is evidence; a confident statement about the cause would not be.
Return to Customer Requests to run the condition-by-condition comparison, or to Fulfill Orders when maturity and the order confirmation flow are the real question. This page deliberately omits a complete plant list, every property combination, prices, growth times, rewards, unlocks, and a best-money method. Community tables remain leads to verify, not content to copy.
- Capture the property, request, and result together
- Separate observation from cause
- Do not state a repair status without current evidence
- Do not expand a verified example into a complete plant table