EZ Pathfinding V3 [OUTDATED]

Resources Community Resources
, ,
#21

K, this is nice makes my life 10x easier.

2 Likes
#22

How would I make it so it automatically knows when to jump?

2 Likes
#23

Are you using a part or an npc? I believe npcs jump automatically if the AgentHeight is high enough. With a part, try using RayCasting with the EZRaycaster module to tell how far a part is in front, behind or to the side of the teeming part.

1 Like
#25

Another question is, How do I constantly update the path so it follows a moving player?

#26

I might create a better way and more efficient way of updating a path but using RunService functions + Creating and following new paths could work. I believe there are functions in this module to chase and find the closest player.

1 Like
#27

Does the module require your NPC to have a player script called “Animate”?

2 Likes
#28

NPC’s dont jump automatically, there is a article on PathWaypoint, in which there is a Action property that can tell you which waypoint does the NPC needs to jump

2 Likes
#29

No, it does not. I would add it if you want an animation but it is not required. While moving, it will stay in the regular pose and have no animation.

1 Like
#30

Hello, can you explain more on ChaseNearestPlayer()? Can I get the name of the player or player Instance? Because I only want it to chase a certain team of players

1 Like
#31

I think that’s a typo for chase, right?
You can check for a player’s team color using if statement.

1 Like
#32

Yes it was a typo. So how do I return the player?

1 Like
#33

I am confused about ChaseNearestPlayer() because it doesn’t return anything. If you are talking about GetNearestPlayer() then it returns a character. You can then use Players:GetPlayerFromCharacter(char Obj.) to get the player Instance.

1 Like
#34

May I ask about the default module settings? Jump Power and Walkspeed. Is it 50 and 16 respectively? Also, what is the PFparams?

1 Like
#35

FindNearestTorso function is highly inefficient, I suggest looping through players in PlayerService to find the nearest Torso, or if they are NPCs, put them in a separate folder and loop through the folder.

2 Likes
#36

An extension or rather a new module that I wouldn’t count as a new version is coming out soon! Make sure to look for that.

Details

It can be applied to all newer EZ Pathfinding modules. It can also act as a separate module not connected to EZ Pathfinding modules. It will include all newer pathfinding functions and add more functionality to this module.

2 Likes
#37

From what I know this is the most efficient way of achieving a successful wrapper for the Pathfinding Service.

2 Likes
#38

No offense, but you really need to incorporate OOP. This isn’t very efficient, nor intuitive.

Other then that, interesting concept.

2 Likes
#39

I suggest that a path created by Module.new have its own move method.

3 Likes
#40

How so? I believe this is very efficient if you are not creating many paths at a time. It is also meant mainly for making Roblox pathfinding functions and not for a alternate pathfinding service.

2 Likes
#41

I don’t really understand by what you mean about incorporating a move function in the module.new function? Do you mean having another parameter and if true, moves on the created path right away instead of having to call the move function separately?

1 Like