You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The current logging system generates individual messages for each violation, even when multiple similar violations occur in quick succession. This creates spam and makes it difficult to identify patterns of abuse.
Describe the solution you'd like
Implement a message caching system with these features:
Configuration options:
smart_logging:
enabled: truecache_duration: 30# secondsminimum_stack: 3# violations before stackingbroadcast_interval: 60# secondsexclusive_logs: # only log these types
- bed_explosions
- illegal_blocks# ORignored_logs: # don't log these types
- player_velocity
- minor_violations
Example output:
"[IllegalStack] Prevented 8 bed explosions in the last 30s at world(x: 100-150, y: 60-65, z: 200-220)"
Additional context
This system would make it easier to identify patterns of abuse while reducing log spam. The stacked messages would provide better context about the scale and location of violations.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The current logging system generates individual messages for each violation, even when multiple similar violations occur in quick succession. This creates spam and makes it difficult to identify patterns of abuse.
Describe the solution you'd like
Implement a message caching system with these features:
Configuration options:
Example output:
"[IllegalStack] Prevented 8 bed explosions in the last 30s at world(x: 100-150, y: 60-65, z: 200-220)"
Additional context
This system would make it easier to identify patterns of abuse while reducing log spam. The stacked messages would provide better context about the scale and location of violations.
The text was updated successfully, but these errors were encountered: