Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
WarKingz

too far away from navmesh.

Pending 2.1.6

I keep getting problems with the new update 2.1.6 

 

[BotSpawn] A spawn point at 11 in Spawns file WorldScientist is too far away from navmesh.
[BotSpawn] A spawn point at 7 in Spawns file TwinTower is too far away from navmesh.
[BotSpawn] A spawn point at 0 in Spawns file TwinTower is too far away from navmesh.
[BotSpawn] A spawn point at 8 in Spawns file WorldScientist is too far away from navmesh.
[BotSpawn] A spawn point at 9 in Spawns file WorldScientist is too far away from navmesh.
[BotSpawn] A spawn point at 17 in Spawns file TwinTower is too far away from navmesh.
[BotSpawn] A spawn point at 5 in Spawns file TwinTower is too far away from navmesh.
[BotSpawn] A spawn point at 7 in Spawns file WorldScientist is too far away from navmesh.

  • Like 1

Share this comment


Link to comment

Hi,

Are you both coming from a few versions ago? V2.1.1 or something?
There's a note in the main description explaining, but the way custom spawn points are stored has recently changed,
in order to facilitate auto-migrating them if Parent_Monument is in use.

That means people can use custom spawn points + Parent_Monument and only ever have to set up their spawns once,
but it does mean that existing custom spawn points would need to be re-done now.

Share this comment


Link to comment

Then I guess they're just too far from navmesh?

It should warn you if that is the case, when adding custom spawn points.
"No navmesh was found at this location. Consider removing this point or using Stationary : true."

Share this comment


Link to comment

I'll have to get on a test server and check, then, but I have added and tested multiple new profiles over the last few days.

I'd recommend using `/botspawn edit <profilename>` for the problem-profile then `/botspawn removespawn` untill there are no custom spawn points left,
then use `/botspawn addspawn`, watching chat output for any navmesh warnings.

If you get a warning about an added spot, use `/botspawn removespawn` then try again in a different spot.

You should be able to see exactly where the spots are and, hopefully, watch the npcs spawn when you oxide.reload BotSpawn.

Edited by Steenamaroo
  • Like 1

Share this comment


Link to comment

i have to run 2.1.1 for my bots to work there is way to many bots to add them all again as it is the earth apoc map with the new HDR coming soon i dont think the map will be that pop after that so its all ok 

Share this comment


Link to comment

About Us

Codefling is a forward-thinking platform for developers to share and monetize their work from plugins to game assets and everything in-between.

2065 files sold to 246 customers and $26874.99 of payments processed this year!

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.