Sets the message prefix for all LagFixer chat messages.
You can use Minecraft color codes (&e, &8, &l, etc.).
Example:"&8[&e&l⚡&8] " → displays as [⚡] in gold and gray.
🔹 prefix_hover
When enabled (true), hovering over the prefix in chat will show plugin version information.
Useful for quick diagnostics and ensuring everyone runs the latest version.
🔹 threads
Number of worker threads used for asynchronous tasks.
Higher values may improve performance but can cause instability if untested.
Keep it at 1 unless you know what you’re doing.
🔹 monitor_interval
Defines how often (in seconds) LagFixer updates performance metrics such as TPS, MSPT, and CPU usage.
Lower values mean more frequent updates but slightly higher CPU usage.
Recommended:5 seconds.
🔹 errors_reporter
If true, LagFixer automatically reports unexpected errors and profiler data to the support team for faster debugging.
Disable this only if you prefer full privacy or run the plugin in a restricted environment.
🔹 updater
When enabled, LagFixer will automatically check for new updates and notify you in console and chat.
Recommended to keep it on for security and performance improvements.
🔹 warnings
Shows console warnings for outdated or legacy API methods that may not be supported in newer Minecraft versions.
Useful for server owners and developers who want compatibility awareness.
🔹 bStats
Enables anonymous performance statistics through bStats.org.
This helps the developer improve LagFixer based on global usage data.
No personal information is collected.
⚙️ Command Settings
🔹 command.permission
Defines the permission required to use /lagfixer and related commands.
Default:"lagfixer.command"
You can assign this permission to admins or trusted staff members.
🔹 command.aliases
A list of alternative command names that can be used instead of /lagfixer.
Default aliases:
/lf
/antilag
/lag
These can be customized freely.
🗺️ Map Settings
🔹 map.interval
Sets how often (in seconds) the /lagfixer map handler updates performance data.
It’s recommended to keep this value at least twice as high as monitor_interval to avoid overloading the server.
Example:
If monitor_interval = 5, then map.interval should be 10 or higher for best stability.