Hi! First of all, thanks for your work on EliteEssentials, the new /spy feature is really useful.
I would like to suggest two improvements for the spy system:
-
Persistent spy status
At the moment, when an admin/staff member disconnects and logs back in, they have to enable spy again manually.
It would be very useful if the enabled spy modes could be remembered per staff member, so if an admin had /spy command, /spy dm, or /spy gchat enabled, those settings would still be active after reconnecting.
Ideally this could be configurable, for example:
spy.persistStaffState: true/false
- saving the enabled spy modes per admin UUID/name
-
Spy log file / audit log
Another very useful feature would be a dedicated log file that saves all detected spy events, even when no admin currently has spy enabled.
For example, the mod could create a log file containing:
- private messages detected by DM spy
- commands detected by command spy
- group chat messages detected by group chat spy
- timestamp
- sender/player
- receiver, when applicable
- command/message content
This would be very helpful for moderation and server security, because staff could review suspicious activity later even if nobody was online or actively using spy at that moment.
A possible config could be something like:
spy.logging.enabled: true/false
spy.logging.logCommands: true/false
spy.logging.logPrivateMessages: true/false
spy.logging.logGroupChat: true/false
spy.logging.file: "logs/spy.log"
This is similar to how we handled it in a separate CommandSpy mod before, where command/message detection was not only shown live to admins, but also saved for later review.
Thanks again for the great mod!
Hi! First of all, thanks for your work on EliteEssentials, the new
/spyfeature is really useful.I would like to suggest two improvements for the spy system:
Persistent spy status
At the moment, when an admin/staff member disconnects and logs back in, they have to enable spy again manually.
It would be very useful if the enabled spy modes could be remembered per staff member, so if an admin had
/spy command,/spy dm, or/spy gchatenabled, those settings would still be active after reconnecting.Ideally this could be configurable, for example:
spy.persistStaffState: true/falseSpy log file / audit log
Another very useful feature would be a dedicated log file that saves all detected spy events, even when no admin currently has spy enabled.
For example, the mod could create a log file containing:
This would be very helpful for moderation and server security, because staff could review suspicious activity later even if nobody was online or actively using spy at that moment.
A possible config could be something like:
spy.logging.enabled: true/falsespy.logging.logCommands: true/falsespy.logging.logPrivateMessages: true/falsespy.logging.logGroupChat: true/falsespy.logging.file: "logs/spy.log"This is similar to how we handled it in a separate CommandSpy mod before, where command/message detection was not only shown live to admins, but also saved for later review.
Thanks again for the great mod!