AutoPurge

Alright nevermind, just seems weird there's been nothing to remove for 9 days even though I have 388 hits on Displayname, and showing 256 sleepers in game.

I have 30 people last login 09/19/2016
I have 153 people last login 09/18/2016
I have 53 people last login 09/17/2016
I have 0 people last login 09/16/2016
I have 0 people last login 09/16/2016

On a 4 day purge that hasn't found anything to remove for 9 days, I'm saying it seems weird.

 

You could set "removeRecordAfterDays" maybe to 10 days...this would remove any orphanad entries in the data-file for entries not actualized since ten days.

 

Hi~Fujikura
I have two questions:
1urgeOnStart this will remove all entries ?
2:removeRecordAfterDays If i restart the server, the time will reload?

 

PurgeOnStart will run the check (same like by timer or 'autopurge.run') right after the plugin was loaded.

"removeRecordAfterDays" checks on plugin loading for orphanaged entries older then x days and does remove them from the data-file.

 

Thank YOU!

 

Still waiting for the option to purge raided bases.

Most people simply build a base elsewhere, making this plugin useless for high pop realms where people constantly rebuild.

Please add an option that if a building doesn't have a tool cupboard attached it removes, or no door has been opened in X (config) hours!

 

I would like to see such a function too in the plugin, but it sounds easier to realize then it is...
I did already some tests against the decay system and tests against resets of the timers, but i did not get the results i did expect to realize such a function.

 

I noticed a huge bug. If a player change his name the old structures of him will get purged after the time which got set.

Would it be possible, that it checks steamids?

 

Please add support for door checks We have a lot of users who are regulars on our servers, but after getting raided they leave the old base and make a new one. This makes the current purge a bit useless since the user is on quite often. Thanks in advance!

I think this has been mentioned before but I think Fujikura you it had to work in all cases. Even having a Config flag that was set to false by default would be amazing

 

It checks only SteeamID's and nothing else.
[DOUBLEPOST=1475313397][/DOUBLEPOST]

That was already asked a few times (and two posts above) and i already answered thats it not that easy to implement because of the complexity of the decay-system.

 

UPDATE: THe doors can't be used as trigger indicator. Their value "decayResetTimeLast" will reset on every server-restart.

 

Code:

[09/25/2016 18:38:49] Nothing to remove... up to date.
[09/26/2016 07:42:02] Nothing to remove... up to date.
[09/26/2016 18:45:33] Nothing to remove... up to date.
[09/27/2016 06:26:57] Nothing to remove... up to date.
[09/27/2016 07:59:18] Nothing to remove... up to date.
[09/28/2016 08:58:06] Nothing to remove... up to date.
[09/29/2016 08:58:10] Nothing to remove... up to date.
[09/30/2016 14:16:15] Nothing to remove... up to date.
[10/01/2016 14:16:20] Nothing to remove... up to date.

193 sleepers, 5 day purge timer, maximum pop of about 18 per day for 10 days.

Same story with this as Anti Offline raid, the data resets on update day Got no one in the data file showing as last online past Thurs

 

The plugins does delete only thoes entries, which are purged or are older then the default limit of 30 days for orphanaged entries.
It does not clean it byself with valid data-sets in it....Either check your config again, maybe you missed sth, or your wipescript is a bit to salty

 

You're an amazing developer Fujikura! Thanks so much for looking into this. Would another alternative be to see if the building owner has actually touched that building? I have no idea if that is implementable or not, or whether the logging for it would be atrocious. Autopurge is amazing either way

Would just be really amazing for older bases that an active user isn't using anymore.

 

There's always a solution for nearly most cases...but often "a really must have solution" costs cpu/mem alot...
[DOUBLEPOST=1475540140][/DOUBLEPOST]

Basically a door check system could be used on that way, if they are used or not in an amount of time...combined as dataset for each base....
But that will not be accurate enough, and could generate also an overheap...For example on raided bases where all doors were destroyed by raid

 

What????

I suspect it's the same problem that anti offline raid has. In that the data file gets broken on update day.

 

Idk whats the prob on AntiOfflineRaid, but i'm sure, AutoPurge does not loose its files without external action.

 

Yeh. The anti offline raid guy was sure of himself too

 

And he also righ on it!
Both plugins use these functions to save the data (AntiOfflineRaid only n.1 and 2:

Code:

        private void OnServerSave()
        {
            SaveData();
        }        private void OnServerShutdown()
        {
            SaveData();
        }
       
        private void Unload()
        {
            SaveData();
        }

...but the main needed on Restart is "OnServerSave".
This one will be called on each saveinterval and on restart.
The data-files can't "glitch" away.

So you need to identify some issues in your complete restart process.
Otherwise me and @Calytic can't assist you at finding YOUR specific problem