Abandoned Bases 2.1.8

2.0.7 released - Requires Rust update

tugboats, locking the raid and ejecting enemies has been added. I had a lot of fun implementing these and hopefully you don't run into too many issues with them

keep in mind that the eject setting does not work when you enter the dome/event. it works when you enter the base, loot or try to damage something.

enjoy!

Hey Nivex,

What counts as raid ended? Have it set so players can't hog the raids, but it just stays with base ticking down on standard despawn timer

@dylanstar12

heya, they must loot everything

if you want TC required only then enable Only Cupboards Are Required To Cancel An Event

this will allow them to destroy or fully loot the TC to complete the event too

Is there a way to disable 2nd and 3rd message when someone shoots a base?

1. This building is not eligible.........
2. XYX (1234567890) was last seen x hours..........
3. This building will become abandoned in x hours...........

I hope you understood what I am trying to explain.

Thank you.

@KayKay

hi, revoke abandonedbases.attack.time

it will prevent #3 in next update 2.0.8 too

49 minutes ago, nivex said:

@KayKay

hi, revoke abandonedbases.attack.time

it will prevent #3 in next update 2.0.8 too

I have 3 situations after the 2.0.8 update, and restarted the server after.
- disabled all perms, except abandonedbases.attack.time -> No Message.
- disabled all perms, except abandonedbases.attack -> Two Messages (1. This building is not eligible.........2. XYX (1234567890) was last seen x hours..........)
- disabled all perms, except abandonedbases.attack and abandonedbases.attack.time - > Three messages (1. This building is not eligible.........2. XYX       (1234567890) was last seen x hours..........3. This building will become abandoned in x hours...........)

I am unable to find the combination where only message No. 1 would pop up.

Thank you for your prompt response, I own multiple plugins of yours, and appreciate your insta reply.

#1 requires abandonedbases.attack

#2 players require abandonedbases.attack and abandonedbases.attack.time, admin requires only abandonedbases.attack. admin does not require abandonedbases.attack.time permission and will see the messages always.

#3 same as #2

@KayKay

Hello!

After the recent update, all people now are able to raid other peoples bases (bases are taking damage).

Is there anything that change?

2 hours ago, Nuno Correia said:

Hello!

After the recent update, all people now are able to raid other peoples bases (bases are taking damage).

Is there anything that change?

damage isn't possible unless there is an event at that base

this plugin does not provide protection

you would need truepve or nextgenpve for that

if they aren't providing protection then its not loaded. I recommend default config for truepve

1 hour ago, nivex said:

damage isn't possible unless there is an event at that base

this plugin does not provide protection

you would need truepve or nextgenpve for that

if they aren't providing protection then its not loaded. I recommend default config for truepve

I use TruePVE and this one,

After report, I have checked myself and I found If people go inside PVP Zone, they can raid everybase even If the base is not at event, so any PVP bubble makes players raidable bases, It happened just after I updated today both TruePVE and Abandoned Bases. Before bases near the PVP bubbles were ok and not raidable.

Thank you in advance!

@Nuno Correia

there were no changes regarding that. the one change was for PVP which is player vs player only

i've tested this for you and it's not possible to damage another base inside or outside of the event. the base must be part of an event for this plugin to allow it. a few reasons this may happen for you:

1. enabling purge will allow all bases to take damage and must be started with sab purge

2. truepve is not installed, loaded or is misconfigured

3. another plugin is allowing the damage via the CanEntityTakeDamage hook

7 hours ago, nivex said:

#1 requires abandonedbases.attack

#2 players require abandonedbases.attack and abandonedbases.attack.time, admin requires only abandonedbases.attack. admin does not require abandonedbases.attack.time permission and will see the messages always.

#3 same as #2

@KayKay

Thank you, this sorted my issue out. Appreciate your work !

those having issues with damage being allowed can boil this down to a few reasons

1. truepve/nextgenpve is not installed or it is not configured correctly
2. you have purge enabled, but you'd know this because you would have to type the sab purge command to enable it.
3. another plugin is allowing the damage (zonemanager, dynamicpvp, etc)
4. you have zones allowing this damage, see #3, and is easily fixed by adding the appropriate flags to your zones in the zone plugin

TruePVE:

• you can block this with TruePVE if you map the zone to a ruleset.
• rulesets must be configured properly or the damage will be allowed
• avoid creating entity groups for rules that require too many entity names, such as "buildings" or "structures" or "deployables" - there is always an easier way, see below
• zones which are mapped to "exclude" will be completely ignored by TruePVE. this means you cannot create a ruleset named "exclude"

defaultAllowDamage when set true will allow ALL damage by default and is the most difficult to configure properly as it requires a good understanding of how the plugin works

• best used when mapping zones to a ruleset for PVP
• you do not need to create rules that say "can hurt" unless you have a contradicting rule that says "cannot hurt"
• e.g.:
• anything can hurt players
• players cannot hurt players

defaultAllowDamage when set false will block ALL damage by default unless it is overridden by a flag or by another plugin

