LessLagg

LessLag

Server performance guardian for Paper/Spigot (1.20.4+) with Folia support.

LessLag is built for production servers that need stable TPS without disruptive “wipe everything” behavior. It focuses on three things:

- Apply safe, configurable mitigation - Apply safe, configurable mitigation - Apply safe, configurable mitigation

Why use LessLag?

- Low overhead, not guesswork - Low overhead based on live server pressure - Low overhead for entities, redstone, AI, chunks, memory, and farms - Low overhead: workload budgeting + on-demand deep metrics

Highlights

- Predictive optimization with health score, MSPT percentiles (`P50`, `P95`, `P99`), uptime, queue status, and spike counters - Predictive optimization with MSPT distribution + avg/min/max - Predictive optimization via `/lg sources` and `/lg trace` to identify hotspots and likely culprits - Predictive optimization with protections for named/tamed/NPC entities - Predictive optimization (activation limits, clock detection, piston pressure control) - Predictive optimization (frustum/distance-based) - Predictive optimization (villager optimizer, breeding limiter, density optimizer) - Predictive optimization from MSPT trend analysis

What makes it practical in production?

- Low-overhead telemetry model for daily checks and incident response - Low-overhead telemetry model before emergency-wide cleanup - Low-overhead telemetry model for villager halls and high-density breeding setups - Low-overhead telemetry model (on-demand deep stats + workload budgeting)

Useful Commands

- `/lg status` — live performance dashboard - `/lg health` — health report and context - `/lg tickmonitor` — tick/MSPT distribution diagnostics - `/lg sources` — lag source analysis - `/lg trace` — runtime bottleneck summary - `/lg density` — density optimizer limits + suppression stats - `/lg breeding` — breeding limiter blocked-event stats - `/lg reload` — reload config/messages without restart

Quick Operations Workflow

1. Baseline with `/lg status` and `/lg health` 2. During spikes, run `/lg tickmonitor` + `/lg trace` 3. Use `/lg sources` to identify likely hotspots 4. Mitigate minimally (`/lg clear hostile`, `/lg ai disable`) only when needed 5. Tune one module group, then `/lg reload` 6. Validate recovery through MSPT percentile and spike trend improvements

Tuning by server style

- Lobby/Minigame: keep balanced defaults, tune entities/chunks gradually - Lobby/Minigame: prioritize density + breeding + villager modules - Lobby/Minigame: emphasize chunks/world-guard and notifications

Permissions

- `lesslag.admin` — full command access - `lesslag.notify` — receive performance alerts - `lesslag.setup` — setup advisor access

Compatibility

- Paper/Spigot `1.20.4+` - Folia supported - Compatibility toggles for common optimization plugin stacks

Install

1. Put `LessLag.jar` in your `/plugins` folder 2. Restart the server 3. Configure `plugins/LessLag/config.yml` 4. Run `/lg status` and `/lg setup` to verify baseline

Links

- Website: https://lesslag-web.vercel.app - Source/Issues: https://github.com/Alexteens24/Lesslag

If you report an issue, include your server version, plugin list, and output from `/lg status`, `/lg tickmonitor`, and `/lg trace`.