nivex
-
Posts
5,405 -
Joined
-
Last visited
-
Days Won
187
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
yes, the base will get deleted on a scan.
-
ah ok. it must have a minimum of 2 foundations. setting it to 1 will not work.
-
twig does not qualify
-
I didn't say that floating skins wasn't from RB or CopyPaste. I said it can happen solely from CopyPaste too. if you cannot interact with the door skins then it is not an issue. kills are sent to every entity so if you have some deployables like that furnace that aren't killed then something is blocking that kill. also that furnace should not be spawning half way under the ground. that base was not copied properly, or the height was modified you can send me a base with an issue and I can look at it.
-
@Stark no, those are the default settings so that only appears to new players. all other players are stored in the oxide/data/RaidableBasesUI.json file. so you'd click the arrow and move it yourself. if you want to change the default then you unload the plugin, copy it from the RaidableBasesUI file into the config and delete the RaidableBasesUI file. it's intended that players move it where they want it though -
heya, no idea what causes the floating skins but they are harmless. this happens solely with the CopyPaste plugin too so there's no telling what causes it. it's client-side only and reconnecting fixes it. no idea why you have a furnace half way into the ground. I doubt that is RB
-
Changed Status from Pending to Closed
-
no problem. ill continue to look into it too but i've been trying for a while now and since 2.7.8 you're the only report so it's very odd that it still happens. makes me think it's another plugin but just don't know
-
Changed Status from Pending to Closed
-
hi, that's from Oxide. they'll aware and will update it at some point
-
so my suggestion is to use Timed Execute and unload the Raidable Bases plugin 5 minutes before your server restarts this way the bases despawn before the restart since they cannot despawn during a restart. something is causing it to not despawn after the restart so this will fix that. I don't know what's causing that. I dont have the issues since 2.7.8. so I still suspect another plugin causing it.
-
well I don't think it's Raid Protection plugin you do need to update that though
-
there's no errors in the logs so thats good. looks like it is another plugin blocking the despawn after the server restarts I don't have the Raid Protection plugin on any of my servers so I can't check it
-
also, those do not look like bases that failed to despawn after being raided. they look like bases that failed to despawn after a server restart
-
hi, attach your server log
-
@Cascadian AC sounds like the difficulty setting got defaulted in the profiles, oxide/data/RaidableBases/Profiles "Difficulty (0 = easy, 1 = medium, 2 = hard, 3 = expert, 4 = nightmare)": 0, just change it back. not sure why that happens since I don't change it.
-
no problem
-
nah, it doesn't think the base is in an event. that message means that the base can't be in an event because it has no TC. another plugin would have to be blocking the decay because it isn't possible for it to be Abandoned Bases. TruePVE ignores decay, but it is possible for another plugin to hook TruePVE and block the damage. though that's completely unnecessary since TruePVE won't override another plugin since it doesn't handle decay damage to begin with. so a plugin could simply hook OnEntityTakeDamage instead and block the decay that way.
-
I'm changing Cancel Automated Events If Abandoned Owner Comes Online in next update so that it works when players convert bases by attacking them. since if the base converts it would technically be automated since it's not done with the /sar command
-
Abandoned Bases and TruePVE do not control any decay damage
-
"Do Not Destroy Base When Despawn Timer Expires": false, "Do Not Destroy Manually Converted Base When Despawn Timer Expires": false, hi, set this true
-
Changed Status from Pending to Closed
-
rip wish the updater would not do that np
-
if they all spawn as easy then the profiles are not correct. something has reset them. either, 1. oxide or newtonsoft bug changed the difficulty setting - no idea why this happens. I never modify it. 2. auto update plugin installed free version, followed by premium being installed again if #1 then just open the profiles and change the difficulty setting to what it should be. they are all set to 0 as this is the only way they can spawn as Easy. if #2 then you have to reinstall the package or a backup
-
thanks guys! adding the files is case sensitive, too and you can verify with rb.config list it will only show File does not exist next to files that don't exist. everything that exists will be shown separately.
