Keyboard and mouse
Record movement, camera, interaction, menus, and building actions separately. A generic movement assumption does not prove the action used by a flower plot or crafting interface.
A safe device checklist for finding current prompts, plus the exact actions that still require hands-on verification before publishing a fixed control map.
The official public experience page does not document a fixed keyboard, controller, or mobile layout. That means a remembered Roblox key or another game’s control scheme is not reliable evidence for planting, harvesting, crafting, serving, or building here.
Record movement, camera, interaction, menus, and building actions separately. A generic movement assumption does not prove the action used by a flower plot or crafting interface.
Watch for button prompts changing when a controller becomes active. Test menu navigation, selection, confirmation, cancellation, and any building mode independently.
Capture the visible touch layout and any contextual button that appears near a plot, creation station, customer, or decoration. Screen size can affect where prompts appear.
For action-specific context, use the planting and harvesting guide or the bouquet crafting guide. Those pages explain what state the game is expected to be in without inventing the input.
These fields are intentionally not filled with guesses. Each one needs a dated in-game observation before exact values or instructions are published.
A fixed official keyboard map is not published on the public experience page. Follow the prompts shown in the current Roblox session and record them before creating a key list.
No fixed official controller layout was documented on the checked public game page. Prompts may depend on the device and current interface.
Use the touch controls and labels displayed by the current game. This guide does not convert a desktop assumption into a mobile instruction.