Sarab Controls & Settings

Why controls deserve their own page

Sarab will end your run for ordinary reasons: you opened the wrong menu, you could not toggle light in time, or mobile touch targets ate your sprint. Master binds in a calm lobby minute, then take that confidence into the dark. Pair this page with Getting Started and How to Survive.

Exact on-screen labels may be Arabic. Learn what the input does, not only what the English word would be.

PC controls (typical Roblox horror layout)

These are the patterns most Roblox horror experiences use. Confirm in Sarab’s pause/settings if a custom bind screen exists:

Action	Common input	Survival note
Move	WASD	Strafe while listening; do not hold W into every door
Look	Mouse	Slow pans while scanning corners
Sprint	Shift	Budget stamina — see survival guide
Interact / pick up	E (sometimes click)	Wait for the prompt; spam-clicking can skip feedback
Flashlight / tool	Click or a number key / F-style toggle	Rebind mentally: “light is a button, not a lifestyle”
Jump	Space	Useful for small ledges; not a panic teleport
Menu / Roblox escape	Esc	Close GUIs before a chase escalates
Push to talk (if used)	Your Discord/Voice bind	Keep it off the same key as interact

If you rebound Roblox movement globally, make sure interact is not fighting your clip tools or browser overlays.

Mobile controls

Mobile players clear Sarab, but the default thumb layout fights horror:

1. Move the jump/sprint cluster so your right thumb can camera-swipe without hitting jump.
2. Practice interact on harmless props before you need a key under pressure.
3. Use headphones with a mic if you call out — speakerphone echo ruins audio reads.
4. Lock orientation to landscape for stable UI.
5. Lower touch sensitivity if you over-flick into walls during chases.

When the codes or settings panel opens, make sure the on-screen keyboard will not cover Submit — details in How to Redeem Codes.

Sarab movement tips

• Peek with purpose — shoulder check corners instead of sprinting wide.
• Backpedal while listening if a cue is unclear; walking forward into unknown audio is how ambushes win.
• Doorway discipline — stop in the frame, look both ways, then commit.
• Vertical awareness — stairwells change audio; pause on landings.
• Crowd etiquette — in busy 25-player servers, do not body-block the only exit while looting.

Route memory ranks high on the Tier List. Controls are how you execute that memory under stress.

Interaction tips for Arabic UI

• Wait for the interact highlight before mashing.
• If a prompt appears in Arabic, interact anyway when the context is obvious (door handle, key glow), then translate screenshots later if the note matters.
• Assign a “reader” on your team so one person handles translation while others cover — teamwork section in How to Survive.
• Do not open large note UIs in exposed hallways; drag the note to cover first.

Horror settings checklist

Audio

• Headphones on
• SFX / ambient high enough to hear directional cues
• Music lower than footsteps and pursuit tells
• Chat sounds reduced so Discord/Roblox pings do not mask growls
• Test by standing still at spawn for ten seconds and naming three ambient layers

Graphics

• Prefer stable frame rate over max shadows if your device stutters in dark scenes
• Avoid pitch-black gamma tricks that also hide threat silhouettes — crush blacks carefully
• Turn off heavy post-effects if they add input latency on low-end PCs
• On mobile, drop particles/quality one notch during peak hot lobbies for smoother peels

UI / quality of life

• Increase UI contrast if Arabic text is hard to parse on your monitor
• Disable unnecessary overlays (FPS meters that cover prompts, colorful desktop capture widgets)
• Keep a second device ready for translation screenshots

Pre-run controls warm-up (60 seconds)

1. Toggle light three times.
2. Sprint a short distance and stop with stamina remaining.
3. Interact with a safe prop twice.
4. Open and close the Roblox menu once so Esc muscle memory works.
5. Confirm voice chat is not broadcasting noise into your own headphones.

Then begin the session goals from Getting Started.

Common control failures

Failure	Fix
Sprint key stuck in brain as “always on”	Consciously walk for one full minute
Interact key rebound to something awkward	Reset to default for horror week
Mobile jump during camera swipe	Reposition jump button higher
Light toggle forgotten	Bind a memorable phrase: “beam check” every landmark
Menu opened mid-chase	Practice Esc close during calm

Accessibility notes

• If you rely on visual captions, pair with a hearing teammate when possible — Sarab is audio-forward.
• Colorblind players should not depend solely on red threat UI if the map uses subtle lighting tells; lean harder on sound.
• Photosensitivity: horror maps flash; lower bloom and take breaks.

Related pages

• Getting Started — first session flow
• How to Survive — apply binds under pressure
• Walkthrough — objectives once control is comfortable
• Tier List — which habits to prioritize
• Scripts — do not “fix” controls with injectors

Good controls will not clear Sarab alone — but bad controls will end otherwise perfect runs.