The player guide Cannon not working

Sledding Game Cannon Not Working

A cannon puff without launching the player was reported during the early Steam release. The September update explicitly fixes cannon softlocks and lets players who rolled snowballs use cannons. Update first, then distinguish that recorded lock from a missed interaction or a host-connection problem.

Steam PC symptom report from May 2026, compared with the official September 21 fix. No unverified input trick is presented as a current universal fix.

Identify the recorded failure

The original report describes the cannon making a puff of air without ejecting the player. Replies mention non-host sessions and busy servers, but those reports do not prove the sole cause of every cannon failure.

Record whether you saw and used an interaction prompt, entered the cannon, heard/saw the puff and then remained stuck. That sequence is more useful than a report that only says “cannon broken.”

Sledding Game mountain valley and sledders viewed downhill.
The cannon symptom is a launch interaction failure; ordinary downhill movement is a separate check.

Sources: Cannon report and replies

Check the documented fix against your build

The September announcement names two relevant changes: cannon softlocks are fixed, and players who previously rolled snowballs can now use cannons. If your report predates that update, retest on the current build before repeating an old workaround.

The May thread concerns Steam players. The official announcement also contains Xbox fixes, but the thread itself is not an Xbox reproduction record. Include the actual store and device when reporting a continuing failure.

Sources: September 21 official update · Cannon report and replies

Make one controlled retry

  1. Update and retest the interaction

    Use the current game update, return to a cannon and follow its visible interaction prompt. Note whether you rolled snowballs beforehand.

  2. Use Unstuck if you remain locked

    The September update adds Unstuck, which returns you to the last safe standing spot. This can release the position; it is not proof that the cannon’s cause is repaired.

  3. Compare the session

    If the host connection is struggling, note the pulsing indicator. Try the same interaction in your own arranged session if available.

  4. Record a persistent failure

    Keep the exact sequence, build, store, host/client role and outcome for a bug report.

A May reply reports that logging out and back in restored the cannon once. Treat that as a historical player workaround, not a guaranteed current fix.

For the host-connection symptom, use lobby connection help. The controls reference keeps interaction bindings separate from troubleshooting.

Sources: September 21 official update · Cannon report and replies

All player guides