The Loopler infinity-track iconThe Loopler GuidesPlay Demo

Cards, Gates, Charms & Garage Mechanics

The Loopler is built around repeated automated laps. Your main control is the build around the car: choose and upgrade Cards, place Gates in limited track slots, arrange their trigger order, and combine them with passive Charms.

Quick answer: Cards shape the run's active build, Gates turn track position and order into repeatable triggers, and Charms add passive support. When an interaction is unclear, test one layer at a time and keep the Demo version in view.

How Systems Work Together

The useful build question is not which isolated part has the largest number. It is whether the system fires often enough to matter across repeated laps:

  1. Cards define the active plan and the events worth improving.
  2. Trigger conditions decide whether a Card or passive effect contributes during an ordinary loop.
  3. Gate placement controls when track effects happen relative to the rest of the lap.
  4. Charm scaling rewards a build that already meets its condition reliably.
  5. Infinity scaling should be treated as announced full-game scope until the released build can be tested directly.

That order keeps launch advice useful without inventing a complete item database or a final balance formula.

Cards

The official Steam Demo description says players pick and upgrade cards. In practical build terms, every Card should answer one of three questions:

  • What repeatable event does this improve?
  • Which current Card, Gate, or Charm makes that event more valuable?
  • Does the build meet the condition often enough for the choice to matter?

Use those questions before selecting the largest visible number. A conditional Card with no reliable trigger is weaker than a smaller effect that contributes every loop.

Gates and trigger order

Gates occupy limited track slots. Their position therefore matters for more than presentation: it determines when their effects occur relative to the rest of a lap.

To troubleshoot Gate mechanics:

  1. Identify the Gate whose output matters most to the current build.
  2. Note what must happen before that Gate triggers.
  3. Place supporting effects earlier when the order is relevant.
  4. Run the same setup once before changing another slot.

Older community questions discuss whether a Gate is being upgraded or replaced. Treat any exact old-interface instruction as an early Demo snapshot, not a universal rule for the updated Demo or full game. The durable decision is to check whether the operation changes the existing Gate, its level, or the slot occupant before confirming it.

Charms

The full-game announcement names Charms as a large passive system. A passive effect is most useful when it reinforces what the build already does reliably. Compare Charms by asking:

  • Is the condition active during a normal loop?
  • Does it support the main scoring or cycling interaction?
  • Would a more general passive prevent the current failure more often?

The announced total—70 Charms—describes planned full-game scope. It is not a claim that every Charm is present in the current Demo or that a complete confirmed effects table exists.

Full Game Systems Preview

The announced full-game scope points to a larger system than the Demo: Tracks, Cars, Loadouts, Challenges, Cards, Gates, Charms, and Infinity Mode all matter to build planning. Use that as a roadmap for what may need testing after launch, not as proof of final item names, unlock conditions, or balance rankings.

Until the release build is checked directly, this page treats the full-game systems as announced scope. It explains how to ask better build questions now; it does not publish a complete database or final meta list.

Modifiers and inheritance

Modifier inheritance has produced player confusion, including discussion of a Smooth Tuned Engine interaction. The discussion confirms that the terminology is confusing, but it does not establish an exact universal inheritance formula.

Use a controlled check instead:

  1. Record the vehicle part and modifier before changing the Loadout.
  2. Change only the relevant part or selection.
  3. Compare the displayed effect and the next run's matching trigger.
  4. If the result differs from older advice, prefer the observed updated-Demo behaviour and note the version.

This keeps modifier inheritance separate from older unlock advice. A pre-overhaul colour or unlock explanation may describe its historical build correctly while being wrong for the current Loadout.

Garage and Loadout

The updated Demo uses a Loadout context, while an older pre-overhaul question shows that unlock terminology has confused players. Available official and developer information does not establish exactly how “unlocked,” “available,” and “selected” relate in the current build.

Use the current interface as the authority: note the label and visible state before a run, change only the relevant selection, then compare what the next run actually uses. Do not carry an older colour or unlock instruction into the updated Demo solely because the same term still appears.

Apply the mechanics

Once the terms are clear, return to the Demo build diagnostic. It turns these mechanics into a one-change-at-a-time test for scoring, Silver, and drift choices.