Poco Loco race buttons and controls

Poco Loco has three different control surfaces: creator race and camera controls, viewer interactions, and local developer test tools. A button visible in a local test is not automatically a public viewer feature. The rules below apply to the supported Twitch and Kick surfaces.

Prepare the correct control surface

Creators need a signed-in account and their own active race. Viewers need the matching provider identity and, for actions on their own car, an entry in the current race. Use the race's Keyboard controls help for the controls active on your device; desktop bindings can be customized and may differ from browser defaults.

Joining happens on Grid. Viewer race actions need a running session. Take the Wheel, where available, controls the creator's own entered car; it does not give a viewer remote steering of another racer.

Use creator race and camera controls

In the browser's spectator controls, W A S D or right drag pans the overview camera. Left/right or dragging orbits the followed racer. Q / E, the wheel, or pinch adjusts zoom; 1–9 follows race positions; R returns to track overview; Tab toggles racer labels. Shift / + / - adjusts camera speed. Open Keyboard controls for the current context.

Escape opens the race pause/resume surface or the Grid countdown overlay. Use Resume, settings, shortcuts, and the available race actions from the appropriate menu. Opening Tutorials only opens reading help; it does not start a race action or apply an effect.

When Take the Wheel is active, controls change meaning: W / S are throttle/brake, A / D steer, Space is handbrake, Q cycles the chase camera, and holding E looks behind. In a race, R resets the creator car; it is not the overview shortcut in this context. Desktop mouse capture is released by Escape. Use the contextual help instead of applying spectator shortcuts while driving.

Boost and Honk on Twitch

Boost gives your own entered racer a temporary speed boost. Free Boost is limited to 3 uses for a race expected to last under 60 seconds, or 5 otherwise. The server decides the allowance from the session's expected duration. A purchased Twitch Boost is available beyond the free allowance; it still needs your racer in the current running race.

Honk sounds your own vehicle's selected horn. Twitch Honk does not have the Kick per-race horn limit. It still requires your entered racer and a running race. Honking does not change your finish position or directly award points.

Yeet and Spin on Twitch

Yeet sends one random eligible vehicle into the air; Yeet 3 requests three random eligible vehicles. Spin spins one random eligible vehicle; Spin 3 requests three. You do not pick the target. Actual affected racers depend on the eligible cars in the current race, and an unavailable target can make an effect unavailable.

These are optional Twitch Bits interactions. They are not free join commands, Kick chat controls, or a guaranteed way to win. Prices come from the creator's extension configuration and the current Twitch product/checkout, so read the amount shown in Companion before confirming. The price can differ between creators.

Use Kick free actions

After you have joined, send boost in the creator's Kick chat during the running race. It uses the same short/regular free Boost allowance described above. Send honk to sound your own car's horn; Kick allows 5 honks per player per race.

Kick does not use Twitch Bits, the Twitch extension, or Companion's paid Yeet/Spin surface. Provider capabilities are intentionally separate. Once an allowance is used, wait for the next race instead of trying a Twitch purchase flow on Kick.

Understand unavailable and pending actions

Common reasons an action cannot run are no running race, the wrong channel/session, no entry for your provider identity, an exhausted free allowance, or no eligible target. A paid Twitch action also needs valid identity and a verified transaction. Only one matching checkout can be pending; avoid repeatedly approving new purchases while verification is unresolved.

There is no single wait time that applies to every action. Check your remaining allowance and the current button state. An action may be unavailable while a purchase is pending or the provider connection is unavailable. A completed payment and a dispatched effect are separate stages; preserve the visible transaction result and contact support if fulfillment remains uncertain.

Keep local test controls separate

Local race test controls, planner diagnostics, capture mode, and admin tools are developer or locally enabled surfaces. Their Boost, Honk, Yeet, and Spin buttons help exercise simulation behavior. They are not evidence that every viewer can use those buttons, ignore quotas, or bypass payment in a public race.

After using ordinary creator or viewer controls, the expected result is the relevant camera/menu change or an accepted effect in the current race. Reading this tutorial does not mutate the race.