REDLINER Slide Guide

Slide briefly makes the player frictionless and supports drift speed.

What Slide Does

Slide maintains momentum by briefly making the player frictionless and adding a minor speed boost. It can be used while grounded or airborne.

Drifting

The TRELLOLINER note says sliding drift uses strafing logic, but needs roughly 45 degrees more turning than regular strafing. Practice this before trying to fight at full speed.

Wide slash is only usable while sliding for a brief period and costs two stamina charges. That makes slide a combat setup, not only movement.

Source and Freshness

Source checked: TRELLOLINER snapshot, checked 2026-06-17.

Raw path: docs/redliner/raw/data/trelloliner-summary.json.

Content intelligenceREDLINER slide guide

Search Intent And Player Task

Players want to understand slide momentum, drift timing, and why slide also affects combat.

Use this page to: Use slide to preserve speed, set up wide slash, and turn routes without losing camera control.

Evidence Used

  • Movement query results include dash, slide, grapple, wallrun, and movement-chain pages.
  • The Trello movement notes describe slide as frictionless momentum and drifting support.

Information Gain

The page connects slide to wide slash cost and drift angle, giving users a concrete reason to practice it before advanced routes.

Practice Plan

  1. 1. Slide on flat ground, then repeat after a dash to feel the retained speed.
  2. 2. Practice drift turns before trying to aim a slash at full speed.
  3. 3. Use slide before wide slash only when you can afford the two-stamina cost.

Common Mistakes

  • Sliding without a destination and losing camera alignment.
  • Treating slide as movement-only while ignoring the wide slash window.
  • Forcing slide routes when stamina should be saved for defense.

Source Boundaries And Update Plan

REDLINER changes quickly, so this page separates stable source facts from practice advice. Official Roblox metadata is used for game identity, controls, creator information, and public game stats. TRELLOLINER is used for mechanics, weapon values, map-object behavior, and failure states, but exact balance-sensitive numbers are treated as snapshot data until a later live pass confirms them again.

The practical recommendation is to use this page as a training route, then verify the result in game. If a future update changes a weapon value, control behavior, code status, or movement interaction, the source log should be updated first and the affected article should link back to that change. That keeps each REDLINER guide useful without pretending that unsourced community claims are confirmed facts.

For ranking quality, the page also needs to create a useful next click. After reading the mechanic or weapon note, compare it with the related tool, run one practice drill, and then open a neighboring page that explains the failure state. That pattern is intentional: REDLINER players rarely solve a search with one isolated definition. They usually need a mechanic, a route, a counter-risk, and a source boundary before the advice is safe to use.

How To Use This REDLINER Guide In Search Context

This page is written for players who arrive from a narrow REDLINER search and need a practical answer before their next match. The target query is not treated as a title swap. The page starts with the verified mechanic or route fact, adds the player task behind the query, and then sends the reader toward the tool or neighboring guide that completes the job.

If the topic is movement, the useful outcome is a route choice that saves stamina, keeps grapple available, and avoids turning dash into a fake invincibility button. If the topic is combat, the useful outcome is a safer read on parry, clashing, bullet value, or weapon pressure. If the topic is setup, the useful outcome is a control map that keeps the most important inputs reachable instead of promising universal sensitivity numbers.

The page should also help you avoid bad search results. REDLINER has similarly named legacy and unrelated pages in the wider web results, so the canonical source layer matters: current Place ID 94987506187454 for game identity, TRELLOLINER for mechanics snapshots, and the source log for updates. When those layers disagree or become stale, the safe answer is to label the limitation and recheck the live game before presenting a balance value as current.

Related Guides