Uploaded May 2025 | Updated November 2026, 3 hours ago
Let's take a quick look at how I parse, store, and use map data in my tactical roguelite so that units know where and how they can move and attack.
Some related Q&A:
- Why is the navigation an autoload?
It's a holdover from early prototyping days of getting to a functional prototype as fast as possible as it makes it easy for other nodes to access it, but it's not exactly the most elegant way to connect units to the navigation system.
- So what's the alternative?
I'd probably generate a navigation instance per-battle and pass a reference to the objects that need it. That would help keep concerns where they belong for just a little extra overhead, but for this game the autoload works just fine.
- If units don't pathfind, how do they know where to move to?
Movement is defined the same as any other action - as an array of tiles to pass through with a block mode to truncate a path if it is blocked by something in its way. There's no difference in implementation between a move action and attack action, just a difference in the paths they take for resolution. The video on how units work has a bit more detail on this.
- How does the navigation system know where other units and objects are?
Relevant nodes within the battle scene register callables on initialization so that it can get the latest info on the world as needed.
Text version: shaggydev.com/2025/05/19/udd-navigation
How units work: youtu.be/dE6oFnyILKY
Check out Unto Deepest Depths! store.steampowered.com/app/3106600/?utm_source=yt
00:00 What is a level?
01:36 Generating navigation data
03:11 Pathfinding
03:50 Working with unit actions
Let's take a quick look at how I parse, store, and use map data in my tactical roguelite so that units know where and how they can move and attack.
Some related Q&A:
- Why is the navigation an autoload?
It's a holdover from early prototyping days of getting to a functional prototype as fast as possible as it makes it easy for other nodes to access it, but it's not exactly the most elegant way to connect units to the navigation system.
- So what's the alternative?
I'd probably generate a navigation instance per-battle and pass a reference to the objects that need it. That would help keep concerns where they belong for just a little extra overhead, but for this game the autoload works just fine.
- If units don't pathfind, how do they know where to move to?
Movement is defined the same as any other action - as an array of tiles to pass through with a block mode to truncate a path if it is blocked by something in its way. There's no difference in implementation between a move action and attack action, just a difference in the paths they take for resolution. The video on how units work has a bit more detail on this.
- How does the navigation system know where other units and objects are?
Relevant nodes within the battle scene register callables on initialization so that it can get the latest info on the world as needed.
Text version: shaggydev.com/2025/05/19/udd-navigation
How units work: youtu.be/dE6oFnyILKY
Check out Unto Deepest Depths! store.steampowered.com/app/3106600/?utm_source=yt
00:00 What is a level?
01:36 Generating navigation data
03:11 Pathfinding
03:50 Working with unit actions










