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.
Copy the request before choosing a plant
Write the customer's wording exactly as it appears in the current full release. Separate each visible condition rather than compressing several requirements into a vague summary. If the request uses a property label, retain that label. Do not substitute real-world plant-care knowledge for the game's own language, because the task is to satisfy the game's current matching system.
Next, inspect the candidate plant information visible in the interface. Compare one request condition at a time with the corresponding displayed property. The research names size and moisture as examples, but this page does not invent the complete set of fields. Any additional property should be recorded only when it is actually visible in the current game.
- Copy the complete customer request
- Split it into individually visible conditions
- Use the game's property labels verbatim
- Add no property that the current interface does not show
Create a small traceable comparison
For each candidate, record its displayed name and only the properties relevant to the request. Mark each condition as visibly matched, visibly not matched, or unclear. This produces a compact evidence table for the current task without pretending to be a universal Plant Compendium. Attach a version when visible and a verification date so a later interface change can be recognized.
Choose a plant based on the visible comparison and record the result the game presents. One successful choice demonstrates that request in that observed context; it does not establish every possible combination or unlock rule. One unsuccessful choice also does not prove that the displayed property is broken, especially when the supplied research does not define the anomaly.
- Record the candidate's current displayed name
- Compare only properties relevant to this request
- Use matched, not matched, or unclear
- Date the result instead of generalizing it forever
Distinguish missing data from an interface anomaly
If a request result conflicts with the visible comparison, first preserve the evidence: request text, candidate plant, maturity state when relevant, property labels, result message, current version, and date. The research flags possible interface or property anomalies, but it does not confirm their cause, complete list, or fix status. 'Observed mismatch' is the accurate label.
The Plant Properties Guide explains how to record size, moisture, and any other currently visible field without inventing values. This page does not provide a complete plant list, every property combination, prices, growth times, rewards, unlock conditions, or an optimal sales strategy. A third-party compendium can suggest candidates to verify, but it is not copied as first-party evidence.
- Preserve the evidence before diagnosing
- Call an unexplained conflict an observed mismatch
- Do not claim a fix from an undated report
- Verify third-party suggestions inside the current build