NoLag Ultimate — Server Optimization & Protection

Vanilla: 85.26 SEI

NoLag: 86.84 SEI

NoLag Ultimate 21.6.0 is a configurable server-side optimization and protection plugin for Minecraft Java Edition. It combines performance monitoring, memory maintenance, entity management, and targeted safeguards against selected gameplay patterns that can place excessive pressure on a server.

Rather than relying exclusively on periodic entity removal, NoLag provides several independent systems for monitoring server activity and managing potentially expensive operations. These include redstone activity, fluid-based machines, Nether chunk traversal, TNT activity, entity processing, dropped items, and command restrictions.

NoLag is designed for administrators who want centralized control over these systems, with configurable thresholds and protection rules. Its behavior depends on the server platform, configuration, workload, and enabled modules; it is not intended to guarantee a fixed TPS or eliminate every possible source of lag.

Core Features

Performance Monitoring & Diagnostics

NoLag includes monitoring and diagnostic tools to help administrators understand the current state of their server.

• TPS and MSPT monitoring: View current server tick performance.
• Memory statistics: Inspect Java heap usage, available heap capacity, and memory-pressure indicators.
• Performance Impact Analyzer: Records activity across categories such as chunks, entities, hoppers, redstone, physics, fluids, TNT, cleanup, and memory.
• In-game dashboard: Access server diagnostics through a graphical interface.
• Server statistics: Review available entity and loaded-chunk counts, memory usage, and configured view distance.

The analyzer provides recorded timing data and estimates to assist investigation. These measurements should be treated as diagnostic information rather than a complete profiler of every plugin or server operation.

RamFixer & Memory Maintenance

RamFixer combines heap-pressure monitoring with incremental maintenance routines.

Its available mechanisms include:

• Configurable heap-pressure thresholds.
• Time-sliced memory maintenance to distribute work across multiple ticks.
• Checks for eligible distant or unreferenced chunks.
• Cleanup of invalid or dead dropped-item entities.
• Cache maintenance for selected NoLag modules.
• An administrative memory sweep with before-and-after measurements.
• Optional, cooldown-protected garbage-collection requests for manual maintenance.

Chunk handling includes safeguards for nearby players, spawn areas, and force-loaded chunks. Sweeps and cache maintenance are designed to limit unnecessary work, but the amount of memory reclaimed depends on the state of the server and the JVM.

Redstone & Physics Protection

NoLag includes separate systems for excessive redstone activity and certain block-physics operations.

The redstone detector evaluates multiple signals, including repeated state changes, clock-like timing patterns, nearby machinery, and activity within the surrounding chunk. This allows it to distinguish stronger machine-like patterns from isolated redstone updates.

When the detector confirms suspicious activity, it can suppress redstone transitions without automatically removing the machinery itself.

A separate physics safeguard can restrict selected physics updates when server performance falls below configured thresholds. These protections are configurable, and administrators should test their settings with their particular farms, redstone builds, and gameplay mechanics.

Fluid Flood & Machine Protection

The Fluid Flood Protection module monitors selected patterns involving water, lava, ice, dispensers, and piston-driven machinery.

Its detection logic considers several signals rather than fluid flow alone, including:

• Unusually dense fluid propagation.
• Rapid placement of fluid sources.
• Repeated dispenser activity associated with fluid mechanisms.
• Piston activity and moving-machine structures.
• Additional evidence associated with suspected flooding machines.

Depending on the detected pattern and configuration, the module can cancel fluid-related events, neutralize suspicious fluid or ice activity, and remove selected machine components.

Important: Machine-component removal is enabled in the supplied default configuration. Review features.fluid-flood-protection before deploying this module on a world containing complex redstone or flying-machine builds. Test the configuration on a staging server before enabling it on a production world.

Nether Chunk Traversal Protection

High-speed travel through the Nether, particularly across the Nether roof, can produce substantial chunk-streaming activity.

NoLag includes a dedicated system that monitors player movement and chunk traversal patterns. Depending on configured thresholds and server conditions, it can:

• Adjust per-player chunk send distance.
• Apply movement or vehicle-velocity damping.
• Track repeated traversal and unusually rapid chunk changes.
• Apply configurable violation thresholds and recovery periods.
• Support permission-based bypasses for trusted players.

This system is intended to reduce the impact of extreme traversal patterns. It does not guarantee that all forms of chunk loading or travel-based lag will be prevented. Teleport handling, bypasses, and Nether-roof restrictions can be configured independently.

TNT & Explosion Controls

The TNT protection module provides configurable controls for explosion-heavy gameplay.

Available controls include:

• A limit on primed TNT entities per chunk.
• Handling for TNT chain reactions.
• Configurable explosion-yield behavior.
• Control over explosion-generated fire.

The supplied configuration sets the default primed-TNT limit to 25 per chunk. Actual behavior depends on the configured limits and protection settings.

Entity Optimization & Stacking

NoLag includes several systems for managing entities under different conditions.

Entity AI Optimization

Eligible living entities outside the configured activation range can have their AI temporarily disabled during performance pressure. AI can be restored when conditions improve. Players and several important entity categories are excluded from this process.

Entity Culling

A per-player visibility system uses distance and viewing direction to manage the visibility of selected entities. This is separate from server-side entity AI throttling and should not be interpreted as a universal reduction in entity ticking.

