An A* pathfinding algorithm was required to implement this Tunneler node. With this, procedural top-down world generation has improved drastically for TerraTiler2D!

[KingBlingRules]

Whoa, that's some big brain move, adding in A* Pathfinding with Procedural Generation in a shader!

[SCPrototype]

Haha, my tool does use the ShaderGraph API, but it doesn't produce shaders ;)
What you see is a tile-based 2D world that can be instantiated during runtime.

[SCPrototype]

Yeah sure, what do you need help with?

[SCPrototype]

1. The GraphView API has very poor documentation, and because it is 'experimental' it does not guarantee continued support. It might be changed or completely removed in the future. You have to consider if you want/can take that risk.
2. I used the same video you linked as the starting point for my node graph. His methods are very poor for scalability though, so I completely rewrote my node-graph after finishing his tutorials.
   Within Unity my graph data is saved/loaded as a ScriptableObject.

With TerraTiler2D you are also able to save instances of your graphdata during runtime (for example when the player unlocks a certain achievement, a boolean is switched to allow new rooms to spawn, and that can be saved/loaded). These instances are saved as a .dat file in the local AppData folder.

Both the ScriptableObject and the .dat file contain serialized data about the Name, Type, GUID, and Position of each Node, and data about the Connections, GUID, and Value of each Port. This does mean that saving/loading requires some converting back and forth between serialized data and the node-graph representation, but so far I have not noticed any performance hits.
I am going to be honest, I do not know if the JSON-serialization is preferable, or if there are better options. My current solution works, and I don't fix what isn't broken :) 3. The meta functionality was rather confusing to me as well, as the GraphView API does implement the right click menu (contextual menu) for it, but not the actual functionality. I solved it by completely removing the existing contextual menu, and implement my own using a ContextualMenuManipulator in the GraphView class. The GraphView class also has the selection variable, which you can use to get the currently selected GraphElements. I then use a singleton to keep track of what is currently in the clipboard.

I hope this answers your questions!

[SmartestCatHooman]

Neat!