Awesome! This should make it much easier to set up climbing AI in my newer maps.
14 Likes
Pretty cool 
I will make sure that Pathfinding now supports Climbable Trusses 
7 Likes
Finally, another long waited feature is here. Those improvements will definitely make the engine look much better.
6 Likes
Been waiting for this for too long, very glad to see it’s here!
5 Likes
This will make it so we don’t have to create our own Climbing Functions. YAY!!! 
4 Likes
I would like a parameter for AgentCanDrop. Currently the only way to allow an agent to drop off a navmesh onto a lower navmesh is to set AgentCanJump to true. But this means the path will also allow jumping up onto a higher navmesh. Sometimes there are cases where your agent should not jump but should be allowed to drop down.
36 Likes
This is an awesome change 
! My only gripe is that TrussPart still has sizing constraints. Perhaps a Climbable property could be added to BasePart or Part?
42 Likes
Awesome. It will work with climb-able parts that are not trusses too (parts placed over each other with a little gap between them)?
6 Likes
Great work! Finally some new cool updates to pathfinding!
3 Likes
I tested it and for now it doesn’t work unfortunately, let’s hope it does in future updates
2 Likes
Gonna also ping @SomeFedoraGuy
A good workaround until Roblox fixes this (assuming they will) might be to use invisible TrussParts via BasePart.Transparency = 1.
9 Likes
I am honestly happy with this addition, now I can make them get out of a hole! I wonder if one day you are guys would add a way to pass an IgnoreList/WhiteList to pathfinding.
These are some features I consider are missing or complex to find solutions from a Roblox dev at the current moment (Will not be requesting them right now, just wanted it to through it out here):
(If anyone knows how to execute any of the points below, please give me the solution of it, that is performant and not something crazy like cloning the whole world or setting a collision group to all the parts like some people speculate)
-
I want Pathfinding to ignore everything except terrain (because I want to make my object just move around there) and sometimes I want an object to ignore certain blocks when doing the path as well. I can’t do that now as far as I know. Using Pathfinding Modifiers will not be good for this since I will not be inserting thousands of them when this task must be done.
-
Ability to ignore completely a material so my object never goes through water/lava as well. I don’t want him to be swimming or walking through certain areas that are considered hazardous in the game.
-
Ability to make so if a part that is hazardous will be touching him, he shouldn’t walk to it.
-
Add another kind of path that you give it a goal, the path will be computed but if it cannot reach the goal it will give you all the waypoints to the nearest one to the goal.
5 Likes
THE ONE PIECE IS REAL!
im honestly really happy with this new addition to pathfinding, this is going to make many NPCS and other pathfinding in other games more advanced and more easy to use! No more manual climbing scripts!
3 Likes
Should this have been a future since the service was released? Yes. Am I hyped that it’s here? Yes. I’m excited to see future pathfinding updates to make it better. Good job!
2 Likes
Superb addition! Particularly like that we can set the cost of the climbing action
2 Likes
Very convenient timing, right as I’m making monster AI for my horror game.
3 Likes
-
I don’t think you can ignore everything except terrain unless you set the cost of every single BasePart material to
math.huge(Material | Roblox Creator Documentation) or pathfinding modifiers (which you said you didn’t want to use but if you use a script you could automate it) -
You should be able to use pathfinding costs to ignore a material or specified hazardous parts. (PathfindingService | Roblox Creator Documentation)
--example, would ignore water no matter what
Costs = {
Water = math.huge
}
- Not sure exactly what you mean but this but it’s impossible to detect if a script makes a part hazardous unless you have some sort of variable (like a BoolValue or boolean attribute) or pathfinding modifier.
- I’m pretty sure pathfinding already tries to find any path and if it can’t reach it then there isn’t a possible way to the goal. You might have to re-compute it.
3 Likes
This should’ve been released way way way way way earlier.
3 Likes
You know how Raycasting accepts an IgnoreList and a WhiteList? Well, I would love something like that for this, so when I tell my NPC to walk to somewhere he ignores a bunch of objects.
Doesn’t cost means that he will ignore that material if there are other ways? I believe that if you are on an island, and the only thing that there is around you is water and I tell it to walk to another island it will literally swim to it. If I am wrong, please correct me.
This is kinda like the first point, but it could be a list you pass to CreatePath named Hazardous which the pathfinding will avoid.
That’s the issue, it returns a path with no success; however, I would love a way for me to tell the pathfinder to return some waypoints that I can use to walk near the goal.
For example:
NPC: 
Objstacle: 
(A huge wall that makes the path impossible)
Goal: 
Path: →
→ → → → → → → → →
Since there is an obstacle and you cannot reach the goal, I would love that Pathfinding returns to me all the waypoints before reaching the obstacle. I haven’t checked if it does this when the path has no success, but yeah. It’s mainly useful when you want an object to follow a player from their PrimaryPart’s position which pathfinding thinks it’s blocked because of something in the way.
4 Likes
They probably won’t add it since there’s pathfinding modifiers and costs sadly. It would definitely make it easier.
If you set it to math.huge then it won’t at all, even when it can’t find another path that doesn’t.
Yeah that would be helpful.
I guess the only workaround right now is to just use MoveTo to the goal when it can’t find a path (and you could use Raycasting to see if it’s actually blocked)
3 Likes