Objective Waypoint System

[YetiTech Studios]

Does this require navmesh? I use custom path finder(3D voxel style with A*).

Yes it requires NavMesh, by default A* is not supported but it is possible if you want to change it.

[rasamaya1]

Does this require navmesh? I use custom path finder(3D voxel style with A*).

[YetiTech Studios]

Changelog v1.5
* Fixed waypoints spawning together when getting closer to target.
* Removed bobbing timeline animation from Blueprints. This is now a shader effect. (Thanks Imagine-Games)

[MyNameIsPonz]

Please update this to Version 4.22 - I've purchased the asset and can't use it :/

[PotatoFaceGames]

Hey please update your system to not use ThirdPersonCharacter, its a bit annoying having to refactor it

[YetiTech Studios]

How hard would it be to add an auto run feature to this system? Similar to Black Desert Online. Player clicks on map or on objective and that starts the path which is then followed by the player's character following that path?

It shouldn't be hard, one way of doing it, click on the map or an objective, swap your player controller with an AI controller and drive that AI controller to that specific location (AI Move To node).

[EmpireLion]

How hard would it be to add an auto run feature to this system? Similar to Black Desert Online. Player clicks on map or on objective and that starts the path which is then followed by the player's character following that path?

[YetiTech Studios]

Not entirely true, because "Internal_PathFinding_SpawnMode" cast the pawn to ThirdPersonCharacter.

We have casted to ThirdPersonCharacter because that was just an example project. We are planning to make another update to replace those cast nodes with Event Dispatchers.

[monsieurgustav]

There is no need to copy over functions or parameters to your new character blueprint

Not entirely true, because "Internal_PathFinding_SpawnMode" cast the pawn to ThirdPersonCharacter.

[YetiTech Studios]

Do you have any tips on implementing this on a custom character? If I already have a character set up, is there a quick way to copy over all the functions and needed parameters into my new character blueprint? As far as I can tell, I'm going to have to reset up a ton of the functions in my new character and wasn't sure if there was a simple way I was missing.

There is no need to copy over functions or parameters to your new character blueprint, you simply add/remove the Objective Waypoint System component to your custom character. Inside your character blueprint assign your target actor to a function called FindPathToActor in Objective Waypoint System Component. If your target is not an actor but a location use FindPathToLocation in the Objective Waypoint System component. The marketplace package comes with a full example project, please feel free to check it out.

[DMHokie]

Do you have any tips on implementing this on a custom character? If I already have a character set up, is there a quick way to copy over all the functions and needed parameters into my new character blueprint? As far as I can tell, I'm going to have to reset up a ton of the functions in my new character and wasn't sure if there was a simple way I was missing.

[YetiTech Studios]

Any tutorials available on how to use it?

Apologies for the late reply, we have not been notified about this post since the new forum update. The Objective Waypoint System comes with an example project which shows you how to implement the system. Make sure you have one NavMesh in your level.

heya Yeti,

Any tips for getting this up and running in VR?

As long as you have one NavMesh in your level and provided a goal actor in your system it should work.

[MrKiser]

Any tutorials available on how to use it?

[Morphus1]

heya Yeti,

Any tips for getting this up and running in VR?

[YetiTech Studios]

Thanks Yeti, doesn't the way-point component require being attached to a character?

Objective Waypoint System is a Component so you have to add it to an Actor based class. Since its a non-scene component you cannot attach to other scene components (like StaticMeshComponent, SkeletalMeshComponent etc.)