#path

[KLS]

Nothing says nodes have to all be connected.

Path process takes nodes you already have and tries to connect them automatically. When I created befallen yesterday for example I just ran around doing #path add until I got nodes in every spot possible then with process it will try to connect them. It's not perfect, sometimes it will connect nodes together it shouldn't, and sometimes it fails to connect nodes together that should be (especially in water it fails a lot).

And maps for dump and process output are relative to your zone server, when creating a zone I usually have a hotbutton: #path dump Maps/zonename.path

[Dibalamin]

Got it now. I thought based on the description of process it would attempt to create common nodes based on the map. I didn't realize I had to hammer in a bunch, process it to connect them, then dump it.

Thanks KLS!

[Dibalamin]

Is it better to have as many nodes as logically possible or can you limit it down with no reduction in AI?

I ran into an issue in Crushbone. Mobs are perfectly content to leap off bridges and run straight at PC's instead of proceeding to what I considered well placed nodes....

[KLS]

I found lowering Pathing:MinNodesLeftForLOSCheck and upping Pathing:MinNodesTraversedForLOSCheck helps a lot with that kind of stuff, I'm thinking about tweaking the default rules so it works better over all. Generally if you can get away with fewer nodes it's better, but not even I follow that to a T.

[Dibalamin]

Here is what I did for crushbone

http://www.stormrunner.net/Pathing/crushbone.path

and here is highpass

http://www.stormrunner.net/Pathing/highpass.path


Critique and advise how I can do it better if you would, cause I'm not sure I'm on par yet. I tried to recreate the pathing bug in crushbone too =o.

[cavedude]

Thanks, Dibalamin I added both maps to the maps SVN.

[Dibalamin]

We've coded a bunch more over at p1999 and have them up for testing. If they pass the muster, I'll hand them on over.

This is freaking awesome!