Jump to content

1 Screenshot

  • 182.5k
  • 5.4k
  • 143.13 kB

This area is for discussion and questions. Please use the support area for reporting issues or getting help.

Recommended Comments



nivex

Posted

@miniMe_rust

hi, np, I've included the guid at the end of each hook call in the next update

Guid guid

example

private void OnAbandonedBaseStart(Vector3 center, float radius, bool AllowPVP, List<BasePlayer> intruders, List<ulong> intruderIds, List<BaseEntity> entities, bool CanDropBackpack, bool AutomatedEvent, bool AttackEvent, Guid guid)
            {
                // attack event means someone started the event by attacking the base with the abandonedbases.attack permission. this will only convert a base when it has become abandoned
            }

 

  • Love 1
miniMe_rust

Posted

On 1/12/2026 at 8:35 PM, nivex said:

@miniMe_rust

hi, np, I've included the guid at the end of each hook call in the next update

Guid guid

example

private void OnAbandonedBaseStart(Vector3 center, float radius, bool AllowPVP, List<BasePlayer> intruders, List<ulong> intruderIds, List<BaseEntity> entities, bool CanDropBackpack, bool AutomatedEvent, bool AttackEvent, Guid guid)
            {
                // attack event means someone started the event by attacking the base with the abandonedbases.attack permission. this will only convert a base when it has become abandoned
            }

 

You're the best!

  • Love 1
StrongWolves

Posted

@nivex

 

Hello,
I’m constantly having an issue with a plugin – or possibly with the interaction between this plugin and RealPVE.

When players raid a base that is already raid-allowed (for example an abandoned base), any locked storage containers that get destroyed turn into a small grey box. This box cannot be opened by anyone, even though the base should be fully raid-able.

I’m not sure if this behavior is caused by a setting in the plugin, or if it’s a conflict with RealPVE (ownership / protection not being removed correctly).

Is this controlled by some configuration option, or is it a known incompatibility with RealPVE?

nivex

Posted (edited)

@StrongWolves

hi, that's an issue with RealPVE and I added the requested fix in 2.2.6 so it shouldn't be an issue

Edited by nivex
StrongWolves

Posted

On 1/19/2026 at 5:33 PM, nivex said:

@StrongWolves

hi, that's an issue with RealPVE and I added the requested fix in 2.2.6 so it shouldn't be an issue

So the fix has been released, I updated the plugin, but the problem still persists. If a player raids an abandoned base and destroys a chest that has a lock on it, it turns into a grey stash and cannot be looted. How can I fix this? Is it somewhere in the config?

nivex

Posted (edited)

@StrongWolveshi, he needs to fix it. I've already added the requested hook.

Edited by nivex
Soller

Posted

Hi. The players complained to me again that they were being killed when they were standing AFC. Apparently, some players put a cupboard tool next to it and launch a raid. I have a PVE server, and the option is enabled for manually launched raids to be PVP. I don't want to completely remove these PVP moments from the server. I had a thought, is it impossible to make sure that after launching the raid, no one except those authorized in the closet is allowed into the raid area for the first 5 seconds? So that the player near whom the raid was launched would simply be thrown out of the raid territory.

nivex

Posted

@Soller

hi, do the limits not work? I've added the limits when you requested it. I understand that hurts legitimate players too. so an alternate solution would be helpful.

"Loot Required (SAR)"
"Foundations Required (SAR)"
"Walls Required (SAR)"

ejecting is good thinking, but it will still be exploitable. such as predicting where the player would be ejected, or the player returning and walking into the event accidentally just to die anyway

I have a solution, block /sar when another player is in the event radius and not authed on the TC. just a modified version of your idea. optional, and enabled by default.

 

  • Like 1
nivex

Posted (edited)

added in the next update

  • Added sar option, `Distance to block the command when used near players that are not authed` (50 meters) - vanish, invis and noclip users are excluded!
  • "AuthorizeOther": "You are not allowed to use this command near unauthorized players.",
  • you can of course change that message or remove it entirely by setting it to "AuthorizeOther": "",

still working on player-made boat support in multiple plugins of mine so it will be released when that is completed:)

Edited by nivex
  • Like 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Like 11
  • Love 11

User Feedback

2.2m

Downloads

Total number of downloads.

10.4k

Customers

Total customers served.

150.4k

Files Sold

Total number of files sold.

3.2m

Payments Processed

Total payments processed.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.