Town walking is choppy; match the overworld walk #52

Closed
opened 2026-11-08 18:34:24 +00:00 by Grok · 1 comment
Member

Summary

Walking inside a town is choppy. Holding a direction on the overworld glides from tile to tile. Town walking should match that overworld motion.

Where

scenes/world.tscn while place is town. Calwen is the first street that shows it. The Waking Field path is the reference walk.

Both places already share one presenter, scripts/ui/world_view.gd:

  • The hero moves with smoothstep from tile center to tile center over FieldRules.walk_seconds_per_tile (0.25 s unencumbered, 1/3 s when the inventory is over its cap).
  • The camera eases toward the hero each frame.
  • Each accepted step calls _paint_if_needed(true), which clears and repaints the window around the party.

Town cells resolve through the town layout and TownSurround. Overworld cells use MapBook. A stall on the town path would show up as a hitch between tiles. That cause is not confirmed.

Rules

  • Game Design §3.1: four cardinal directions, one tile per step, unencumbered walk speed 4 tiles per second on the overworld and in towns.
  • Game Design §10: while the inventory is over its cap, movement speed is 25% lower.
  • Technical Outline §4.4: unencumbered speed is 4 tiles per second; over the inventory cap, speed is 3 tiles per second. A town step advances 0 time units.
  • Technical Outline §6: the field view paints a window around the party. Water and lava advance a frame without clearing the window.
  • Game Design §11.1: world tiles are 32×32.

Expected

Holding a direction in a town moves the party with the same glide as the overworld. Unencumbered speed is 4 tiles per second. Over the inventory cap, speed is 3 tiles per second. The hero and the camera do not pause, snap, or hitch between tiles while the direction stays held.

Acceptance criteria

  • A straight walk down a Calwen street matches a straight walk on the Waking Field path: 4 tiles per second unencumbered (Game Design §3.1, Technical Outline §4.4).
  • The same comparison holds at 3 tiles per second while the inventory is over its cap (Game Design §10, Technical Outline §4.4).
  • The hero sprite and the camera glide between tile centers the way they do on the overworld. No visible pause or snap while the direction stays held.
  • The walk keeps a steady frame rate. The playtester frame-time hitch detector (Technical Outline §11.1) does not flag that town walk. A uniformly slow town is still a failure when it does not match the overworld glide.
  • Grid rules stay: one cardinal tile per step, walls, doors, gates, and town time (0 units per step, Technical Outline §4.4) unchanged.
  • Dungeon floors are out of scope.
## Summary Walking inside a town is choppy. Holding a direction on the overworld glides from tile to tile. Town walking should match that overworld motion. ## Where `scenes/world.tscn` while `place` is `town`. Calwen is the first street that shows it. The Waking Field path is the reference walk. Both places already share one presenter, `scripts/ui/world_view.gd`: - The hero moves with `smoothstep` from tile center to tile center over `FieldRules.walk_seconds_per_tile` (0.25 s unencumbered, 1/3 s when the inventory is over its cap). - The camera eases toward the hero each frame. - Each accepted step calls `_paint_if_needed(true)`, which clears and repaints the window around the party. Town cells resolve through the town layout and `TownSurround`. Overworld cells use `MapBook`. A stall on the town path would show up as a hitch between tiles. That cause is not confirmed. ## Rules - Game Design §3.1: four cardinal directions, one tile per step, unencumbered walk speed 4 tiles per second on the overworld and in towns. - Game Design §10: while the inventory is over its cap, movement speed is 25% lower. - Technical Outline §4.4: unencumbered speed is 4 tiles per second; over the inventory cap, speed is 3 tiles per second. A town step advances 0 time units. - Technical Outline §6: the field view paints a window around the party. Water and lava advance a frame without clearing the window. - Game Design §11.1: world tiles are 32×32. ## Expected Holding a direction in a town moves the party with the same glide as the overworld. Unencumbered speed is 4 tiles per second. Over the inventory cap, speed is 3 tiles per second. The hero and the camera do not pause, snap, or hitch between tiles while the direction stays held. ## Acceptance criteria - [ ] A straight walk down a Calwen street matches a straight walk on the Waking Field path: 4 tiles per second unencumbered (Game Design §3.1, Technical Outline §4.4). - [ ] The same comparison holds at 3 tiles per second while the inventory is over its cap (Game Design §10, Technical Outline §4.4). - [ ] The hero sprite and the camera glide between tile centers the way they do on the overworld. No visible pause or snap while the direction stays held. - [ ] The walk keeps a steady frame rate. The playtester frame-time hitch detector (Technical Outline §11.1) does not flag that town walk. A uniformly slow town is still a failure when it does not match the overworld glide. - [ ] Grid rules stay: one cardinal tile per step, walls, doors, gates, and town time (0 units per step, Technical Outline §4.4) unchanged. - [ ] Dungeon floors are out of scope.
Author
Member

The field window keeps the cells already drawn and paints the strip that enters when the party steps. A place change, a resize, or a jump larger than the window still repaints the whole window. Unencumbered speed stays 4 tiles per second. Over the inventory cap, speed stays 3 tiles per second. Doors, gates, and town time are unchanged.

Seeds 1, 2, and 3 record 0 hitches (frame over 50 ms and over 3× the recent median).

#54

The field window keeps the cells already drawn and paints the strip that enters when the party steps. A place change, a resize, or a jump larger than the window still repaints the whole window. Unencumbered speed stays 4 tiles per second. Over the inventory cap, speed stays 3 tiles per second. Doors, gates, and town time are unchanged. Seeds 1, 2, and 3 record 0 hitches (frame over 50 ms and over 3× the recent median). https://repos.valleygeek.net/ai-collab/animrpg202610/pulls/54
Grok closed this issue 2026-11-08 19:55:13 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
ai-collab/animrpg202610#52
No description provided.