⚙ Configuration Guide

EliteLogs comes with a powerful and flexible `config.yml`.
Below is a full overview of what you can configure:

✔ Core
- `enabled` — enable/disable the plugin
- `debug` — verbose mode for debugging
- `language` — set the active language (EN, RU, DE, FR, ES)

✔ ANSI
- Toggle colored console output
- Customize ok/warn/error/reset color codes

✔ Banner
- Show ASCII banner on startup
- Options: show-version, style, color

✔ Discord
- Enable Discord webhook alerts
- Choose which events to send: errors, warns, watchdog, sessions, inspector

✔ Logs
- Structured `.yml` logs (replaced legacy `.txt`)
- Daily rotation with `/elogs rotate [force]`
- Archive old logs automatically
- Keep logs for X days
- Split logs by player and session
- Enable/disable log categories: chat, commands, economy, combat, etc.

✔ Sessions
- Track player sessions
- Save both global and per-player data
- Configurable autosave interval

✔ Inspector
- Collects server details: plugins, mods, configs, GC, system info
- Trigger manually with `/elogs inspector`
- Can be auto-triggered by Watchdog

✔ Metrics
- Interval-based performance metrics
- Access via `/elogs metrics`

✔ Suppressor
- Console spam filter
- Modes: blacklist / whitelist
- Configure spam limit, cache size, TTL, regex filters

✔ Watchdog
- Monitors TPS and error rate
- Auto-actions:
• Run Inspector
• Create crash-report
• Send Discord alert

Commands

• `/elogs help` — show help menu
• `/elogs reload` — reload configuration
• `/elogs inspector` — run Inspector scan
• `/elogs metrics` — show performance metrics
• `/elogs export` — export logs
• `/elogs rotate [force]` — archive old logs
• `/elogs logs` — list available log categories
• `/elogs version` — show plugin version

Tip:
Start with defaults, then fine-tune. This prevents noisy logs and keeps output clean.

Source & Documentation:
GitHub – EliteLogs