SimplePath - Pathfinding Module

[Neuroticxs (Ace)]

Yes, I was able to get it working, Although minor code changes are needed on the simple path module
I have changed InvokeWaypointReached function to this so I can retrieve Last, Current, Next Waypoints.

I believe the original one only sends the Last and Current waypoints, not the next waypoint. I noticed this since I was trying to check if the current waypoint label was == “Door” and it doesn’t return anything, But the next waypoint does. Although I haven’t fully understood if SimplePath does traverse every single waypoint or skips the Current Waypoint if it’s the last waypoint and goes to the target Position instead.

So, doing this way works. Let me know if you found a better solution. So far this works wonders.

Lastly, Listen for path.WaypointReached:Connect(function(lastWaypoint, currentWaypoint, nextWaypoint) and check it’s waypoint Label
eg: nextWaypoint.Label == "Door" then do the rest.

Hope it helps!

Edit:
One thing to note is to use Agent Parameters when using pathfinding links make sure its weight is 0.001 on Agent Parmaters if its the highest priority to traverse. Never go 0. As you can see my Link is DoorwayEnter.

local AgentParams = {
	AgentRadius = 1.2,
	AgentHeight = 0.6,
	AgentCanJump = false,
	AgentCanClimb = false,
	WaypointSpacing = 2.5,

	Costs = {
		DoorwayEnter = 0.001,
		Walkable = 0.1,
	}
}

When you Enable Show Navigation Mesh in Studio Settings to see the waypoints you will notice the waypoints will stop from the Start of the Pathfinding Link and the last waypoint will be the end of the Pathfinding Link and won’t continue to generate waypoints to the target. I haven’t figured this out yet. But believe this is caused by the module. Work around is just call Path:Run() again when every single waypointReached event.

[Lord_BradyRocks]

Sweet thanks for the information!

Then when you are listening for next way point = door, do you then kick off the code to open the door?

which then allows the npc to go through it? (

or do you sill have it so the npc does not collide with the doors, and the door opening is just a visual effect?)

[Neuroticxs (Ace)]

Yes, Since you need to listen to Path.WaypointReached event and call path:Run(target) to continue the waypoints, Instead I call a function to open the door and make the NPC move forward a bit when Waypoint Label is “Door” and do animation, After the animation I call Path:Run(target) again to continue

[ihatespiders61 (ihatespiders)]

how can i use simplepath to follow the nearest player?

[Duck_sac]

Use this to check repeatedly for the nearest player:

local function FindNearestPlayer()
	while wait(0.5) do
		local found
		local last = math.huge
		for _,plyr in pairs(game.Players:GetPlayers()) do
			local distance = plyr:DistanceFromCharacter(script.Parent.HumanoidRootPart.Position)
			if distance < last then
				found = plyr
				last = distance
			end
		end

		Goal = found.Character.HumanoidRootPart
		return Goal
	end

end

[JaceMorphing (xZen)]

Why does this happen when I try to use SimplePath with a custom r15 rig?
(I use Path:Run())

[Hapun]

I’ve since found the solution to the replied issue. For everyone who utilizes this module, please refer to this post, it may save you a headache in the future:

@Hapun

After a lot of tinkering, I’ve narrowed down the issue to one little line of code and thought I’d share it for future gents:

path:ComputeAsync(character.PrimaryPart.Position, destination)

I edited it to:

path:ComputeAsync(character.PrimaryPart.Position - Vector3.new(0, character.PrimaryPart.Size.Y/0.75, 0), destination)

[Gonistical (Devious Intentions)]

very good, but how can i do this with something like bodyposition as a example?

[ihatespiders61 (ihatespiders)]

That’s not simplepath’s problem, it’s the rig. Most likely the arms are causing this.

[JaceMorphing (xZen)]

It was issue with my script, the model was supposed to have attributes for speeds, like RunSpeed and WalkSpeed, but I forgot to add them so speed was always 0, I’m just really dumb.

[CryptoArtz (BlackSmith)]

I got inspired by this module, and i used it on my first AI chaser for some testings.
and now ill tryna implement my own pathfinding module using this service, thx for sharing us your creation!

[amadeupworld2]

SimplePath module: Trouble with cancelling a path

Here’s a link to the pathfinding module I’m using. Whenever Lighting.ClockTime changes, I go through all NPCs and call a module NPC_Pathfinding for _, npc in pairs(CollectionService:GetTagged(activeZone.Name.."_1")) do if targetDestination then npc:SetAttribute("target", targetDestination) local path = NPC_Pathfinding.new(npc, targetDestination) path:walk() end end Finally, in this module, I call the SimplePath module. function path:walk() self.Dummy.AttributeC…

Please help ):

[trainmaster_65 (CheesyWorth)]

no matter where it’s at it will keep jumping, is that normal?

[KristinaMoment (Kristina)]

It doesn’t work

The broken code in concern:

[VSCPlays]

I don’t get the issue, I’m unable to reproduce it (used it in my worst game and didn’t experience the issue)

[colvyr (nana)]

incredibly useful work thank you

[Maxwell_Studios (Maxwell)]

whenever i put my pathfinding chase code onto bigger npc’s they start to turn sharply when i move alot, depends on how big the npc is
any help?

code:

vid:

[fouroul94 (Nurfed)]

Delete the while loop, just use the same script as the doc exmaplet

[LaxThyBoltious (genericrobloxian)]

im having a bit of trouble with this.
when using this module on characters that are extremely large (nearly 230 studs tall), the module just doesnt work.
humanoid:moveto() works, but when i try to use path:run() the character just doesnt move.

[deathcharge415 (Ne3u1imity)]

Have you made sure that it actually works on normal characters too?