nivex
-
Posts
5,906 -
Joined
-
Last visited
-
Days Won
199
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by nivex
-
if your host is using Linux then they have to install libgdiplus. if these bases were copied recently with copypaste then you need to update copypaste to 4.1.37+ and/or re-save them no one has reported any bases spawning like this. it has always been that they spawn with everything but do not despawn when they're supposed to because of a bug you can enable Despawn Dropped Loot Bags From Raid Boxes When Base Despawns in each of the profiles to see if this fixes the issue if the above doesn't apply to you, oxide/data/RaidableBases/Profiles/ it's been reported from a few users that this fixes the issue with the base not despawning properly. it will destroy the gray loot bags that drop from the boxes in the base so players must loot them before the raid despawns. it will not destroy any loot belonging to a player. this is the only workaround atm -
hi,yes, by the default the times are: abandonedbases.basic - 5 days abandonedbases.veteran - 5 days abandonedbases.vip - 7 days players must be granted a permission in order for it to apply. if you grant abandonedbases.basic to the default group then you can still give abandonedbases.vip to your vip group -
hi, no, this is not possible.
-
yes, its in the config: Difficulty Colors (Border) Difficulty Colors (Inner)
-
hi, 2.7.2 is current and was not updated on Saturday. sometimes the website will display the wrong date and I've found it unusual but I've never mentioned that bug to @Deathfor some reason. either way you will see 2.7.3 when it is updated
-
you can message me from the codefling discord
-
hi, have you saved any bases with copypaste since the last rust update? you will need to update copypaste if you haven't already 4.1.37 and recopy all those bases again. failing that remove all newly copied bases from your profiles if you haven't copied any new bases then use the rbe debug command in the server console when this happens. type it again to toggle it off.
-
so you used my fix and it works? yes, you should change that line too.
-
I don't understand what you're saying =p
-
I think I figured it out in the .cs file go to line 2794 and make a new line by pressing enter key. put this code on line 2794: if (priv.IsKilled() || building == null || building.decayEntities == null) { _skipped++; yield break; } it will look like this when done:
-
this happens because something is null in code or the datafile. I'm trying to figure out what that might be
-
ok I found the error but not home atm
-
that is not helpful you must DM me the server log ask your host -logfile log.txt this is all they need to add
-
your rust folder. c:\rustserver\log.txt may be named latest.log, server.log, etc do not post it here - DM it to me if you don't see the logfile then ask your host how to find or enable it
-
I need the trace message for that error. if you do not see it then it is in the server log (not oxide log)
-
yes
-
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?
