Quick answer
Choose separate jobs for the bag carrier, escort and defender in Hit a Lick. Use a decision exercise rather than an unverified fixed route.
Source: Trapstar Games / Valve · checked 2026-10-22 ↗What should the carrier and escort each accomplish?
Treat the carrier’s job as moving the objective toward a return opportunity and the escort’s job as reducing the next interruption. These are suggested team roles, not mandatory game classes. The description does not establish carrier movement penalties, forced weapon restrictions or player collision. Avoid building a plan around any of those unverified mechanics.
Why can winning distant fights leave the bag untouched?
Before an attempt, name one immediate task for each willing teammate. One person can watch the next exposed approach while another keeps attention on the home objective. If nobody has agreed to defend, do not quietly assume that a distant teammate is doing it. A short request is more actionable than blaming the team after a failed return.
Where should an escort look while the carrier moves?
Choose complementary attention rather than both staring at the same target. Ask the carrier which immediate direction they intend to move, then cover a plausible interruption they cannot comfortably inspect at the same time. This is general positioning advice, not a tested map route. Do not infer that standing beside the carrier physically blocks movement; collision has not been established here.
Should the carrier turn around to help every fight?
Use the objective as the decision point. If an escort starts an optional fight away from the return, bringing the bag into that fight can turn one unnecessary risk into two. The carrier can keep attention on the next safe decision while the escort communicates whether the threat actually affects that movement.
If the intended approach becomes unsafe, pause the plan and reassess available cover rather than insisting on the original route. The escort should report a concrete observation, such as the direction of incoming fire, instead of promising that an entire area is clear. Neither player has complete information, and this article does not guarantee a safe return.
Why should old bag routes be checked again?
Update 1.0.2.0 reports layout changes on TheStrip, removal of a Chicago Mall door leading outside and a fix for an exploit that could despawn the bomb or bag. Those are developer reports. They are reasons to question an old route demonstration, not proof that a particular route was tested successfully on the installed version.
After an attempt, review one decision: did the escort reduce an immediate interruption, or did both players abandon the return for the same duel? Keep the map and build with any notes. Use the main Hit a Lick guide for the mode overview; use this exercise to discuss division of attention without inventing timers, scoring prerequisites or fixed shortcuts.
Common questions
What should the carrier and escort each accomplish?
The Steam description defines Hit a Lick around taking the opposing bag back to your hood while protecting your own. That gives the carrier and nearby teammates a shared destination, but it does not make every nearby opponent an equally useful target. A fight that attracts both players away from the return can undermine the purpose of the escort.
Why can winning distant fights leave the bag untouched?
In an October 14 Steam discussion, BigKneeGuard described matches where players pursued distant kills and left the bag uncontested. This is one player’s dated experience, not a measurement of current match behavior. It identifies a useful decision problem: your group can be busy fighting without creating a practical objective attempt.
Where should an escort look while the carrier moves?
Consider this hypothetical exercise: the carrier is about to leave cover, the escort sees an opponent farther down a lane, and another approach remains unchecked. The useful question is whether that opponent can interrupt the next move. Chasing a distant duel may leave the unchecked approach available to someone closer to the carrier.
Evidence, sources & revision notes
Version & evidence scope: Developer announcements: 1.0.2.0. Later builds have not been verified here. How we verify ↗
Revision history
- — Compared the named source material and recorded the limits of the conclusions.
Did this help you take the next step?
Send details to the editor ↗