Moving two squares, attacking and then moving again can all happen in the same turn. Taking an action does not reset your available movement. With Speed 30 feet and 5-foot squares on normal ground, spending 10 before the attack leaves 20 afterwards: four squares, assuming no other rule intervenes.
One route, two parts
An original example using the 2024 D&D Basic Rules: an adventurer with Speed 30 feet moves two ordinary squares, resolves an Attack action and wants to continue down a clear passage. She has spent 10 feet; taking the action does not refund them.
The official movement rules allow movement before and after actions, Bonus Actions or Reactions on the same turn. Our example adds no Dash, special speeds or Difficult Terrain. The calculation is 10 + 20 = 30, not two separate 30-foot budgets.
Bring that record to DMGrid
Agree the scale and route with the DM before moving. After the first part, state that 20 feet remain. Return to that balance after resolving the attack and before moving the token. A session note such as “10 spent / 20 available” can retain the calculation. It is a suggested record, not an automatic counter attributed to the app.
DMGrid connects the tactical board, turns and campaign notes. It also documents circular walking and running ranges. A circle does not prove that the app deducted the first segment, or authorize entry into any square. Check actual costs and resolve rules at the table.
Three checks when continuing
- Remaining movement: what did you spend before the action? Here, 20 feet remain rather than 30.
- The next route: recalculate for Difficult Terrain or another extra cost. Four squares only follows from the normal-ground assumption.
- Leaving a reach: splitting movement does not remove Opportunity Attack rules. Resolve whether one applies before continuing rather than inferring permission from token movement or a circle.
You can also stay where you attacked; you need not spend every remaining foot. The useful record reflects what actually happened.
DMGrid is a paid Windows beta. Review its public facts and product overview to assess whether its board-and-notes workflow suits your table. This example establishes neither automated rule resolution nor an interactively tested session.