nivex
-
Posts
5,566 -
Joined
-
Last visited
-
Days Won
193
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
NextTick(PurgeTemporaryRespawns); remove this code from the .cs, and update your server with the latest steam and oxide updates there's nothing else that I can see that would cause this. i believe it to be the facepunch update to pooling that they reverted afterwards.
-
ok i will check it out now
-
Changed Status from Pending to Closed
-
2.7.0 released you do not have to wait to update enjoy! -
oh I'm not doubting that you saw walls, but you're certain there was a raid base there beforehand? I mean I know the walls were definitely there, but sometimes annoying questions need to be asked to be sure. just like a tech that asks you, "is it plugged in?" "did you turn it on?" "is the issue between the keyboard and chair?"
-
@Hawkhill walls: when a raid ends the entities despawn in the order of walls, blocks and then deployables last. they're all in the same list, so if the walls don't despawn then the base won't either. this means that the kill messages were sent to those walls, because your base despawned afterwards. its unknown why this happened. any number of things can break it such as bad server performance, other plugins blocking the kill, the server canceling the invokes, oxide throwing errors, etc. i would need more information. i suspect its an oxide issue as i have seen IOCore exceptions being thrown from OnEntityKill which can't happen unless oxide is bugged or another plugin is bugging out oxide. this was from one other report. other than that i've heard nothing else about this, and that one was bases not walls. @Aussie4life floaters: bases won't float unless you've modified a autoheight or height setting, or if the base was not copied properly to begin with. many other packages did not copy the bases properly. my packages were all copied at 1.5 meters so they will paste as intended
-
@byond1991 lmao ya thatll do it
-
Changed Status from Pending to Closed
-
hi, no problem
-
@TheRiddledNote sorry I meant to say disable Do Not Destroy Manually Converted Base When Despawn Timer Expires to prevent base despawning for /sar convert bases -
@Aussie4lifeset the radius back to 25-45. you're trying to spawn it on top of the base and thats not gonna work
-
ya they can use /sar convert they need abandonedbases.convert perm to use the command you need to set Despawn Timer to 0 if you dont want the base to despawn afterwards they can use /sar cancel to cancel the raid there is a cooldown before they can cancel, and you can require the raid be completed before canceling too. it requires abandonedbases.convert.cancel you need to configure everything. @TheRiddledNote
- 610 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
@aussie4life its either disabled, theres an error, or you have a plugin deleting them i tested with 65.0 and it spawns fine, though it should not have a radius higher than the protection radius - 5, or 45.0
-
oxide/data/RaidableBases/Default_Loot.json you don't need to add it. it's already there. just replace the text in the file with [] and reload the plugin
-
edit the default loot table and replace it with []
-
Changed Status from Pending to Closed
-
np, update is done but the forced Rust update will break the plugin so I will wait until then to release for any last minute changes of theirs that could break my new fixes.
-
hi, example 1 is the correct way. example 2 would add everything in to each profile which is really bad. np!
-
I don't recommend it otherwise players will be able to jump over at times when terrain is uneven, but yea you can change it. Ignore Stack Limit When Clipping Terrain - false Use Least Amount Of Walls - true oxide/data/RaidableBases/Profiles/
-
@Dr.D.Bug yes that is also fixed. I posted about this some time back and included instructions for the fix in my post too if you want to use the fix now. the rust update is going to break the plugin so I will wait to release until then, or perhaps the night before as I sometimes do. @TwoShoes if you want to change all positions by default then you can set them in the config set your own positions in game, unload the plugin, open oxide/data/RaidableBasesUI.json and copy the settings from your own offsets that you just created into the config into the relevant UI for each. save and reload plugin. then everyone will start with your defaults, but they will still be able to move it to where they want it afterwards. @byond1991 use the stability paste option in each of the profiles, oxide/data/RaidableBases/Profiles/ if you do not have stability option then add it as seen below to each base that you want to change stability on. i will add command rb.config stability true and rb.config stability false in next update so you can do this for all profiles with ease "raideasy1": [ { "Option": "stability", "Value": "true" }, { "Option": "autoheight", "Value": "false" }, { "Option": "height", "Value": "1.0" } ],
-
use Maintained Events or Scheduled Events in the config change Minimum Required Players Online to what you want
-
@Dr.D.Bug the radius is fixed by changing if (size is Vector3) to if (size is Vector3 && !size.Equals(Vector3.zero)
