The source register was reviewed on 2026-10-04. Official Roblox surfaces support published facts; third-party videos only identify questions for a new in-game test.
A stable game identity or advertised feature can cite the official Roblox experience. A price, timer, recipe, control, reward, or test result needs a dated current observation. A YouTube video can help locate an interface or question but does not become official merely because it shows gameplay.
These sources are authoritative for the exact fields they expose. They do not automatically verify details they do not state.
Supports: Game identity, creator, core play loop, offline growth, employees, upgrades, decoration, daily rewards, and official media.
How we use it: Primary source for stable gameplay claims on this guide.
Official pageSupports: The developer's public Roblox group and the official group destination linked to this experience.
How we use it: Use to verify the group identity; do not assume an off-platform social account is official.
Official APISupports: Universe-level identity metadata for universe 10324001605.
How we use it: Reference data only. A returned updated field is not automatically a patch-note date.
Official APISupports: Changing public game metadata supplied by Roblox.
How we use it: Recheck at publication time; live counts and timestamps can change.
Official APISupports: The public game-pass listing for this universe.
How we use it: Names, availability, price, and effects must be rechecked before a buying guide is published.
Official APISupports: Current and upcoming update events hosted by Magic Box Games, such as Big Buildings (October 2, 2026) and Next Update (October 14, 2026).
How we use it: Primary source for the update log. Only current and upcoming events are returned, so older event names stay labelled as reported.
Official APISupports: The public badge listing for this universe.
How we use it: Use only for badge facts visible in the current response.
These links can make an in-game research session more efficient. Every gameplay claim taken from them must be reproduced in the current game, dated, and described in original words.
Supports: Potential first-session actions and interface sequence.
How we use it: Use to create a test checklist, then reproduce every action in the current game before publishing it as fact.
Research leadSupports: Potential seed, planting, and harvest interface locations.
How we use it: Verify names, prompts, costs, timing, and device differences in-game.
Research leadSupports: Potential crafting-table flow.
How we use it: Do not copy recipe claims; verify the current requirements and results in-game.
Research leadSupports: Potential staff interface and hiring flow.
How we use it: Verify staff names, unlocks, costs, and effects in the current game.
Research leadSupports: Potential building and decoration actions.
How we use it: Verify placement, removal, rotation, and refunds before documenting controls.
Research leadSupports: Potential upgrade interface and requirements.
How we use it: Verify every tier, prerequisite, cost, and effect in-game.
Research leadSupports: A potential supplies and growth-speed topic.
How we use it: Confirm that the feature and terminology remain current before adding it to the flower guide.
The seven image files used by this guide were obtained from the recorded Roblox CDN source URLs. A promotional image supports what is visibly shown and its official-media origin; it does not prove an unseen recipe, value, control, or outcome. Rights remain with their respective owners.
A checked date says when the listed surfaces were reviewed; it does not promise that the game has not changed since. A correction should identify the affected page, the exact claim, a current source or reproducible observation, and the date. Until a dedicated site correction channel is available, this guide should not imply that player submissions are being monitored.
For how the evidence is applied, compare the flowers guide, bouquets guide, and upgrades guide.
