nivex
-
Posts
5,889 -
Joined
-
Last visited
-
Days Won
199
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by nivex
-
yea a cooldown is planned- 634 comments
-
- 2
-
-
- #rust
- #rust plugin
- (and 6 more)
-
I'll think about the silent option but on the fence about it I really dislike redundant options that further bloat the files There has to be a better way to implement it -
commands are added in next update
-
@m3dus4 hi, no, teleport is not optional. I will add this option and abandonedbases.teleport to bypass the option in the next update for you there's no option for server-wide pvp - you should unload the plugin and TruePVE during purge if you want this.
-
@SynNation sorry yes it is indeed 3/5/7 by default. you definitely should go over each config option though
- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
@Swedish Chef yes, per your request =p
-
@Swedish Chef yea it will only work for that specific type of door I added your request in next update which you will need to enable Added `Force All Doors To Have Same Skin` (false)
-
heya. I do believe you can use Preset Door Skins option for this.
-
@VSM the mechanic is in my Raidable Bases plugin. so I'm aware of how useful it is, and would like to implement it. but those aren't opinions, and won't be implemented until there is an elegant solution to those issues. it must not impact server performance, and it must be written efficiently with the least amount of code. something i'm not so great at doing, though I do have a very clear understanding of what works and what doesn't work. either way, it will not be viable until then. @SynNation yes, change the settings in the config. that time determines how long a player/team can be inactive before the base is considered abandoned.
- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
as always, I am open to suggestions. I have taken suggestions and implemented them for the past 7 years. I build my plugins for the community given what you guys request them to do. so I have no problems considering an idea from all angles to see if its viable, or if its poorly thought out. the worst I can say is no.
-
yes you can change them I understand, and I've considered this but it is not a viable option. players often build far too close to others, and the dome can overlap their base when another base becomes abandoned. even though their base cannot be raided it still posses a few other problems 1. players do not build too close on every server - but it applies to the majority and this cannot be ignored 2. I would need to prevent the player from being kicked from his own home so that the raid can continue in the base that is abandoned 3. dynamic radius would need to be forced for this option to work which means I would have to remove dynamic radius as an option and force it to always be used instead. even then, it is not a guarantee if the abandoned base is a compound or built using elongated shapes. 4. even if I did manage to find a solution to the above then players could exploit this by freely harassing others anyway since that player would not be ejected from his own home. this would be minimal, but it cannot be ignored either ejecting enemies is not viable given the above. the only solution is to prevent enemies from looting containers or bags that drop from containers. this too presents its own issues 1. I can't prevent people from picking up individual items that are dropped on the ground. rust does not provide persistent information to make this viable. anytime an item is stacked onto another item the unique identifier will change. i'm not going to hook everything required as a workaround because it would be too costly on server performance 2. server owners will ask why the player is not ejected instead, and I will constantly have to repeat myself and hope they understand. if they're not happy then they'll have no choice but to accept it for what it is. 3. players can still annoy other players even if they can't loot by running around them or standing in areas so they can't get through them ultimately, this is something that should be enforced by the server owner regardless of how annoying it is. it's not a perfect plugin, and it is impossible for it to be. I will continue to improve it, but some things just cannot be handled in a way that everyone will agree with. the best way to handle this issue is to make these events PVP only and then the raiders can kill anyone trying to counter raid them.
-
ya that's fine
-
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
