Steenamaroo

I could add a spawn offset value for default profiles but, to be honest, it would take as much time/effort for users to set that up as it would to just create a new profile exactly where you want it then parent it to the monument in question. It's about as automatic as it gets, auto-updating the custom profile location every time you change map. There's no license permitting user modifications and no support can be offered to anyone who decides they don't care.

My previous post describes how to achieve this. Are you commenting with two accounts or is this two people?

Hi, It's not possible to move the central point of default profiles but you can turn the profile off then create a custom profile at the exact locations you'd prefer, then set that custom profile's "Parent_Monument" field to the name of the default profile you just disabled. For example, you could use the chat commands to create "DomeCustom" somewhere near the Dome, then set DomeCustom's parent monument to "The Dome 0". That way the central point for the profile is exactly where you want it but if you change map seed BotSpawn will automatically relocate the profile to keep it in the same spot, relative to the new Dome location.

Hi, Thanks for letting me know. Would you mind checking if this fixes it? BotSpawn.cs

Hi, According to Wulf we should use true/null as return objects in OnSomeAction hooks.

Hi, Most likely they're getting run over. It's something I've been meaning to look at.

Edit the user config, not the plugin. Font size, alignment, and position are all user customisable.

Hi, There is in the next update. I'll push it later today.

Changed Status from Pending to Closed

The solution, then, is to make the profile radius bigger or use the BotSpawn chat commands to create custom spawnpoints - The latter allows you to place them on, or in, the actual monument where people won't be building.

If you're happy for them not to spawn simply turn off the lighthouse profiles - "AutoSpawn" : false,

Hi, The best way to suppress the log spam is either to ensure that BotSpawn will find spawnpoints at the lighthouse, either by using custom spawn points or increasing the radius, or ask for fewer, or no, npcs. The lighthouse and the Dome in particular require a larger radius for finding random spawn points as randomly chosen points must be on open terrain with a clear view up to the sky. Setting a small radius for these profiles makes that impossible as the monument itself is in the way.

It's no problem. I'll add a global config option for Staggered_Despawn in the next update. Thanks.

It doesn't matter much to me whether they despawn gradually or all at once. I just thought gradual would have been preferred by most so that a large chunk of population doesn't suddenly vanish to any players who happen to be in the area. I'll add a global option for instant despawn in the next update.

Hi, There's a check for population/time of day every 10 seconds and npcs are killed off one at a time. That means if you have 5 npcs for day and 1 for night and night time is 20 hours, it might be 20:40 before you reach population of 1. The reason for this is just so multiple npcs don't suddenly vanish all at once.

Changed Status from Pending to Closed

Have fun.

Hi, You have to damage something. Fire at a barrel or building block or something.

Changed Status from Pending to Work in Progress

Private copy sent for testing. Will be in next release.

Hey man, Sure, I can do those ^. Grab UpdatesChecker and a beer.

Pleasure.

Hi, I'm not aware of any big issues right now. Maybe peacekeeper is enabled? That would make them ignore players holding no weapon or melee weapons, and immune to melee damage.