Product / Godot 4.x / Early access
A production-grade navigation layer for Godot 4.x: TileMap-driven grids, tactical pathfinding, multi-size agents, dynamic blockers, influence maps, Dijkstra maps, flow fields, and editor-first diagnostics for games where movement is gameplay.
Planned tiers: Lite / Standard from $69 / Pro from $129
The problem
Godot gives developers useful building blocks: AStarGrid2D, NavigationServer, navigation regions, and enough examples to move something around a map. That is a good beginning. It is also, for many tactical and agent-heavy games, only a beginning.
The awkward part arrives when the game stops asking for "a path" and starts asking for decisions: can a 3x3 unit stand here, how far can this enemy move after AP and terrain costs, what route does a crowd take when lanes change, why did this tower placement break the wave, and which tile is reachable without walking through a unit that is allegedly solid.
PathForge Pro is planned as a commercial Godot navigation layer for that stage of a project. It does not try to replace all navigation in all genres. That way lies a framework with a logo, a conference talk, and three haunted abstractions. It focuses on grid and tactical navigation first: the part of game AI where the map is discrete, the rules matter, and "why no path?" should have a better answer than silence.
Features
The first useful release is planned around TileMap and TileMapLayer workflows: generated grids, terrain costs, blocked cells, dynamic blockers, and navigation data that does not have to be maintained in a second secret map.
Tactical RPGs, roguelikes, tower defense games, and simulations need movement ranges, AP costs, reachability maps, terrain penalties, and enemy threat overlays. A shortest path is useful. It is not a design document.
When a route fails, the answer should not be a shrug and an array of coordinates. The product direction includes blocked-cell inspection, clearance visualization, movement-profile checks, and direct explanations for why no path exists.
The default Godot workflow should stay pleasant. The hot path still needs somewhere serious to go: batched queries, local graph updates, query budgets, cache-friendly data, and an optional Rust or C++ GDExtension core when the profiler asks impolitely enough.
AStarGrid2D alternative
AStarGrid2D is a useful Godot API. It is not a bad tool because it has limits. Everything useful has limits; the dishonest tools merely hide them until your release candidate.
PathForge aims at the production gap: TileMap sync, multi-size unit movement, dynamic blocker updates, tactical cost layers, repeatable query performance, and debugging views that make the navigation system observable. The point is not to make pathfinding clever. The point is to make it boring enough to ship.
Production questions
Use cases
Movement ranges, terrain costs, occupied tiles, large units, and readable overlays for players who want to know why the knight cannot stand on the very important square.
Many agents, repeated queries, flow fields, formations, and path pressure where one hero unit politely walking around a wall is not representative research.
Large maps, many agents, changing buildings, blocked-route diagnostics, and path cache reuse for simulations that produce their own charming emergencies.
Dynamic blocking, route validation, enemy lanes, and editor checks before a player discovers that one tower placement has converted the level into modern sculpture.
Grid movement, changing maps, weighted terrain, reachability, enemy movement choices, and debugging tools for procedural levels that are very proud of their edge cases.
Pricing
Final packaging may move as the V1 scope hardens. The current direction is a free Lite tier for evaluation, a Standard tier for commercial grid tooling, and a Pro tier for native acceleration or advanced tactical systems where included.
Planned public entry tier
Free
Planned paid tier
$69+
Planned studio tier
$129+
Roadmap
V1 scope is currently centered on PathForge Grid Pro: TileMap-driven grid generation, reliable grid pathfinding, terrain costs, dynamic blockers, multi-size agents, clearance maps, editor overlays, and a query model that can grow into tactical systems without pretending every game is the same game.
Flow fields, influence maps, formation movement, deterministic helpers, and deeper RTS-scale behavior are planned as Pro-facing work. They belong in the product direction, but they should earn their place with real demos and profiler captures, not a feature table that has never met a production map.
FAQ
For production grid navigation, that is the intention. AStarGrid2D is useful for prototypes and small systems. PathForge is being designed for projects that need multi-size agents, diagnostics, tactical overlays, and repeated path queries without turning every edge case into custom glue code.
No. A* is one useful algorithm inside the product direction. PathForge is planned as a navigation workflow: TileMap-derived grids, terrain costs, dynamic blockers, movement ranges, clearance maps, tactical AI maps, diagnostics, and performance scheduling where the project needs it.
The target is Godot 4.x, with the first production scope aimed at modern Godot 4 releases. The current planning target is Godot 4.5+, because supporting old engine behavior forever is how tools become museums with buttons.
Lite is planned as a free entry tier for small projects and evaluation. Standard is planned for commercial grid pathfinding with multi-size agents and clearance maps. Pro is planned for advanced tactical systems such as flow fields, influence maps, Dijkstra maps, and deeper diagnostics.
That is the plan for the paid tiers. The final license text will be published before paid release, because surprising customers with license details is a hobby best left to cursed installers.
Yes, multi-size agent pathfinding is one of the main reasons PathForge exists. Clearance maps and editor visualization are planned as first-class features rather than something taped to the side after the first large unit gets stuck in a doorway.
Not in the first Grid-focused release. Volumetric navigation for flying, swimming, drone, and zero-gravity agents is a long-term product direction, not a V1 promise. The first release is being kept narrow enough to ship and support properly.
Not yet. The V1 scope is being defined, and the early access list is open for indie developers and small studios who want launch notice, pricing updates, and a chance to influence the first production shape.
Early access
Join the early access list for launch notice, pricing updates, and the occasional practical question about what your pathfinding system is currently doing to your frame budget.
