Geralldo.RuLey

Apologies for the misnaming; it should be NPCSpawn instead of BotSpawn. I have both NPCSpawn and BotReSpawn installed. However, in this instance, the issue stemmed from the HarborEvent. I suspect the problem arose because I reverted to the default configuration and removed the previously customized one. The previous configuration was spawning NPCs at coordinates 0.0.0 (underground), along with other entities that the plugin may utilize for certain functionalities. Additionally, the old edited position settings were causing NPCs to spawn floating.

It Still throwing infinite Navmesh errors flooding the server console. installed Latest BotSpawn + HarborEvent. (with the default config). unloading HarborEvent resolved the issue, with no further spam in the server console for the past two hours

Thank you

I got this error message from yesterday and continuously spamming the console. no changes has been made [03.31 04:32:32] Failed to call hook 'OnPlayerSleepEnded' on plugin 'EpicLoot v1.1.15' (FormatException: Input string was not in a correct format.) at System.Number.ThrowOverflowOrFormatException (System.Boolean overflow, System.String overflowResourceKey) [0x0001a] in <4889cca7f3644a7fa341501beb4caacb>:0 at System.Number.ParseSingle (System.ReadOnlySpan`1[T] value, System.Globalization.NumberStyles styles, System.Globalization.NumberFormatInfo info) [0x00071] in <4889cca7f3644a7fa341501beb4caacb>:0 at System.Single.Parse (System.String s, System.IFormatProvider provider) [0x0001b] in <4889cca7f3644a7fa341501beb4caacb>:0 at System.Convert.ToSingle (System.String value) [0x0000f] in <4889cca7f3644a7fa341501beb4caacb>:0 at Oxide.Plugins.EpicLoot.SetupDefaultPlayerUI (BasePlayer player) [0x0007f] in <809a41e637974ff38350dcfc093380e8>:0 at Oxide.Plugins.EpicLoot.SendInspectMenuButton (BasePlayer player) [0x00051] in <809a41e637974ff38350dcfc093380e8>:0 at Oxide.Plugins.EpicLoot.OnPlayerSleepEnded (BasePlayer player) [0x00056] in <809a41e637974ff38350dcfc093380e8>:0 at Oxide.Plugins.EpicLoot.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x02bd6] in <809a41e637974ff38350dcfc093380e8>:0 at Oxide.Plugins.CSharpPlugin.InvokeMethod (Oxide.Core.Plugins.HookMethod method, System.Object[] args) [0x00079] in <87ce9ac9776a48658bc55eae6debe38b>:0 at Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String name, System.Object[] args) [0x000d8] in <b6d06fce9e044af4a6ddc8d724bd3b0b>:0 at Oxide.Core.Plugins.Plugin.CallHook (System.String hook, System.Object[] args) [0x00060] in <b6d06fce9e044af4a6ddc8d724bd3b0b>:0

I know it is complicated but Could you also add an option specifying which entities can be utilized by teams or clans and limit clan placements? I've limited the planter box placement and more for VIPs. However, some individuals are exploiting this system by employing their Smurf accounts to join clans, place planters, and then leave, the clan member limit is 3. Despite the limit, they're still able to place as many planters as they desire and utilize them, as the planters are solely protected by the TC range, along with both the planter defender and prevent looting plugin.

it's giving me a console error for the latest FP patch EggHunt. item definition.

can you add permission system?

Can you also allow us to modify the background elements by the config?

I got the same problem.

Would you add ignore turret damage for individual profiles too? I created many custom profiles and bosses that bosses should not be AFK killed by players with their turrets while hiding in the base. but I do allow them to build a defense for the default profile bots.

use NPCHealth from Umod.

Hello. I bought this plugin from Chaos. can you please add to destroy or block usage if the player lost permissions? for example, I use this for my VIP and when it expires the planters and bag will not be usable for them.

They are default player but thanks for pointing out the raidablebases.allow permissions, I thought it was meant for them to allow raiding. I will update the result. Thank you.

ill post it on support. Thank you.

the lockout or prevention system seems to be broken too. a clan of 2 can call multiple bases (both are nightmares) and raid separately, it happened after the latest update.