Closed JumpcraftPK closed 3 years ago
Would this be better as a config setting? If set in the config it could automatically prune old accounts at startup.
That would work as well! An automatic way to purge old accounts after a certain time limit would be great!
On Sat, Dec 12, 2020 at 6:26 PM ElgarL notifications@github.com wrote:
Would this be better as a config setting? If set in the config it could automatically prune old accounts at startup.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ElgarL/GroupManager/issues/63#issuecomment-743937299, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM33KMZDWSEVJ2ZZAVWZHGDSUQQ4VANCNFSM4UY56FBA .
A very early beta build (if you are willing to test it) - Don't use on a live server yet as this version has MANY changes and is very untested (working towards SQL support).
http://palmergames.com/libs/GroupManager.jar Delete your old config and allow GM to create a new one.
v3.0:
- Performance improvements.
- Version update checking now works correctly.
- Add a purge for old users (runs at server start). New users will gain a 'lastplayed' variable upon joining. This value will be updated each time they join. If they do not log in for (default 90 days) their data will be deleted. Manually created users who have never joined will not be deleted. Users created with older versions of GroupManager who never log in will not be deleted. To protect specific accounts from deletion set the lastplayed variable to '0'.
I will go ahead and test this out in our practice server!
On Sun, Dec 13, 2020 at 5:13 AM ElgarL notifications@github.com wrote:
A very early beta build (if you are willing to test it) - Don't use on a live server yet as this version has MANY changes and is very untested.
http://palmergames.com/libs/GroupManager.jar Delete your old config and allow GM to create a new one.
v3.0:
- Performance improvements.
- Version update checking now works correctly.
- Add a purge for old users (runs at server start). New users will gain a 'lastplayed' variable upon joining. This value will be updated each time they join. If they do not log in for (default 90 days) their data will be deleted. Manually created users who have never joined will not be deleted. Users created with older versions of GroupManager who never log in will not be deleted. To protect specific accounts from deletion set the lastplayed variable to '0'.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ElgarL/GroupManager/issues/63#issuecomment-744005943, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM33KM6ILWASEPHQSZKHDRTSUS4ZBANCNFSM4UY56FBA .
You may want to update. I changed the way this works (slightly). It now uses the servers last seen to test if the player needs to be purged. This will be more accurate and can in fact remove old players from before this feature was added. It will also result in less data updates so less chance of a conflict further down the road when SQL is added. You can still protect players from being purged by adding a lastplayed variable set to zero (0).
I'm closing this as its currently in the experimental branch.
With a large amount of players passing through on some servers, this causes group manager to create user data for each individual player. I think a good feature to have would be the ability to delete inactive user data after X amount of days. For example, if a player has been inactive for over 100 days you can "purge" them from your user file.
Ex command: /manuclean
This would also clean up the users.yml file resulting in less lag in the console.