Mob Stacker

Nearby eligible mobs can be grouped into configurable stacks to reduce the number of individual entities that need to be managed. Stack sizes, scan intervals, and related behavior are configurable. Individual mobs can also be separated through the supported interaction and permission system.

The implementation accounts for selected properties, including age state, sheep color, and slime size, where applicable. As with other stacking systems, test compatibility with custom mob data and plugins that modify entities.

Item Stacker

Compatible dropped items can be merged into larger stacks, reducing the number of separate item entities in an area.

Dropped Item & Entity Cleanup

NoLag provides both scheduled cleanup and a configurable item-lifetime system.

• Periodic cleanup scans are distributed across multiple ticks.
• Cleanup processing has configurable limits and a per-tick time budget.
• Administrators can trigger cleanup manually.
• Countdown announcements are configurable.
• Emergency cleanup can use different processing limits and may include eligible mobs.
• The regular cleanup scanner excludes numerous protected categories, including players, named mobs, tamed pets, leashed entities, villagers, mounts, and selected special entities.

The separate item-expiry system removes tracked dropped items after their configured lifetime. In the supplied configuration, this lifetime is 120 seconds, while the scheduled cleanup interval is 5 minutes.

Review both settings before deployment, particularly if the server relies on dropped items remaining in the world for longer periods.

Hopper & Low-TPS Controls

Hopper throttling changes the handling of inventory-transfer events when TPS falls below configured thresholds. Stronger server pressure increases the likelihood of a transfer being delayed by a cancelled event.

NoLag also includes low-TPS Elytra restrictions and selected command and physics safeguards.

These mechanisms prioritize reducing load under configured conditions, but they can affect automation or gameplay. Administrators should tune their thresholds to match their server's requirements instead of assuming that every safeguard is suitable for every gameplay style.

Command Security

The configurable command filter can block selected commands associated with expensive operations or administrative actions.

The supplied configuration includes entries such as /fill, /setblock, /clone, and selected WorldEdit-related command names. Administrators can modify the list, customize player messages, and enable notifications for staff.

Permission-based bypasses are available for trusted players and administrators. Review the default blocklist against your server's plugins, command aliases, and staff workflow before enabling the filter in a public environment.

Optional Chunk Optimization

NoLag includes an adaptive chunk-optimization module with controls for view distance, simulation distance, player movement, and loaded-chunk housekeeping.

When enabled, this module can adjust configured distances in response to server performance and can use movement information to bias per-player distances. Its chunk-cleaning routine uses incremental processing and protection checks to avoid unloading selected chunks near players or marked as force-loaded.

This module is disabled by default in the supplied config.yml. Enable chunk-optimizer.enabled only after reviewing its distance limits and chunk-cleaner settings. Some optimizations may change the amount of world content visible or simulated by players.

Commands

The main command is /nolag, with /nl, /lag, and /antilag as aliases.

Command	Purpose
/nolag tps	Display TPS and MSPT
/nolag stats	View available server statistics
/nolag performance	Inspect Performance Impact Analyzer data
/nolag dashboard	Open the in-game diagnostics dashboard
/nolag ramfix	Start a manual memory sweep
/nolag cleanup	Start a manual cleanup scan
/nolag items	View dropped-item lifetime information
/nolag reload	Reload NoLag configuration
/nolag version	Display plugin and detected server version

Administrative commands use their corresponding nolag.* permissions. The nolag.admin permission grants access to the main administrative features.

Some global-scan and optimization operations are unavailable in Folia-safe mode. Consequently, not every module or command behaves identically on every supported platform.

Compatibility

Minecraft Java Edition compatibility targets

• Minecraft 1.21.1–1.21.11
• Minecraft 26.1
• Minecraft 26.1.1
• Minecraft 26.1.2
• Minecraft 26.2

Server software targets: Paper, Purpur, Spigot/Bukkit-compatible servers, and Folia.

Java runtime: Java 21 for the listed 1.21.x releases; Java 25 for Minecraft 26.x releases.

These are the project's declared compatibility targets, not a claim that every listed version has been individually integration-tested. Platform-specific API differences may affect individual features.

Configuration & Deployment

NoLag's behavior is controlled through plugins/NoLag/config.yml. Review the available options before using the plugin on a live server, especially:

• Fluid Flood Protection and machine-component removal.
• Item lifetime and scheduled cleanup.
• Hopper throttling and low-TPS gameplay restrictions.
• Command filtering and permission bypasses.
• RamFixer thresholds and manual maintenance.
• Chunk Optimizer and chunk-cleaner settings.

Back up important worlds and test configuration changes on a staging server first. This is particularly important for servers running custom redstone machines, item transport systems, automation-heavy farms, or plugins that modify entity behavior.

Design Goals

NoLag Ultimate brings performance diagnostics, resource maintenance, and targeted protection systems into one configurable plugin. Its purpose is to give administrators additional tools for monitoring server conditions and managing specific sources of overhead without relying on a single blanket cleanup mechanism.

Actual results depend on server hardware, JVM configuration, world characteristics, player activity, other installed plugins, and the chosen protection settings. NoLag should be evaluated in the context of the server it is intended to run on rather than through a universal performance guarantee.