On PC, use W, A, S and D to move, and hold the right mouse button while dragging to turn the Classic third-person camera. Space is the normal Roblox jump input and is also used for keyboard training in Tongue Escape. A keyboard gameplay example uses Space to deploy the tongue. Check the current tongue prompt before using it away from a treadmill, because the key's effect depends on the action and situation.
PC keys and what to check
Movement, camera and ordinary jumping use Roblox defaults unless a game overrides them. Check these inputs on safe ground before testing an unfamiliar tongue action over a gap.
| Action | PC input | Context and visible result |
|---|---|---|
| Move | WASD | W moves forward, A left, S backward and D right. Position the character on safe ground before aiming. |
| Turn the camera | Hold right mouse button and drag | In Classic third-person view, rotate until the departure and landing are both visible. In first person, move the mouse to look. |
| Zoom | Mouse wheel | Move the camera closer or farther away. Classic mode can enter first person at its closest view if the game permits it. |
| Ordinary jump | Space | The default Roblox jump. A game-specific action can use Space in another situation, so check which action responds. |
| Keyboard tongue launch | Space in the recorded keyboard setup | The tongue extends in the CHALLS example. Check the current tongue prompt and test on an easy opening before relying on that binding. |
| Keyboard training | Space, with repeated effective inputs | Stand on a usable treadmill, press Space, watch Tongue or Level progress, then repeat while working toward the target. |
For training, keep checking the progress display. Standing on a treadmill does not by itself confirm continued growth, and one press is not a demonstrated increase of one whole Level. Stop the training sequence when you reach your chosen target; after leaving and returning, check the input and progress again. Use the training guide for station requirements and a controlled growth test.
Mouse recordings show a click deploying the tongue without naming its button. Keep that action separate from right-button camera dragging. Read the current tongue hint and the stopping and travel prompts; the Space launch example does not establish a Stop or Slide key, second-press rule or hold-and-release sequence.
Mobile and gamepad basics
On mobile, use the left movement joystick and drag the right-side view area to rotate the camera. Use the onscreen jump button for ordinary jumping. Release the joystick while arranging a departure so the character does not drift sideways. Landscape view can give the gap more screen space.
With a gamepad, the left stick moves the character and the right stick turns the camera. The usual Roblox jump is Xbox A or PlayStation Cross. These are navigation defaults, not tested tongue-launch, training or stopping bindings for this game. Use the tongue prompts shown for your device rather than translating the PC Space instruction into a guessed touch button or trigger.
If an input differs, open the Roblox menu and look at Help and the available camera settings. Developers can lock a camera mode, so an unavailable setting is not a tongue-length problem. Before leaving safe ground, check the prompts for starting and ending the tongue path, beginning travel and restarting after landing or attaching. Check Stop, Slide and restart separately; do not assume that the PC launch key also performs those actions.
Frame the departure and the landing
Stop on safe ground and use the camera controls above to frame the starting edge, path and landing together. Choose a broad, visible destination. If an edge launch produces an ordinary jump, step approximately half a step back onto the platform and try the same setup again.
Keep the starting position fixed between attempts. Moving backward adds distance, while moving sideways changes the line through an opening. On mobile, release the joystick while aiming. Reposition if another player's tongue blocks the view; their reach does not measure yours.
Aim through the opening, then check the endpoint
Camera direction can guide the extending tongue vertically and horizontally. Make a small early correction toward the center of an opening and watch the tip. For cramped passages, try first person from stable ground. Reduce camera sensitivity if small movements repeatedly push your aim past the opening.
A tongue ending in clear space before the landing calls for a shorter route or more reach. If the tip reaches but the character falls, check the landing and body clearance. Downward travel has been shown moving faster than upward travel, so leave room to arrive on a descent and inspect an uphill connection before relying on it.
Leave room to finish on the platform
Choose an endpoint inside safe ground. An extension reaching a platform can still carry the character beyond its edge. Use the stopping input shown for your current setup.
After arrival, check that the character is supported before setting the next direction. If you repeatedly overshoot, keep the same departure and move only the intended endpoint inward. Changing reach and angle together would hide which adjustment helped.
Check space for the character's body
A tongue fitting through a hole does not prove the character can follow. Inspect ceilings, sidewalls, pillars, lava and projecting edges along the body path. A route skimming a surface can fail after the tip has passed it.
Aim through the usable opening with room around the character. Watch where contact occurs after a failure. Extra length does not pass through solid walls, so find the opening or marked anchor before adding more Level.
Recognize a honeycomb anchor
Yellow honeycomb surfaces can provide an intermediate attachment on vertical sections. Aim at the marked surface and check that the character has attached before turning toward the next ledge. A plain wall or gray block is not an interchangeable anchor.
While attached, inspect the next target and the space above the route. Use the current tongue prompt to continue; a long extension still needs body clearance and a safe endpoint. For named examples, use the stage targets and obstacle checks.
Check an input on a familiar crossing
Choose a short crossing you recognize and keep equipment and departure unchanged. Check the displayed tongue input, use it deliberately and watch the first response: an ordinary jump, extension or travel. Note which action state you were in when it worked. If the route ends early, check for unintended repeated input before changing reach. Change only one camera or starting-position adjustment on the next attempt, so the result can tell you whether that correction helped.
Diagnose one failed attempt
| What happened | Check | What to change next |
|---|---|---|
| Ordinary jump at departure | Whether you launched from the extreme edge. | Step back onto stable ground and repeat the setup. |
| Tongue ends before the target | Starting position, target and visible endpoint. | Try a straighter reachable line or train for more reach. |
| Tip passes through, body hits | Ceiling, sidewalls and projections along the path. | Choose a line with clearance for the character. |
| Character falls beyond the platform | Whether the route ends near or past its edge. | Bring the endpoint inside the landing. |
| Route ends unexpectedly | Unintended repeated activation or early release. | Check your input before repeating the attempt. |
| Honeycomb approach fails | Whether you aimed at the marked sticky surface. | Reframe the anchor and inspect the approach for obstructions. |
A jump has rescued particular near-landing mistakes, but it cannot supply missing tongue length or guarantee recovery over lava. After a fall, check where the game actually returns you. Keep a reliable approach you can repeat, and check your returned position before planning the next run.