nivex
-
Posts
5,502 -
Joined
-
Last visited
-
Days Won
191
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
I think you should disable those options in PreventLooting config. UseCupboard to false UseOnlyInCupboardRange to false if someone leaves their TC unlocked then players will be able to loot their entire base =/- 606 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
prevent looting is bugged, too. if there are no players authed then everyone can loot. it is not checking bprev.AnyAuthed() && bprev.IsAuthed(player) so it will always return true when no one is authed. so yes, destroying the TC will prevent him from looting anymore. clearing auth will not. this is very bad for normal game play when a player forgets to lock their TC
- 606 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
@FreeManStars they cannot claim without abandonedbases.convert.claim permission oh, yes, that is why. prevent looting can allow looting with cupboard auth. this is not a bug though. if he gets auth he should be able to loot it.
- 606 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
if you use /sar claim then you can loot everything if the raid ends from the timer expiring, or from /sar cancel, then you cannot loot unless you or an ally owned it to start with edit: you must check with ent who in your f1 game console. the only way he can loot is if he is the owner, his ally is the owner, or there is no owner (ent who showing 0). otherwise prevent looting plugin will block him
- 606 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
I did answer you. if it has a steamid as owner then it cannot be looted unless he is ally with that steamid. prevent looting will block it. how did the raid end? /sar claim, or /sar cancel?
- 606 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
config is good, but max dynamic radius might need increase if the dome is too small. you should not disable the sphere until this radius is configured properly for your server you have not showed me the ent who for this box. prevent looting is responsible to block this looting. when the event is over the plugin has no control of the base anymore.
- 606 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
when the event is over it will not block the looting anymore. you must use a plugin like Prevent Looting for that
-
@FreeManStars use ent who on this box they are looting.
-
@FreeManStars no, the bug is when you loot it ejects you. post your config when it's ready. if I keep finding bugs then it won't be ready until I fix that bug too
-
@FreeManStars I think the new changes from 2.0.8 have broken this option yes, setting it to false will use sphere radius. dynamic is configured by default to work for smaller bases. if it's too close then increase Min Custom Sphere Radius to 50, or increase Padding Added Onto Dynamic Radius to 25 Cooldown Between Events will eject you, and there is a bug when looting that is fixed next update
- 606 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
Changed Status from Pending to Closed
-
heya ok, thanks
-
@Kobani set Amount of entities to paste per batch. Use to tweak performance impact of pasting to 5 or less in CopyPaste config, maybe 1 for testing Amount Of Entities To Spawn Per Batch is 1 by default in the Raidable Bases profile already -
@Gumby yes, too many turrets with interference will cause massive lag for quite some time. I can't patch it until the oxide hooks are added you can use this plugin for now, which works for non-player entities such as those from raid bases. you can enable it for player turrets if you edit the config. this is far better than using convars to "remove" limits too. https://cdn.discordapp.com/attachments/839691032085135380/1161559259755061279/NoInterference.cs
-
yes, revoke raidablebases.allow permission from players. that is for admins/mods/staff only raidablebases.despawn.buyraid will let players despawn their own purchased bases but nothing else.
-
@weaksauce heya. I'm just waiting on an Oxide update for this to add the hook that I've requested:) you can use this for the time being. by default it works for turrets not owned by a player (so raid bases). if you want it to apply to all turrets then you can edit the config. NoInterference.cs -
@FreeManStars no. you should assign that permission to a group instead of granting the permission to individual players. o.grant group vip abandonedbases.immune then to see who has the perm you can use this command: o.show group vip give them group using: o.usergroup add 76561198250830000 vip remove them from group using: o.usergroup remove 76561198250830000 vip you cannot remove the permission from them unless you remove them from the group using that command. so use a group that will work best for this.
- 606 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
@FreeManStars that permission will persist for as long as they have it. it gives immunity to the entire base they are associated with. there are no Oxide commands to remove all perms. you have to remove it from individual players or groups you've assigned the permission to
- 606 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
heya, you won't need to install libgdiplus on a windows machine. that library is for linux I am not sure why this happens. it has been an issue for months, but unfortunately I can't fix it until I can reproduce it myself. no errors have been provided so it makes it extremely difficult to figure out I did make several changes in the next update that I am hoping fix it so we'll see you can remove those bases by going to them and using /rbe kill_cleanup
-
@FreeManStars you can add as many of them as you need, yes I am not sure if you can cross over into another day like that. you might have to do 22:00 to 23:59:59 and 00:00 to 04:00 since it is working off of the servers current date time. yes, it will reappear with that
- 606 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
np. I don't get alerts for edits. abandonedbases.notices is when players are notified that a base has become abandoned (An abandoned player's base is now raidable at {0}) it doesn't matter if they leave. the plugin will use its currently configured options. the time zone the server's operating system is using. times for players update when they connect, when they wake up, when they go to sleep (such as logging off) and when reloading the plugin. if he's online then it's not going to tell you that his base is converting in 23 hours unless he has exclude permission or you're looking at a different player. I will look into the looting issue. being ejected is the same cause. vanish/noclip/canbypass perm will bypass this - those other perms will not. canceling the event ends it completely. I don't know what happens after that, your plugins determine that. the event is over. it's not going to do anything after you've canceled it. times work based on 24 hours. 0-23. grey loot bags that fall from containers despawn after 1 hour at most unless you are continuously opening them. either way, once the event is over it no longer has any control over that base. your other plugins do, like prevent looting plugin. @FreeManStars
- 606 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
just fixed issues where bases would stop respawning, or no longer be available, after some time which required the plugin to be reloaded lots of reasons this can happen so I won't bother explaining them all. namely profiles which don't work on the map you're currently using, and busted forced height settings can cause it too.
-
@Aussie4life you can zip everything and DM it to me. rb config, rb data folder, copypaste data folder and copypaste config
-
@Nikedemoscare to elaborate? edit: nevermind, this can only happen if the player is not inside the bubble and tries to deploy the box into the bubble. so there might be a bug where the plugin isn't detecting him inside, but if he was outside and deployed inside then it will always kill it and that goes for any entity, and is intended
-
@Aussie4life sounds like a bad base then your pocket dimensions comment is too vague