• you must create rules to allow specific damage instead. this is ideal and requires the least amount of entity groups in most PVE applications
• does not bloat your config. bloating causes a performance hit and should be avoided.
• generally, PVP zones do not require this being set to false as they contain flags in the zone plugin that you can enable to block damage or actions there instead

So if someone builds a twig on someone else's base, then they get added to the active player list of that base.

Can you find a way to stop this from happening?

@KayKay

lol, ok

Sorry! But seems like this base has not converted although I have set it to convert after 1.5 days. Is there something I am missing to do. It says its not eligible even tho


Thank you for the work you do!

hi, I need to see the permissions not the groups

@KayKay

51 minutes ago, nivex said:

hi, I need to see the permissions not the groups

@KayKay

Here you go.

@KayKay

hi, players require a permission from your config. these permissions allow their base to become abandoned once they've been offline for the configured amount of time.

any of these will work from your config:

• abandonedbases.default
• abandonedbases.mod
• abandonedbases.vip
• if they have multiple permissions then the highest amount of time is prioritized
• it's recommend that the default group be given a permission, such as abandonedbases.default, and vip groups be given a higher amount of time
• o.grant group default abandonedbases.default

events can be configured to start automatically in the config:

Run Once On Server Startup (disabled by default)

• Minimum Required Players Online will require X number of players be connected first
• I recommend setting this to at least 5 (or 25% of your average player base size)
• you can skip this option in favor of the below option instead

Run Every X Seconds (disabled by default)

• this should set to at least 3600
• this cannot be set less than 900
• this should never be set less than 1800 as some scans can take up to 30 minutes on high entity count servers

abandonedbases.attack permission

• this permission will allow a player to attack a base, and if the timer has expired then the base will immediately convert into an event instead of waiting for Run Every X Seconds to start it
• this does pair with Run Every X Seconds, and works without it too so they can hunt for raids as they would do in vanilla
• Automatic Conversions Disabled Between These Times will prevent an event from starting during these times

you can read the update notes for a refresher on how exclude and immune permissions work

7 minutes ago, nivex said:

@KayKay

hi, players require a permission from your config. these permissions allow their base to become abandoned once they've been offline for the configured amount of time.

any of these will work from your config:

• abandonedbases.default
• abandonedbases.mod
• abandonedbases.vip
• if they have multiple permissions then the highest amount of time is prioritized
• it's recommend that the default group be given a permission, such as abandonedbases.default, and vip groups be given a higher amount of time
• o.grant group default abandonedbases.default

events can be configured to start automatically in the config:

Run Once On Server Startup (disabled by default)

• Minimum Required Players Online will require X number of players be connected first
• I recommend setting this to at least 5 (or 25% of your average player base size)
• you can skip this option in favor of the below option instead

Run Every X Seconds (disabled by default)

• this should set to at least 3600
• this cannot be set less than 900
• this should never be set less than 1800 as some scans can take up to 30 minutes on high entity count servers

abandonedbases.attack permission

• this permission will allow a player to attack a base, and if the timer has expired then the base will immediately convert into an event instead of waiting for Run Every X Seconds to start it
• this does pair with Run Every X Seconds, and works without it too so they can hunt for raids as they would do in vanilla
• Automatic Conversions Disabled Between These Times will prevent an event from starting during these times

you can read the update notes for a refresher on how exclude and immune permissions work

Thank you Nivex. You da best!

This has helped me massively. I will try and read more often

no problem

Next revision, simplification request: 

1. When a base goes into an Abandoned state, it stays there fully raidable, (no event timers) until its raided, and the TC is broken.

2. Once the TC is broken,  thats when a timer starts say, 45 min after TC is broken, then it is instatnly destroyed in its entirety.

Thank You for what you do.

@PistOffBastd

I can add an option for no event timer, sure np

there will be a new option along with that option, Seconds Until Despawn After Looting, and if you want to set that to 1 second then you can despawn it this way

Hi ! I just bought your plugin but it is hard to me at the moment to understand .. I just want  a base become abandoned when their players  no longer play ( 2 or 3 days) and I would like the base always stay raidable while there is enough ressources in cupboard or is decaying until someone raid that base .. Is it possible plz? Thanks!

Edit : I just saw i need what PistOffBastd was talking about no? 

Edit 1 : I also saw your comment for @KayKay, it helps a lot !

@FreeManStars

abandonedbases.basic permission is 3 days then it becomes raidable
- give a player this permission or another from the config file
- higher lifetime takes priority
- so if a player has basic and vip perms then vip takes priority

by default it will not automatically convert any bases unless you configure
- Run Once On Server Startup
- Run Every X Seconds (do not set less than 3600)
- you can run a scan manually with sab command

once Despawn Timer expires the base will be deleted/despawned. you can set Despawn Timer to 0 to disable this, but then the base won't be deleted. if someone destroys the TC then the base won't be converted a second time. it will simply decay and no one will be able to raid it again once the plugin is reloaded/server restarts.