Pathing Still some pathing issues after patch

[baalzy]

Heres an example to reproduce a pet going through a wall.

In Droga at the Chief camp guard your pet.

Send your pet on a mob in the side area (where the Goblin Stitcher spawns), he'll path down the hallway correctly but if you /back him he runs straight through the wall back to where he was set to guard instead of pathing correctly.

[Man0warr]

Yeah, most of the time I've had my pet fall thru ground in Seb/HS was when I had him set on guard - they seem to ignore path nodes while in that stance.

[Kostou]

# 1 )When pulling mobs from BR they will path entire zone instead of following you.


# 2 ) Shaman pet took indirect path in gukbottom instead of attacking froggies. Came back with a huge train.


Sorry for the brevity, but many ppl are reporting these same issues to me. Hope this helps.

[Haynar]

Originally Posted by Man0warr [You must be logged in to view images. Log in or Register.]

Yeah, most of the time I've had my pet fall thru ground in Seb/HS was when I had him set on guard - they seem to ignore path nodes while in that stance.

Found it. And you are totally correct. They did not use pathing at all when returning to their guard position. This piece of code has not changed in forever.

Fixed, pending update.

Using the pet guard option, means you are going to be trained when they come back, til this fix goes in.

H

[Man0warr]

I've stopped using pets since the trains but they aren't the only problem - please keep researching why mobs (particularly casters) are ignoring pathing and going through walls (and falling through ground while trying).

Just last night pulling the brain room behind Disco I was able to get the Iksar Necromancer to fall through the world and presumably start up a train, thankfully we had a wizard in group so I called an evac before it got to us. When I got back to Seb a group said they ended up killing the Necromancer at NG camp after he had walked up from Crypt.

[Haynar]

Might be an issue with movement code that when they start casting, while moving, it doesnt mark the moving as stopped. So when spell is finished, they register where it projected it would have been in that direction. I think I know what to look for. Bet its related to casting code. So its probably not my fault =p.

[Haynar]

Yep. There are issues with the persuit spell casting code. I dont see anything that updates movement changes. I didnt write this, so figuring it out so i can see what needs fixed.

H

[Haynar]

I see a few things wrong when a mob stops to cast.

I can fix that. Hopefully I am getting some of the train makers ironed out.

Because of the way the node pathing system was broke where it basically recalculated routes repeatedly, it masked these issues. Thats what is the source of this issue. Now that pathing is working, the fact that they dont actually stop to cast is a problem.

Also if you aggro a mob while its in middle of casting a buff on a mob, it should wait til casting is finished before going after you. Instead it does this warping thing. So was actually a few probs in mobs spell casting ai code.

H

[Man0warr]

Glad you found the issues - this makes zones with multiple levels very dangerous so hopefully it can get patched quickly.

[Haynar]

Expect a big stress test on beta this weekend. We have made tons of changes towards optimizing code. But testing is needed.

Rogean will get it organized.

H