Drive A Kukirin controls checklist

Look for Roblox or game-specific prompts for movement, camera, vehicle interaction, first-person view, helmet interaction, and wheelie behavior. Publish a key only after it is visible in-game or repeatedly tested in the current build.

If the UI shows different prompts after mounting a scooter, treat those scooter-state controls as separate from walking controls. Also check whether prompts disappear in first-person view, because the official description confirms first-person riding but does not explain how the camera state changes control visibility.

Keyboard and mouse players should verify movement, camera, interaction, reset, and any vehicle action keys. Mobile players should capture touch button labels and positions, including whether buttons appear only while riding. Controller players should test analog steering, camera, acceleration, braking, and wheelie input separately. For every device, note whether Roblox default controls handle the action or whether Drive A Kukirin adds its own prompt.

The remote build environment cannot open the Roblox client for a first-hand session. Listing W/A/S/D, space, shift, or mobile buttons without evidence would create exactly the kind of false guide this repair is removing. The correct next update is a small capture pass: join the game, mount a scooter, take screenshots of prompts, try each input once, and mark only repeatable results as confirmed.