AutoPurge

Moved

Total Downloads: 5,820 - First Release: Dec 27, 2015 - Last Update: Sep 18, 2017

5/5, 34 likes
  1. Fujikura updated Auto Purge with a new update entry:

    1.4.2

     
  2. (12:09:20) | [Oxide] 04:09 [Info] [AutoPurge] Purge will be executed every: 24 hours (1D | 0H | 0M | 0S)

    (12:09:20) | [Oxide] 04:09 [Info] [AutoPurge] Players become inactive after: 4 days (4D | 0H | 0M | 0S)

    Nice one, this is helping keep my server stable.
     
  3. IS it possible to not reset the data upon a reload? I know I've got guys who havnt been on for 4 days but because I reloaded the plugin today it's reset the data :( So unless they ever log in again they'll just stay there until decay takes care of their place
     
  4. It should'nt change the timestamp if the player is'nt online.
     
  5. Ah it looks like it must get reset on server restart as I just went through the Oxide logs and can see the other admin restarted last night, it's why Anti Offline raiding is reset too so it seems.
     
  6. is there a way to undo a purge, the system removed some bases of players that just logged on
     
  7. Only by restosting with save-file. The system does only remove from inactive players. It can't purge stuff from players being online.
     
  8. Well it happened with 5 players that had been on maybe a day or two ago right after i installed the new update. the others on the list where fine but i know for a fact they 5 in question had been on. Hmm i wonder if something bugged on my end.

    Have no idea how to rollback a save like that :/
     
  9. Player timestamps got updated when they login, logoff, are online while plugin loading/reloading and finally before a purge-run.
    Maybe you've set your inactive timer to short...
     
  10. Is there maybe a way to get the plugin to tie in better with the server's last online thing? If the auto purge data gets reset for whatever reason (happened on our server a couple times, dunno why, just bugged) then there's no data for the plugin to work with and the building just sits there, this plus a slow decay scale like we have means it's just cluttering up our entity count. Can it not just rely on it's own data file but instead use whatever the server's data is? I can see in my Rust Admin program lots of last connected data for users that aren't included in the Auto Purge data file since it's reset. It would be really useful :)
     
  11. Idk why your data-file got resettet, AutoPurge itself does not do that. It does only actualize the entries of players which come online and go offline, and does delete the entries of those, which were purged.
     
  12. Got mine set to 4 days and

    Code:
    [09/13/2016 03:07:38] Nothing to remove... up to date.
    [09/14/2016 10:20:41] Nothing to remove... up to date.
    [09/15/2016 07:54:18] Nothing to remove... up to date.
    [09/16/2016 07:43:48] Nothing to remove... up to date.
    [09/16/2016 11:02:24] Nothing to remove... up to date.
    [09/17/2016 08:32:57] Nothing to remove... up to date.
    
    No way there's been no one who hasnt been on for 4 days :/

    What does the last time number refer to as I can't make out if it's some weird way of saying a date/time.

    "LastTime": 1474096423
     
  13. Its a unix/epoch timestamp.
    You can check their realtime here: Epoch Converter - Unix Timestamp Converter
     
  14. Fujikura updated Auto Purge with a new update entry:

    1.4.3

     
  15. After loading the plugin I get this Error
    Code:
    [Error] Failed to call hook 'OnServerInitialized' on plugin 'AutoPurge v1.4.3' (KeyNotFoundException: The given key was not present in the dictionary.)
     
  16. Fujikura updated Auto Purge with a new update entry:

    1.4.4

     
  17. Ok so here's something weird, now I've got the proper human time and date, I have 236 null's for "LastDateTime" out of the 256 matches to DisplayName

    I compared a couple of them to the last online date in the Rust Admin app and 1 was on 2 days ago, another I saw on a few hours ago, initially I'd say is there a way I can get rid of the nulls, but when I know some of em were online as late as today :/
     
  18. The NULL'S are only initially, because to change them at load with this update caused an error...they wil get updated on logon/logoff.
    And its only an informational variable without function.
     
  19. Can I not just replace all the nulls with a date and they'll be caught on the next purge?

    check this out

    [09/13/2016 03:07:38] Nothing to remove... up to date.
    [09/14/2016 10:20:41] Nothing to remove... up to date.
    [09/15/2016 07:54:18] Nothing to remove... up to date.
    [09/16/2016 07:43:48] Nothing to remove... up to date.
    [09/16/2016 11:02:24] Nothing to remove... up to date.
    [09/17/2016 08:32:57] Nothing to remove... up to date.
    [09/17/2016 11:02:28] Nothing to remove... up to date.
    [09/18/2016 17:53:51] Nothing to remove... up to date.
    [09/18/2016 18:40:08] Nothing to remove... up to date.

    I'm now up to 9 days, I checked my log file and I can only find last actual login dates of the 17th, everything else is null :/ I'm now up to 250 sleepers and my nightly pop is only peaking at 25-30, lot of deadweight out there.

    Can you please give me a way to modify the Auto Purge data file to change all those nulls to something purge will pick up, at this point I don't mind if I have to get rid of everyone who hasnt been on for 2 days.
     
    Last edited by a moderator: Sep 19, 2016
  20. The "LastDateTime" gets only updated,when the player logons or logoff. Its the same date like "LastTime" dos contain htne, but more human readable. The field "LastDateTime" has no function... so adding any data there would be useless. It translate you only the "LastTime" value.