The Path Tool

I'm exploring uses for the new Path Tool in Hammer. It's what the new ent_path_platform entity uses. I feel like its underused and somewhat under developed in base Source 2, but with a bit of work we can turn that around.

With the Path Tool there is no need to set unique entity names for each node to link them together, so creating and modifying a path is a lot simpler.

The path is then compiled into a single entity that you can name and assign to a different entity like the new ent_path_platform.
attribute 'style' not allowed

attribute 'style' not allowed

The path tool data is already accessible to coders via the BasePath class.attribute 'style' not allowed

attribute 'style' not allowed

In the near future I want each node to have custom key-values and outputs just like we can already do with entities themselves for even higher customizability.attribute 'style' not allowed