How to Track a Solo RPG Character’s Position Without Drawing a Full Battle Map
When you play a solo role-playing game, track only the spatial facts that can change your next decision: the character’s current area, what is nearby, what blocks movement, and where important exits or objectives are. A few named zones, a short list of relative distances, or a simple route log can preserve a clear picture without the time and detail of a full battle map. This guide focuses on one task: keeping a solo character’s position understandable during exploration and encounters, using notes you can update as the fiction changes.
Start with the decisions position needs to support
Before choosing a method, ask what you need to decide. Is an opponent close enough to attack? Can the character reach the doorway this turn? Is the bridge between the character and the exit? Do two creatures share the same blast area? Record enough to answer these questions consistently; leave out details that would not alter a choice or rule.
This principle is supported by abstract-map practice: a rough map can answer questions about who is next to whom, distance to a target, area effects, and relevant features. The map only needs to clarify the situation. D&D Beyond’s guide to using abstract maps recommends drawing when words alone do not make the situation clear, rather than preparing a detailed map by default.
For solo play, make the test concrete: if you can make the next likely movement or targeting decision from your notes, your tracking method is doing its job. If not, add one useful fact. For example, “the guard is across the room” might be enough until the character needs to slip past the guard; then the relevant feature might be “guard between me and the door.”
Use zones for rooms and compact encounter spaces
A zone is a named patch of space, such as “entry hall,” “workshop,” or “upper balcony.” Give each zone one or two details that affect action: a locked door, a waist-high counter, a flooded floor, or a ladder. Connect zones that have a usable path between them. You can write these as three boxes on scrap paper or as a list with arrows; neither version needs a scale.
For instance: Entry — iron door → Hall — broken pillars → Dais — brazier. Put the character’s marker or initials beside the current zone. If an adversary matters, write its name in the zone too. When the character moves, update the marker and note any obstacle, cost, or consequence required by the game rules.
Fate Core uses zones to track relative positions in a conflict. Its rules treat an unobstructed move to a neighboring zone differently from a longer or impeded move, which may require an action and a roll. That is a useful model for deciding what your own notes should preserve: adjacency, barriers, and whether a route is free or contested. Apply the rules of the RPG you are playing; Fate’s specific movement mechanics are not universal. Fate Core’s movement rules describe this zone-based approach.
Keep zones tied to meaningful boundaries. A whole chamber may be one zone if there is no reason to distinguish its corners. Split it into two or more only when the division matters—for example, when a high ledge, a hazard, or a narrow doorway changes who can reach whom. Too many tiny zones recreate the bookkeeping of a grid without its precision.
Track distance with a few shared terms
Some scenes need to distinguish “within reach” from “takes a while to reach” without assigning exact feet. Choose a small vocabulary and keep its meanings stable. One practical set is engaged (in immediate contact or melee reach), near (reachable with one move, if the route is clear), and far (requires more movement or is only reachable at range). Add blocked when a wall, locked door, or other feature prevents a direct route.
These labels are a table aid, not an automatic substitute for the game’s rules. If your system defines exact weapon ranges or movement distances, use those rules when a boundary matters. Otherwise, a consistent relative scale can prevent repeated re-interpretation. D&D Beyond’s abstract-distance discussion similarly describes positions such as nearby, far away, engaged, and behind as shorthand for relative reach and relationship. Read the abstract-distance and zone examples.
Write relationships only when they matter: “me engaged with raider; archer far, behind the rail.” This is usually easier to revise than a sentence describing every creature’s exact location. When a character moves, update the relationship affected by that move; do not rebuild the entire scene unless it has changed substantially.
Use a route log for travel and exploration
A room-by-room encounter and a journey across a region ask different spatial questions. For overland travel or dungeon exploration, keep a compact route log: current location, previous location, next known destination, and notable connections. Example: Old road → collapsed bridge → mill yard; the forest track branches north from the bridge. Add orientation only if the character has a reason to know it.
For a solo session, a short log also helps you resume after a break. Record discoveries that affect navigation—“the stair descends to the cellar,” “the eastern door is barred from this side”—and leave out scenery that has no bearing on routes. If the character becomes lost, preserve uncertainty in the record: write “possible trail toward the mill” rather than treating a guess as established fact. This last practice is a practical recommendation, not a rule from a particular RPG.
Tools designed for solo play often organize information with lists, scenes, and context. Word Mill Games describes Mythic Game Master Emulator as using scene structure and lists that track important goals and characters, alongside question resolution and prompts. Although this source is about solo-play procedure rather than cartography, it supports a useful distinction: keep enduring facts (known places and connections) available separately from moment-to-moment scene notes. Word Mill Games’ Mythic GME overview.
Make a tiny sketch only when words stop being enough
A sketch does not need to be a map in the full tactical sense. Draw a few circles or boxes for areas, connect them with lines for routes, and add a symbol for the character and any immediate threat. Use arrows for one-way movement, a cross for a blocked path, and a star for the objective. Label the features that could influence the next decision.
This minimal sketch is especially useful when several routes, obstacles, or groups interact. It can show that a character is in the courtyard, a sentry is on the wall, and the only open gate lies across exposed ground. Skip scale and decorative detail unless the game’s rules make measurement important. Abstract-map guidance emphasizes that a quick diagram can be made only as detailed as needed to clarify the action, and that simple boxes with written features can be enough. D&D Beyond’s abstract-map examples.
A good rule of thumb is to add marks when the scene changes, not after every line of narration. Moving from the workshop to the hall changes the character’s zone; turning to face a nearby opponent may change a relationship; glancing at the ceiling may change nothing that needs recording. This keeps the sketch legible and the solo session moving.
Keep position notes consistent with your RPG’s rules
Abstract tracking can become confusing when you quietly switch between narrative judgment and precise mechanics. Decide in advance how to handle the common edge cases in your game: whether an obstacle blocks movement, what counts as being in reach, whether movement past an opponent has a consequence, and how area effects interact with zones. If a rule answers the question, follow it. If the game leaves it open, make a clear ruling before resolving the action and keep that ruling consistent.
Fate Core, for example, specifies that moving more than one zone or moving through difficulty can require an overcome action; a failed roll can leave the character where they started. That illustrates why a position record should include obstacles and routes, not merely the name of the current room. Other systems handle movement differently, so use this as a prompt to check your own rulebook rather than copy Fate’s procedure. Fate Core movement.
If a disagreement appears in your own notes—perhaps a foe is described as both “across the room” and “in melee”—pause and resolve it using the most recent established event. Correct the note, then continue. The note is a memory aid for the shared fiction; it should not quietly create a new obstacle or advantage that was never established.
A repeatable solo tracking routine
At the start of a scene, name the current zone or location. Add only the exits, obstacles, and characters that could affect immediate choices. When the character moves, update their location and any changed distance relationship. At the end of the scene, move lasting discoveries—routes, locked doors, landmarks—to the route log, and discard temporary combat clutter.
A quick example: the character begins in the Gatehouse. The Courtyard is one move away through an open arch; a Watchtower is connected by a narrow stair; a guard is engaged with the character’s ally near the arch. After the character retreats up the stair, change the current location to Watchtower and note whether the guard can follow under the game’s movement rules. You have enough information to answer the next spatial question, but no full battle map to maintain.
The best method is the lightest one that keeps your rulings and mental picture aligned. Use named zones for compact scenes, relative-distance words for quick relationships, and a route log for longer exploration. Draw a few boxes when a choice becomes hard to visualize, then return to prose notes when the scene becomes simple again. This gives a solo player a practical record of position while leaving most attention for the character’s next move.