NPC's falling through floors in Burning Wood

[strugglegenerator]

Some NPC's in Burning Woods work great until they start to flee. The moment they begin to flee, some NPC's (not all) will fall through the floor, then pop back up on the ground about 10 seconds later. I can see them at this point, but I cannot hit them anymore.

I've seen it happen to Wurms and Giants so far. Doesn't seem to happen to other races yet.

Any ideas what would cause this?

[chrsschb]

I've been having this problem for months. Have tried different map files from various years. Have tried generating new map files. Have mentioned it a few times in Discord.

No solution yet. Temporarily just made all the npcs no-flee.

[Huppy]

I desperately tried to replicate your issue. I went into Burningwood with a non-gm toon and pulled a ton of mobs, (wurms, giants, etc.), over 45 minutes. None of the fleeing mobs ever went into the ground. I tried both RoF2 and Titanium client, using current source and database. I tried ..... lol

[chrsschb]

Originally Posted by Huppy

I desperately tried to replicate your issue. I went into Burningwood with a non-gm toon and pulled a ton of mobs, (wurms, giants, etc.), over 45 minutes. None of the fleeing mobs ever went into the ground. I tried both RoF2 and Titanium client, using current source and database. I tried ..... lol

Yeah. I even rebuilt a lot of the grids just to be safe. Tried static grids and dynamic pathing. Still having the issue lol.

[Huppy]

Originally Posted by chrsschb

Yeah. I even rebuilt a lot of the grids just to be safe. Tried static grids and dynamic pathing. Still having the issue lol.

I'm actually suprised to hear of anyone still having any serious issues with mobs dropping, especially since the Navmesh system came along last year. I really haven't run into much of that in a long time. But all that work done on the mob movement overhaul last december seemed to help out a lot.

[strugglegenerator]

It's really tough to replicate because it doesn't always happen. Even for me, it happens SOMETIMES, but it does happen.

[Huppy]

Originally Posted by strugglegenerator

It's really tough to replicate because it doesn't always happen. Even for me, it happens SOMETIMES, but it does happen.

Ya, but I have a test server here that I play on all the time, and I never see those issues. It used to be a problem a long time ago, but since many updates done to the source code in the last year, I don't see it anymore, in any zones.

[Huppy]

Something that is really unfortunate on these forums, is when a server is having some kind of glitch or issue, not too many of the other servers are willing to chime in and let us know how many are having the same problem, and if not everybody, then figuring out what the difference is. Like now, there is 140+ active servers. But even the PEQTGC, is that server having this problem ? We use the same stuff they have. (database, code, etc).

[chrsschb]

The real kicker is that it only happens in a single zone.

[strugglegenerator]

Yup. Only in Burning Woods.

[Huppy]

Curious, have you guys updated your maps since July ? (burningwoods was added then)

[chrsschb]

Yeah, that map was added because of me reporting this issue.

[strugglegenerator]

I started my server on May 31st, 2019.

[Huppy]

Actually, I got the date wrong, the .nav for burningwood was commited Aug 27
https://github.com/Akkadius/EQEmuMaps

[strugglegenerator]

So that update doesn't happen automatically? I need to manually overwrite the nav folder and the tools folder with the files supplied in the github link and then reboot my server to see if it fixes Burning Woods?

Just trying to understand the workflow here as I've never done that type of update yet.