Manual scan (sab) finding 0 bases to purge

Plugin Version: 2.2.6 Issue Summary: The plugin successfully converts bases when using the sar purge command (Purge Day mode), but the standard scheduled scan or manual sab command consistently finds 0 bases to convert, even when the Lifetime (Days) is set as low as 1 day.

What we have already configured/tried:

Permissions: Confirmed that players have the abandonedbases.basic permission.

Zone Manager: Emptied the "Allowed Zone Manager Zones": [] list to ensure the entire map is being scanned.

Minimum Requirements: Lowered "Foundations Required" and "Walls Required" to 1 to ensure small solo bases are not being skipped.

Admin Exclusion: Verified the admin has the abandonedbases.exclude permission so admin authorization on TCs does not reset the inactivity timers.

Scan Settings: Set "Run Once On Server Startup": true and have manually triggered scans using sab.

Technical Data/Outcome:

The "No Player Owner" Error: When running a scan, the console reports a very high number of structures (e.g., 386) with "No Player Owner".

The "Cannot Purge" Error: The scan also lists approximately 90 bases that it finds but labels as "cannot purge".

The sar purge Contrast: Running sar purge immediately found and converted 66 bases into raid events. This confirms the plugin can create the events, but the standard logic for determining player inactivity/ownership appears to be failing during a normal sab scan.

Specific Questions for the Developer:

Why does the plugin report hundreds of "No Player Owner" entities on a standard procedurally generated map, and is this causing the sab scan to skip valid bases?

Is there a specific data-file or cache (outside of the config) that should be deleted to fix the "No Player Owner" desync?

Why would sar purge work perfectly while sab finds zero targets on the exact same map with a 1-day lifetime setting?

heya,

no player owner could be for non-player bases such as Raidable Bases events or other copypaste buildings. it must have a player owner or it will be skipped. there could be a valid reason why, but it's impossible for me to know without access to the server. 

1. using PermissionsManager or AdminMenu, show me screenshots for all of these pertaining to AbandonedBases

• admin group
• your permissions
• default group permissions
• permissions for a single player whose base should be abandoned already

2. grant yourself these permissions and go attack any base that should be abandoned already. show me the messages you receive

• abandonedbases.attack
• abandonedbases.attack.time
• cannot use near another event or any ally base
• no messages means the player doesn't have the basic permission or they have an immune permission

3. attach config

Hi tnx for you quick reply. It took me while to get online.  

I performed the attack test. The timers are appearing on all bases, but the maximum inactivity recorded is 3 days and 15 hours. It appears the plugin is only counting inactivity from the moment it was installed/started, and is not reading the lastSeen data from the server's user persistence database for time prior to installation. Because my config was set to 5 days, sab was ignoring these bases.

AbandonedBases(2).json

hello I've taken a look at your config file and will respond separately regarding sab and automated timers.

"Loot Required (SAR)": 0, 
"Foundations Required (SAR)": 1, 
"Walls Required (SAR)": 1,

I understand you did this for testing, but players will be able to exploit this if they're allowed to use the /sar command
PVP is enabled for sar by default, and if no limits are in place then a player need only to build a single foundation, deploy a TC on it and then use /sar to kill anyone inside of the event
I recommend setting strict requirements so that players cannot exploit this, even if they're not currently allowed to use the /sar command.

"Loot Required": 0, 
"Foundations Required": 4, 
"Walls Required": 3,

these settings require the base to be abandoned before it will convert so there's no concern here and it's safe to use whatever settings you find appropriate.

heya. yes, it's intended that the time begin when the plugin is installed. that explains the confusion with bases not converting, they shouldn't because not enough time has elapsed yet. the plugin shouldn't be using any other databases, it tracks this itself when installed. I don't think the persistence db's store any last seen times but I'd be interested if they did.

also, if the plugin is unloaded for more than a day then it will start over again too.