Shot-Calling and the Ping System
Most solo queue comms either say nothing useful or say it as blame. This page covers the two things that actually move games: reading pings as real information instead of generic alerts, and running the basic layer of shot-calling every game, whether or not you’re the one making the big calls.
Pings Are Information, Not Just Alerts
Every ping carries a specific, decodable meaning - the same information a voice call would give, just faster to send and impossible to miss in the middle of a fight. Treating pings as generic noise ("something happened over there") throws away most of what they were built to communicate.
| Ping | What It Actually Communicates |
|---|---|
| Missing (danger) ping | Not just "watch out" - it is a location and a direction: where the enemy was last seen and, by omission, where they might now be. A missing ping with no follow-up is half the information it could carry. |
| On My Way / Assist Me | A commitment with a timer attached - the recipient reads it as "help is coming, hold the position" and plays differently because of it. Pinging it without following through costs more than staying silent would have. |
| Retreat (caution) | Fastest way to say "this trade/fight is no longer winnable" without a chat message - useful specifically because it arrives before anyone has time to type. |
A missing ping placed the instant a laner disappears is worth more than the same ping placed ten seconds later, once the gank it warned about has already landed - timing is part of the information, not a detail.
Two Layers: the Caller Everyone Should Be, the Caller Someone Should Be
Solo queue teams rarely have an assigned shot caller, which leads to a common misread: assuming shot-calling is a role you either have or don’t, so nothing gets called at all. In practice there are two separate layers, and only one of them requires stepping up.
| Layer | What It Looks Like |
|---|---|
| Basic caller (everyone, every game) | Calling your own lane's missing enemy, calling an objective as available the moment its timer allows, calling your own summoner spells as down after using them. No leadership required - just information your team cannot see for themselves. |
| Primary caller (usually one player, not required) | Deciding *when* to act on the information above - "group top," "take the fight," "back off, we lost the read." Requires reading the whole map at once, not just your own lane, and being willing to be wrong out loud. |
Running the basic layer consistently, every game, does more for a team’s actual decision-making than one good primary call in a game where nobody was tracking missing enemies or objective timers in the first place.
Mistakes By Rank
Every rank band below is a version of the same underlying problem: comms that react to what already happened instead of shaping what happens next.
| Rank Band | Common Comms Mistake | The Fix |
|---|---|---|
| Iron-Bronze | Typing a call only after something has already gone wrong, as a complaint rather than information. | Ask whether a message contains a plan or information before sending it - if it only contains blame, it was never a call in the first place. |
| Silver-Gold | Pinging danger once, then going silent even as the situation keeps changing. | Treat a ping as a snapshot, not a standing alert - re-ping when the read changes, the same way a vision check gets repeated, not done once. |
| Platinum+ | Making a correct call that nobody follows, then escalating in chat instead of adjusting the call. | A call that isn't landing is a delivery problem, not a teammate problem - shorter, earlier, or paired with a ping usually lands better than the same call typed louder. |
How This Ties Into the 12 Focuses
Shot-calling does not have one dedicated focus of its own, but three existing focuses meet directly at this page:
- Comms Discipline - that focus measures something narrower than shot-calling (keeping chat complaint-free), but the same discipline applies here: a call that turns into blame the moment it doesn’t land stops being a call at all.
- Minimap Awareness - a ping is only as good as the read behind it; this page’s whole first half is what to actually do with the minimap information that focus is training you to track.
- Objective Timer Awareness - calling an objective the moment its timer allows is the single most common basic-caller job, and the exact habit that focus’s own drill trains.
None of this replaces picking an actual focus to hold for a block of games - it is context for whichever one your baseline points you toward, comms-related or not.