1. Community
  2. Plugin Support
  3. Anti Offline Raid
Who is considered the original builder?Not An Issue
Plugin Page
Posted 7 years ago
Last updated 6 years ago
#1

First of all, thanks a lot for this plugin!

In the documentation, you state that "Anti Offline Raid determines who owns a structure based on who built it". Since bases are often built by more than one player working together, I'm unsure about how the plugin determines who is the original builder (or who owns the base, as you put it). I can think of 3 possibilities:

1 - The player who placed the first foundation.

2 - The player who placed the tool cupboard.

3 - The player who first authorized on the tool cupboard.

Posted 7 years ago
Last updated 6 years ago
#2
Building block ownership is per-block or per-entity.  The player who placed the block is the owner.
Posted 7 years ago
Last updated 6 years ago
#3
In response to Calytic ():
Building block ownership is per-block or per-entity.  The player who placed the block is the owner.
I understand that. I was thinking of the base as a whole. Let's suppose it was built by 2 players, and Player 1 goes offline but Player 2 stays. Is AOR going to protect the whole base or just the parts built by Player 1 (the one who went offline)?
Posted 7 years ago
Last updated 6 years ago
#4
From the perspective of AOR there is no "base as a whole".  Determining what consistutes a base and who owns what percentage of that base is outside of the scope of AOR.  That would be a different plugin, and if such a plugin existed and had easy integration points I would happily add them.

The Clans integration is meant to address that issue on a per-block basis.  When clanShare is enabled the entity owner's entire clan is checked as opposed to just the original builder.
Posted 7 years ago
Last updated 6 years ago
#5

Thanks for the reply. I actually like the way the plugin works. It makes it harder for groups to abuse offline protection, unless one member builds the whole base alone, which is unlikely to happen. As it is now, if any member of a group is online, parts built by that member will not be protected, which is good.

 

Some feedback: we noticed while testing that if the cooldown time is set very low - we were using 1 minute to check if things were working - the plugin kept alternating people's status between online and offline, even though no one left the server. AFK time is set to 60 (we don't want AFK players to be protected). We kept using the /ao command to verify this. Our normal config is a 60-minute cooldown though, and that works just fine. Documentation says that the mininum value for afkMinutes is 5, but doesn't mention a minimum value for cooldownMinutes, but maybe there is one, below which the plugin gets "confused" as to who is actually online.

 

Posted 7 years ago
Last updated 6 years ago
#6
AOR doesn't track whether or not a player is "online" or "offline" based on arbitrary connection status at all, it operates on a timestamp and certain in-game actions invalidate the timestamp.  I think that may be part of the confusion.  AOR attempts to determine whether or not active play is ongoing, which is a part of the afk tracking as well.

The configuration values aren't validated against any particular algorithm - it's pretty open ended:

  1. Active Play 
  2. Player AFKs/Disconnects
  3. Cooldown Minutes (NO PROTECTION)
  4. Interim Damage (PROTECTION LEVEL between 1 minute & 1 hour)
  5. Hourly Damage Scale (PROTECTION LEVEL every hour until online again).
Posted 7 years ago
Last updated 6 years ago
#7

In that case, I don't know what was happening then. We kept doing the exact same things - moving around, placing foundations and checking our online status with the /ao command constantly. With cooldownMinutes set to 1, /ao would alternate reporting us as online and offline every couple of minutes, and offline protection would kick in every time it showed us as offline. With cooldownMinutes set to 60. that stopped happening. Nobody stayed AFK even for a minute, we kept doing things and even firing weapons every now and then to make sure whatever was tracking "active play" would consider us online.

Locked automatically