nivex
-
Posts
5,879 -
Joined
-
Last visited
-
Days Won
199
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by nivex
-
hi, you can attach files rather than pasting their contents =p it looks like there's an issue where it aborts the scan. change else to else if (user != null) and it should work until I can figure out why it happens to begin with it will look like this if done right: -
it's in the config. it is always there if you don't see it in the profiles search for Blacklisted Commands -
lol sounds good
-
@SynNation you did a great job configuring everything. what is the issue? I don't see anything that would prevent what you requested. but I do see a few other things you may have overlooked. Max Amount Allowed To Automatically Spawn Per Difficulty is not configured so random difficulties will spawn instead Reset Purchased Owner After X Minutes Offline should be set to 20 minutes. 10 minutes is not enough time for most people Blacklisted Commands should have up, down and remove blacklisted or they will exploit if these plugin commands exist. "Blacklisted Commands": [ "remove", "up", "down" ],
-
yea add the config as an attachment and show me it @SynNation
-
maintained events always makes sure that the configured amount of bases are spawned if enough map is available scheduled events only spawns them based on how often you configure it to do so buyable events is how people buy a raid using the /buyraid command.
-
@m3dus4 you can use the old one
- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
ah, ok, sure @The Real Butter
-
A what what?
-
Added PVE and PVP options to block Archery and Wizardry plugins (this will retroactively default to your prior setting)
-
it uses a command from within its UI. block the command global.ui_reviveplayerrestore or ui_reviveplayerrestore and tell me if that works. ya, I can add the Wizardry option
-
2.0.6 released... I left a piece of code in 2.0.5 on accident that prevented it from compiling.
-
2.0.5 released!
-
No, the plugins use their own configured times. I'm not sure why he would want to use both plugins though. Especially if he's using TruePVE. Despawn Timer option controls the time before the base despawns
- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
I'll consider this It appears to work fine. I will upload soon.
- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
yes, that would be how it works. I don't know why I have two options for it anymore, though... just set them to the same duration or set Reset Purchased Owner to 0 so that only Lock Treasure Max Inactive Time applies. I may remove it if I can't remember why it was implemented in the first place because it seems redundant to me.
-
@JimDeadlock 1. Yes 2. Enable Use Permission (raidablebases.buyraid) and use raidablebases.buyraid there are no perms to enter a public raid and it won't be added because players will hate it people will leave the server if they can't raid the bases
-
@Darien elaborate =p that's controlled by CopyPaste plugin.
-
Each live server I'm testing on has it's abandoned time set to 5 days, so it's only been 3 days since then. Everything looks to work fine and I will release it in a few days if I don't run into any issues.
-
Despawn Dropped Loot Bags From Raid Boxes When Base Despawns It seems that this loot option is causing the base despawn issues. Please enable it in your profiles and let me know if the issue with the base not despawning is fixed for you You would need to remove prior existing bases before changing this setting. You can do so by using AdminRadar and typing /radar buildings raid. You can then go to each base and use /rbe kill_cleanup to destroy the base. oxide/data/RaidableBases/Profiles
-
@CsaszyKJauto spawn (maintained/scheduled) is not enabled
-
also, the time only shows from /rb when there are no raids spawned. it has always been this way
-
use rbe debug command in server console to see why your auto spawn doesn't work. type again to toggle it off
-
@iMonkey that would be Rustcord. in the Rustcord language file change ":house: {difficulty} Raidable Base at {position} has ended." to: ":house: {difficulty} Base ({basename}) has been raided by {players} at {position} ({gridposition})." or to this: ":house: {basename} has been raided by {players} at {gridposition}." etc... you will need to use the modified version of 3.3.1 below. Rustcord would need to patch this or it will revert when they update. Rustcord.cs
-
I am still trying to fix the despawn bug and will release an update when I have fixed it. Despawn Dropped Loot Bags From Raid Boxes When Base Despawns anyone with a despawn issue should try to enable this in your profiles, oxide/data/RaidableBases/Profiles/ I have 2 reports now that this fixes it so I will look into this to see why that might be
