nivex
-
Posts
5,916 -
Joined
-
Last visited
-
Days Won
199
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by nivex
-
players only need abandonedbases.basic if you want to see that info you need to grant yourself abandonedbases.attack and abandonedbases.attack.time permissions as I said earlier =p then go attack a building that isn't yours or your ally (team, clan, friend) to see it @FreeManStars- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
yes, the data file is erased each wipe, Sphere Amount to 0 disables the dome, and deleted means it did not meet the minimum foundation and wall requirements it's your decision what permission you give to default group. abandonedbases.basic is 3 days. that works for the majority of servers but everyone has their own preference. I recommend at least 3 days. skipped means the TC was not found, the building has no entities which decay such as building blocks, or it was too close to another event so it will retry again later. np. lots of improvements in the next update too. @FreeManStars
- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
heya, no problem @FreeManStars if you set the despawn to 0 then it can't despawn. so it will keep converting until no TC is left anymore, then it will decay on its own. I don't convert bases that have no TC. you can set the number of conversions, or increase the timer instead and I recommend a higher despawn timer instead attack a base with abandonedbases.attack and abandonedbases.attack.time permission and it will tell you the time. if you did not install the plugin soon enough then it will not be accurate for any players that were online prior to the plugin being installed. the plugin won't know the last time someone was on if it was not installed when they were last online. so it will never convert their base. you should install it with a wipe so this doesn't happen. yes midnight to noon and noon to midnight
- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
@FreeManStars abandonedbases.basic permission is 3 days then it becomes raidable - give a player this permission or another from the config file - higher lifetime takes priority - so if a player has basic and vip perms then vip takes priority by default it will not automatically convert any bases unless you configure - Run Once On Server Startup - Run Every X Seconds (do not set less than 3600) - you can run a scan manually with sab command once Despawn Timer expires the base will be deleted/despawned. you can set Despawn Timer to 0 to disable this, but then the base won't be deleted. if someone destroys the TC then the base won't be converted a second time. it will simply decay and no one will be able to raid it again once the plugin is reloaded/server restarts.
- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
yup, in the next update hope to have it released soon -
youll probably like this too then
-
@Hawkhill yes
-
@Hawkhill issues with this are fixed in the next update you can find a fix in a previous reply if you want to fix it now
-
yea for some reason I hid the error in the last update. it'll show again next update. you can see it with rbe debug though
-
@Raiven_007 nice, you must've fixed it
-
@Aussie4life you would need to use rbe debug command when this happens. sounds like a bad copypaste file @Raiven_007 if you try to use the command before the plugin loads then it will say that. if you are using it afterwards and it says that then that then the base is not configured or the copypaste file doesn't exist. you can use the rb.config list command to see what files don't exist, and what you do have configured instead thank you @Gold Mysteriousand @mark bergervoet
-
@KayKay nah, it's a game bug. i've reported it to Facepunch and gave them the fix but it hasn't been applied yet. the bug makes no difference on a vanilla server since all damage is allowed there so there's no priority for them to fix it. the bug is that the initiator of the fire is not set to the player. no initiator means the damage is ignored by RaidableBases. if it doesn't know where the damage came from then it's impossible for it to allow or block it so it gets ignored. if it gets ignored then TruePVE handles it, and it will block the damage because it doesn't kn ow either. if it allowed the damage then players could raid and kill everyone on the server with fire, and rules/flags wouldn't do anything. I wrote a harmony fix for it (inside of a Carbon/Oxide plugin), but honestly players should just use fire that works. ServerProjectileHitFix.cs
-
@Lapegsonita hi, it's a server convar. so you would use the command in the server console I'm not sure if you need to save it in the serverauto.cfg too
-
@Lapegsonita Interference was added in the Rust update. that command is a convar to control it for the server. you can use that, or read this thread https://codefling.com/files/sc/9913-base-turrets-question/?tab=comments
-
this is because an npc is using a crossbow which doesn't work for npcs. I figured out a hack for this, and it works for hunting bows too so those will be enabled as well. npcs will be able to use crossbows, compound bows and hunting bows in the next update
-
@Gold Mysterious ya, but having both options is ideal for server owners who want to enforce it on players but not on raid bases
-
I will disable it on raid bases when a hook exists for it
-
@Dr.D.Bug heya, it is just /rb for that. /rb info didn't exist until 2.7.4 and is just debug for me
-
@MaLai hi, no, sorry there is not a way to do this. the buyable cooldowns are for buying the raid only, and the hogging check is for public raids only I can make a hog option for that though
-
@imkat98 I get the rare report regarding this but haven't been given any errors I can look into it again but I can't fix this without an error or at least being able to reproduce it. I think the RaidableBasesUID datafile is being reset and there's nothing I can do about that if so. I never reset it unless it's null/corrupted
-
@PistOffBastd I can add an option for no event timer, sure np there will be a new option along with that option, Seconds Until Despawn After Looting, and if you want to set that to 1 second then you can despawn it this way
- 634 comments
-
- 2
-
-
- #rust
- #rust plugin
- (and 6 more)
-
@Samuel Pumpe yes, it's per profile no, it won't ignore that amount entirely. it must have an amount to start with or it will not work at all. it just will not force that amount to spawn. it'll roll on the probability once and spawn from that only. so if you don't have enough loot in the base then that's why, and players won't be happy with this
-
@HowlingWolf hi, you can use the rb.config add command to add bases easily rb.config add "Easy Bases" easy1 easy2 easy3 etc. it is case sensitive so type the names exactly or it will overwrite it @Samuel Pumpe hi, I will add this probability option for you, but I don't think it's a good idea. some players will be very upset with this and likely leave the server over it. it will be Do Not Force Items With Lower Probability To Spawn you can use the text field for this, add it to the note { "shortname": "note", "name": null, "amount": 1, "skin": 0, "amountMin": 1, "probability": 1.0, "stacksize": -1, "text": "This is my note" },
-
@Samuel Pumpe@nashslash hi probability range is 0.0 to 1.0 so you wouldn't want to set it above 1.0 0.0033 is valid but that is so very very rare if you do not have enough available loot to spawn from your loot tables then it will pick regardless of the probability. solution? add more items with higher probability. difficulty loot tables should have 180+ items in them. base loot tables should have a few items that you always want to spawn, with Always Spawn Base Loot Table enabled in the profile.
-
@Gamebundle if you set it true then yes
