How would I prevent pathfindingservice from taking the fastest path?

Help and Feedback Scripting Support
#1

Basically, pathfindingservice will try its best to find the FASTEST route, which can end up cutting corners and stuff.

I want to make my own pathfindingservice, which wouldnt generate the fastest route but would walk normally like a player

(I do know I can setup custom waypoints but I’m not sure how to GENERATE paths using those custom waypoints)

Screenshot_2
Screenshot_21090×683 168 KB

4 Likes
#2

I’m pretty sure there are plugins for this to generate your own path. I never did something like this but I hope these will help you!

1 Like
#3

Maybe try skipping some waypoints, kind of like this:

local waypoints = path:GetWaypoints()

for i = 1, #waypoints, 2 do
hum:MoveTo(waypoints[i].Position)
hum.MoveToFinished:Wait()
end

hum:MoveTo(waypoints[#wapoints].Position) -- Just in case it skips the last waypoint
2 Likes
#4

If you want to avoid creating your own paths, which essentially are a table of waypoints(Vectors) from which you would “MoveTo” each one, I suggest planning your builds around a certain hallway width and utilizing the AgentRadius of the :CreatePath(agentParams) argument.

Giving the “agent” a bigger radius means it can’t cut the corners as close because the path computed would make sure the side of the agent would not crash into the wall.

3 Likes
#5

You are a LIFE SAVER, thank you!

1 Like
#6

You will probably need to make your own pathfinding using this.

This seems like a basic 2d Pathfinding. You could drop your nodes as you want, and then connect them together somehow for example by storing those points in a table with the reference to their neighbours as well.

Then you can implement the A* algorithm pretty easily.

Solution by @DreamWakeStudios works as well.

2 Likes
#7

Thanks, since there will be doors implemented in the game and other complicated stuff that a basic path cannot interact with, I will use both of the methods

#8

It is possible to make NPC cross doors using purely A* though, but is a bit more complicated. I would suggest sticking to DreamWakeStudios solution though unless you want to go complex.

1 Like
#9

You can :Connect to the path.Blocked event and trigger a function that gets the blocked waypoint index(automatically passed with the event as the first argument). In that function do your logic checking why it’s blocked. Quick and dirty magnitude check for any doors etc. then open the door or smash it down followed by a new :ComputeAsync to continue on the mission.

1 Like
#10

This only detects if the door was open and then after computing the path it closed. If a door is already closed it will not be able to find any path. In that case custom pathfinding would be more suitable.

Plus there are some known unreliability issues on Path.Blocked event.

2 Likes
#11

Absolutely agree with this and custom implementations can be boundless. Using built-in pathfinding and customary code can work hand in hand, but as you mentioned it would be beneficial having a custom implementation for these types of events.

path.Blocked can be unreliable and I wouldn’t suggest using it as your only check.

2 Likes