How to Place Persistent Status Counters Over Virtual Tabletop Tokens
To keep a condition count visible as tokens move, attach the counter to the token or use a tabletop tool designed to display a token-linked label. Set a consistent position, limit how many counters compete for space, and test visibility from a player’s view. A free-floating map label can look like an overlay, but it may stay behind when the token moves. This guide helps a game master choose and check a practical setup.
Decide what the counter needs to track
First distinguish a changing number from a condition icon. Use a counter for values players need to read repeatedly, such as a countdown, a number of marked targets, or a temporary resource. Use a status icon when the main question is simply whether a condition applies. If the count changes as turns pass, agree on when it changes and who updates it; the visual marker alone may not explain the game rule.
Also decide who should see it. A public condition or shared objective can sit on the map for everyone. A hidden or owner-only value should use a platform’s visibility controls, if available, or remain in a private tracker. Don’t assume a map overlay is private just because it is small or unobtrusive.
Choose a token-linked marker before making a loose label
Prefer the tabletop’s built-in status marker or token counter when it can display the needed number and remain attached to the token. Foundry VTT, for example, displays status effects as icons over token art; its token HUD also supports configured resource bars, whose visibility can be set for owners or everyone. That makes a built-in status icon a good fit for a yes/no condition and a resource bar a better fit for a value that belongs to an actor. Foundry VTT: Tokens
Some platforms provide counter or label extensions. Owlbear Rodeo’s extension listing includes a Token Counter described as adding a counter to a character token, and a customizable labeler for tracking conditions. Check the current tool’s description and behavior before relying on it: a listing tells you its stated purpose, not exactly how it handles every map, user permission, or scene change. Owlbear Rodeo: Extensions
If your tabletop has no suitable attached counter, place a text or number element beside the token as a manual fallback. Treat this as a paired object: move it whenever the token moves, and remove both together. This approach is more vulnerable to drifting out of alignment, especially in a busy scene.
Set a position and a visual rule
Choose one location for every counter, such as above the token or just outside its upper-right edge. Keep it away from the token’s nameplate, resource bars, other condition icons, and important map details. If the platform lets you choose a marker edge, use the same edge throughout the encounter. In Roll20, for example, token markers can carry a numeric badge, and the marker layout can be positioned along different sides of tokens. Roll20 Help Center: Mod Scripts—Objects
Use a short label when the number would otherwise be ambiguous: “2” may mean two rounds, two stacks, or two charges. A compact label such as “R2” can identify a round count, while a distinct icon paired with a number may suit a stack count. Keep the convention stable across the encounter so players don’t have to infer what each number means.
Avoid piling several large icons or text labels on one token. Foundry’s documentation notes that a token can have only one large status overlay at a time, while its smaller status icons appear over the token art. If several conditions matter, prioritize the one that needs immediate attention and use a separate tracker for the rest. Foundry VTT: Tokens
Add the counter and test the anchor
Use this setup sequence for a token-linked counter or marker:
- Select one representative token and add the desired status marker or counter using the platform’s token controls or an installed extension.
- Enter the agreed label or number, then place it at the chosen edge or position.
- Move the token a few grid spaces and check whether the counter travels with it. If it does not, you have a loose map object; either use an attached tool or adopt the paired-object routine.
- Zoom out to the view players are likely to use. Confirm the counter remains legible and does not cover a name, face, bar, or nearby token.
- Check visibility from a player account or player-view mode when possible. Foundry’s token resource bars have explicit visibility options, but other tools and extensions may behave differently. Foundry VTT: Tokens
That movement check is the key test: visual proximity while stationary does not prove that an element is anchored. Also test with two adjacent tokens and with a larger token if the scene uses them. Counters that work on one isolated token can overlap when a group closes ranks.
Make updates predictable
Agree on a small update routine before play: who changes the number, what event changes it, and when it is cleared. For a round countdown, for example, identify whether the count changes at the start or end of a turn. Apply the update at the agreed moment and remove the marker as soon as it no longer applies. This reduces stale counters that look authoritative after the underlying condition has ended.
Where a marker can show a number, use that numeric badge rather than adding a separate text object, if it stays readable at your usual zoom. Roll20 documents status markers with numeric badges and supports adding or removing markers on tokens. The specific controls differ by tabletop, so use the platform’s own interface rather than assuming the same click or drag behavior everywhere. Roll20 Help Center: Mod Scripts—Objects
Troubleshoot counters that disappear or drift
If a counter disappears, check whether it was attached to the token, whether the marker is hidden by a visibility setting, and whether it belongs to the current scene. In Foundry, placed tokens belong to scenes, and resource bars have configurable display rules; a different scene or user view can therefore look different from the one used to set up the token. Foundry VTT: Tokens
If it drifts, remove the loose label and recreate it using a token-linked feature if the platform supports one. If a manual pair is the only option, move the label immediately after each token move and make a quick sweep after group movement. If counters overlap, reduce the number shown on-map, move them to a consistent side, or reserve the map for the most time-sensitive value while tracking secondary details elsewhere.
If players report different displays, compare their view settings and permissions, then check with a second player account. Don’t assume that a marker visible to the game master is visible to everyone. Test the exact combination of tool, scene, and player role you plan to use.
Run a final scene check
Before the encounter, verify three things: the number means one clear thing, it stays with its token when moved, and the intended players can read it at their normal map zoom. Then check that moving or removing the token doesn’t leave a stray label behind. These small checks make an on-map counter useful throughout play rather than a decoration that must be reinterpreted or repaired mid-scene.