Ledger

Ledger

2M Downloads

Track All Player Arrivals and Departures To/From Server

Torun-S opened this issue · 2 comments

commented

Is your feature request related to a problem?

Currently, the /ledger player command only discloses the first and last join. It would be most beneficial to Ledger as a moderation tool to also include every join and leave done by the player as it greatly aids in establishing timelines in disputes or reports and guides further searches on a timeline basis as opposed to a location basis.

Describe the solution you'd like.

Option 1: Have the /ledger player command disclose all join and leave events and/or list sessions with start and end times (marked by joining and leaving the server respectively). Have the player command accept the before and after parameter.

Option 2: Treat server joining and leaving as an action under an action type such as player-join and player-leave, and then have this introduced as a search parameter. These can obviously not be rolled back or restored so unsure how feasible this is.

Describe alternatives you've considered.

While a timeline can currently be established using current search, it is a trial-and-error process, combing through all player activity and gaps in it or activity done on a particular area - a poor substitute to simply finding session timestamps in logs. It is also possible to use server logs, but ops may not have access to them (in our case, they do not).

Agreements

  • I have searched for and ensured there isn't already an open issue regarding this.
  • I have ensured the feature I'm requesting isn't already in the latest supported mod version.

Other

No response

commented

I second this – this could look something like CoreProtect's "session" action – since migrating from Paper to Fabric, and as a result migrated from CoreProtect to Ledger, the lack of the login/logout tracking is the only main complaint I have with Ledger so far. Having this implemented would resolve that complaint.

commented

I'll third this. Having the login time is great, but there's no indication if a user is still online or when they logged off. Even an entry in the actions table would be great, as I could look for the specific action of logging off.