-
Posts
5,151 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
Changed Status from Pending to Closed Changed Fixed In to Next Version
-
no problem enjoy!
-
line 2755 if (!brain.CanLeave(brain.AttackPosition) || !brain.CanShoot()) replace with if (!brain.CanShoot()) Allow Npcs To Leave Dome When Attacking is bugged and wasn't letting them attack because they can't leave the dome. stationary npc works fine because they can't leave anyway you don't need to remove your previous edit if you don't want to. it's fine as is. it didn't compile because I gave you code from the next version I'm working on by accident lol
-
ok, trying to figure it out
-
the profile and config are missing so I can't check them again
-
hi, edit the .cs file it's quite easy. I gave you the line number to start at the first block of the code is what needs replaced with the second block of code if you edit this directly on the server then oxide will reload the plugin when you save it
-
I don't remember who asked about npcs walking through high walls but I've fixed that in the next update just keep in mind that npcs can spawn outside of the walls which is intended. if you increase Arena Walls Radius to 40 or 45 and your Protection Radius is 50 then they will initially spawn within the arena walls
-
ya it's bugged I've fixed it in the next update line 2972 in .cs if (player.IsKilled() || AttackTarget == player) { return false; } should be this if (player.IsKilled()) { return false; } if (AttackTarget == player) { return true; }
-
np. ok, will take a look for you
-
your player mentioned the TC wasn't looted and the raid ended. it's not required unless Require Cupboard To Be Looted Before Despawning is enabled so I think there's a miscommunication here either way, the server still needs restarted regularly. tell me what the memory goes down to after a server restart
-
hi, post the profile for this and your config
-
modded servers should be restarted daily. otherwise issues like this can happen, or worse. the machine doesn't need to be restarted daily. just the rust server
-
very odd. yes it appears that the server had a hiccup and prematurely ended the raid. this means that CanUndo returned true when it shouldn't have. this just can't happen under normal server conditions i've seen this happen on rare occasion over the years. I'd like to try and fix it, but I think I'm chasing a rabbit down a hole how many plugins are you using? what is your entity count? how often do you restart? do you have an item leak? an item leak can increase memory usage, cause performance issues, in turn causing the server to behave oddly are you using a shared or dedicated server? do you have plugins that remove loot from containers that might contribute towards this problem? do you know if the user saw the event "Destroying raid base at in X minutes" message?
-
hi, attach the oxide/log/RaidableBases/despawn file attach the config too also, which base was this, in what grid and owned by which player?
-
Changed Status from Pending to Closed
-
hi, there is an option for this in the next update
-
@Delltus hi, zone pvx info is for pvp zones from zone manager - not pvp delay. it's also not maintained, hasn't been updated in 1 year and one of the hooks is out of date raid bases has its own pvp delay ui "Delay UI": { "Enabled": true, "Offset Min": "-34.488 87.056", "Offset Max": "179.631 124.804", "Font Size": 14, "Panel Alpha": 0.98, "Text Color": "#FF0000", "Background Color": "#252121", "Title Background Color": "#000000" },
-
Changed Status from Pending to Closed
-
no problem
-
hi, this isn't possible abandonedbases.attack.time grants the time until abandoned and last seen time admins do not require abandonedbases.attack.time i will add a separate permission in next update