Touch, confirmed vs in-game

TTK Testing mobile controls

Mobile is an official platform. The published inputs are still the PC keys. Use this page to find the matching actions on your screen, and confirm every touch target in the client.

Last checked: October 25, 2026.

The short answer

Sable Digital lists mobile alongside PC, Xbox, and PS5 as a platform for TTK Testing. The official control list that ships with that statement is a PC list: M1 fire, M2 aim, C crouch, Q and E lean, number keys to swap weapons, and P for helmetcam. There is no official touch map in the description we checked on October 25, 2026, and this wiki will not draw one. On a phone or tablet, the buttons that count are the ones the current client paints on your screen. Treat every sentence below that is not the PC list as a way to discover those labels, and confirm each one in game before you trust it.

What is confirmed, and what is only a Roblox habit

The platform sentence and the key list come from different levels of detail. "Mobile" tells you the experience is offered for touch devices. It does not tell you where the fire button sits, whether lean is on screen, or whether helmetcam has a tap target. The PC keys tell you which actions exist in the design the developers chose to publish. They are the names to hunt for on a touch layout: fire, aim, crouch, lean, weapon swap, helmetcam. They are not coordinates.

Roblox on mobile, as a platform habit and not as a TTK diagram, usually gives an experience a thumbstick or tap-to-move control plus extra buttons the experience defines. Many shooters on that platform are easier to read in landscape because the view is wide. That is a general Roblox habit. It is not a TTK requirement we have verified. If the client opens in portrait, play the orientation it gives you, or switch only if the client offers a control you can see. Do not install a third-party "mobile layout" overlay. This wiki has not verified one, and the editorial policy does not send players to unofficial executors or button packs.

Transparent Optics is a setting, not a weapon, and the official description says it simulates both eyes open. If you can open Settings on mobile, that is the setting to test when a sight blocks the screen. The path of taps to reach Settings was not published in the sources for this page. Follow the labels in the client. The Transparent Optics page explains the comparison to run once you find the toggle. Screen size changes how much a blocked sight matters. It does not change the official description of the setting.

Actions worth finding, in the official order

Use the same order as the PC controls page, because that is the order the official list supports. On touch, "find" means "locate the on-screen control that performs this action," not "press this invisible key."

ActionConfirmed on PCOn mobile
FireM1Find the on-screen fire control. Confirm it before a fight. Do not assume a right-side button without looking.
AimM2Find the on-screen aim control. Check whether it holds or toggles by testing once, in a quiet moment.
CrouchCFind the on-screen crouch control if the client shows one. Absence means we do not invent a substitute gesture.
LeanQ and EFind left and right lean if the client shows them. The PC letters do not become swipe directions by default.
Swap weaponNumber keysFind the weapon-switch control the client shows. A title that includes [NEW AR15] does not tell you which icon that is.
HelmetcamPFind the helmetcam control if it is drawn. It is a separate action from aim on PC. Test it separately on touch too.

The June 2, 2026 DevForum post names additional systems: stances, lasers, flashlights, callouts, door kicking, and lockpicking. It does not publish touch targets for them. If an icon appears, read the icon. If it does not, do not add a gesture from a different game. The post also says the project is meant to be easy to pick up. That is a design goal, not a guarantee that the first mobile layout you see is final. The description says updates can be weekly or daily, so a button can move. Re-read the screen after the Roblox updated field moves. The October 25 check put that field at 2026-10-23 UTC.

A first mobile session that stays inside the evidence

  1. Confirm the experience is place ID 120189115846709, creator Sable Digital, before you judge the buttons. A different shooter will teach you the wrong layout.
  2. Wait until you are spawned and the touch controls are visible. Open no external guide beside you that assigns fingers to corners.
  3. Look for a fire control and an aim control. Tap each once when no one is in front of you if the mode allows a safe test, or tap aim first so you only change the view. Note whether aim stays on.
  4. Look for crouch and for two lean directions. If you cannot see them, write "not on my screen today." Do not replace them with a pinch or a shake because another Roblox game uses that gesture.
  5. Find weapon swap and cycle until you can tell the equipped label changed. If you are hunting the AR15 named in the October 25 title, follow the AR15 page and stop when the label matches or when you have cycled every slot.
  6. Find helmetcam and press it separately from aim. Return to the previous view before you move into a fight.
  7. Open settings only through the buttons the client provides. If you find Transparent Optics, toggle it once and look at the same sight. Keep the readable one.
  8. If a control does nothing, use the same boring checks as on PC: the Roblox menu may be open, a popup may be covering the button, or the action may not apply in the current stance. Tap once more. Do not rapidly tap every button.

Performance is part of aiming on a small screen, and this site still has no verified graphics preset to copy. If the view stutters, solve that before you judge a weapon. The settings page tells you to get a stable picture first and to change one option at a time. That advice is editorial, and it applies on mobile without a fake DPI number. We do not publish a sensitivity value. The official sources do not give one.

What to write down

Keep a four-line note: date, device type in your own words (phone or tablet is enough), which of the six actions you found a control for, and which you did not. That note is your layout. It is not a chart for other players until the official description prints one. If you mail it to hello@ttktesting.com, label it as your screen, not as the standard. We will not turn one phone screenshot into a site-wide button map. We also will not publish your username.

Server size still matters on a phone. The October 25 API maxPlayers value is 12, and free-for-all play can come from more than one direction. A comfortable chair and a readable sight do not reduce that. The FFA habits page is about angles and the confirmed actions, not about a device. Read it after you can fire and aim on purpose.

Common mistakes

  • Printing the PC letters as if a phone had a keyboard. M1 and P are confirmed for PC. They are the names of actions, not touch spots.
  • Downloading a "TTK mobile buttons" image from a video description. Video layouts go stale whenever the client changes, and the update cadence is weekly or faster.
  • Assuming lean does not exist on mobile because you have not seen Q and E. Look for the action. If the button is missing, say it is missing on your client today.
  • Using a code or a Discord "mobile patch" to change controls. No verified code exists, and no official Discord invite is on the Roblox surface. See codes and Discord.
  • Judging the AR15, or any weapon, from a blocked sight on a small panel. Fix the view with the official Transparent Optics test before you decide the weapon is unusable.

FAQ

Does TTK Testing support phones?

The official description names mobile with PC, Xbox, and PS5. That is the support statement. It is not a button chart.

Can you publish the touch layout?

Not as a fact. No touch map was in the October 25, 2026 sources. The honest page teaches you how to read the client you have.

Is landscape required?

Not by any source we checked. Landscape is a common Roblox shooter habit. Confirm the orientation your client uses.

Why do PC guides still matter on a phone?

They name the actions the developer bothered to publish: fire, aim, crouch, lean, swap, helmetcam. Those names are what you search the touch HUD for. The letters themselves stay on the keyboard.

What if my buttons do not match a friend's phone?

Write both notes down with dates and device words. Do not average them into one map. A settings difference, an update, or a different menu state can change the screen. The primary source remains the client in front of you.

Sources

Last checked: October 25, 2026. Touch coordinates on this page are intentionally absent.