SimplePath - Pathfinding Module

SimplePath is an open-source pathfinding module that gives you the ability to quickly create a pathfinding script for humanoids and non-humanoids with just a few lines of code. Pathfinding is done using Roblox’s PathfindingService.

This module works by using a “repetitive” approach to pathfinding. The pathfinding agent moves a more efficient path when computed repetitively instead of just once. Part of the reason why is because computing the path once doesn’t guarantee that the agent reaches the goal as expected. Taking the repetitive approach accounts for any obstructions or obstacles blocking the path at the current time. This guarantees that the agent will reach its goal no matter what as long as it’s traversable within the scope of PathfindingService. Although you can still use SimplePath normally, it is strongly suggested that you take a repetitive approach to pathfinding as this was the primary concept kept in mind during the development of this module. However, in some scenarios, it might be better to compute the path just once. For example, if the agent does not interact with moving objects, you should consider changing the structure of your pathfinding code by reducing the number of repetitions between path computations to improve performance.

To get started with using SimplePath visit: Getting Started - SimplePath.



nice pathfinding lol
this is cool


Update 1.01:

  • Fixed a velocity jump issue.
  • Added three new static methods (see API).

Nice module! You can create something like this with it lol


Update 1.02:

  • Fixed issues when rigs had HipHeight of 0.
  • Enabled the usage of Path:Stop() for non-humanoids. See API for more info.

I love the system. But for how I use it, when I stand on top of a part, the NPC is clueless on how to get to me.

1 Like

i don’t think npc can jump or jump good

1 Like

He jumps when he wants, I was on top of a truss and he didn’t know what to do.

1 Like

The NPC cannot always reach you. It can only walk to your location if there is a clear pathway available for the NPC. Sometimes in rare cases, the path may not be generated even though it’s possible for the NPC to reach the goal. Unfortunately, this is one of the limitations associated with pathfinding service and in this case, there’s nothing I can do.


Im not sure if im doing something wrong but this character is jumping randomly Screen capture - eeacd47c9ad32603a6ac47713906a9e1 - Gyazo i used path:run() and nothing else also i have no clue why the gyazo is so laggy

1 Like

It still gives me an error that the hip height is zero. And i am moving a model.

1 Like

When there is something blocking the path or if there is some kind of an interference, it gets detected by when the humanoid does not reach the next waypoint within the set amount of time. After the timeout, the RetryPath method is executed which assumes that there’s something blocking the path so this is why the humanoid jumps and due to the way the script works, the humanoid more or lese doesn’t move while in the air so there’s a velocity applied to it. I’m aware that .Velocity is depreciated and I plan to update the module soon.

1 Like

It doesn’t support truss climbing
(it just stops at bottom)

Also some others bugs Screen capture - 5758cf7fae185b557314c66c6c75ff54 - Gyazo

1 Like

This uses the Roblox pathfinding system (as any other pathfinding module does). If the Roblox pathfinding system doesn’t support climbing (I doubt it does) then it would require a whole rework of the module to make that possible, if there are any other stable pathfinding methods out there.

1 Like

I suggest creating a state property so we can check it with an if statement. While I was making my own NPC with your system, I found it would be helpful to check the status and change it to what I want if it isn’t already. Example:
if path.Status == "Running" then path:Stop() end
or the opposite

1 Like

That’s a very good idea. I will make sure to implement it in the upcoming update. Thank you for the suggestion.

I built a controller like this awhile ago for a friend, but I noticed that when doing obstacle courses that the pathfinder wasn’t finding paths / creating jump links, avoiding dangerous objects, respecting timed events, or able to provide advanced maneuvering like walking sideways. Sometimes it couldn’t even jump on pillars because it would return waypoints in the opposite direction before a jump.

These issues are impossible to fix in a controller like this, so I’m working on a new pathfinder. I’ll likely build on and submit PR for this controller and use that.

If anyone is interested in contributing to the list of do’s and don’ts for the new pathfinder, I’m building a community to discuss those issues. Here is a discord invite:


How do I make it so the npc’s animations will activate when walking.

1 Like

You can download the provided example which includes a dummy with animations.

Edit: If using the example above, make sure to use the latest version of SimplePath.

I’m running into behavior with this module. Here’s how I run it.

         if ClosestObject then
			local Combat_NpcStates = CharacterModel:WaitForChild("Combat_NpcStates")
			--[Trigger States]
			local TriggerStates = Combat_NpcStates:WaitForChild("TriggerStates")
			local Aggro = TriggerStates:WaitForChild("Aggro")
			local RandomX = Universal_Checks.TrueRandom(-ClosestObject.Size.X/2, ClosestObject.Size.X/2)
			local RandomZ = Universal_Checks.TrueRandom(-ClosestObject.Size.Z/2, ClosestObject.Size.Z/2)
			local PathfindPosition = (ClosestObject.CFrame *, 0, RandomZ)).Position
			local CalculatedPath =, {AgentHeight = 5, AgentRadius = 3, AgentCanJump = true,})
			Connections["PathCompleteConnect"] = CalculatedPath.Completed:connect(function(Status)
				--check distance of all players to aggro
			Connections["AggroChangeConnect"] = Aggro:GetPropertyChangedSignal("Value"):connect(function()
				if Aggro.Value ~= nil then

Here’s what happens. This causes a HUGE lag spike. Do you notice anything wrong in my code that could cause this?

EDIT: Turns out I was using the old version of the module. I believe the issue is fixed!