TabTPS: Real-Time Server Performance Monitoring for Minecraft Admins

If you run a Minecraft server, you've probably had that moment: players complaining about lag, and you've no idea if it's your server struggling or their connection. TabTPS puts server health metrics right in front of you (and your players) so everyone knows what's actually happening under the hood.

What TabTPS Does

TabTPS is a server plugin and mod that displays live performance metrics where your players can actually see them. You can show TPS (ticks per second), MSPT (milliseconds per tick), and other server data in three different places: your player tab list, the action bar (that line of text above your hotbar), or as a boss bar at the top of the screen.

Think of it this way: normally, if your server is running at 10 TPS instead of the standard 20, only you (as an admin) would know by checking logs. Your players would just feel the lag without understanding what's happening. TabTPS closes that gap. Players see the numbers. They understand the problem isn't them. And you get immediate feedback about what's actually stressing your server.

It's surprisingly practical for a tool that sounds simple.

Why This Matters for Server Admins

Running a server means constantly balancing performance. Add too many plugins, and TPS tanks. Lag gets worse during prime hours when half your player base logs in. Building large mob farms? That eats resources. Running an ambitious world with custom terrain? More strain.

Without visibility into what's happening, you're flying blind. You make changes and hope they help, but you never really know if it worked. TabTPS gives you that visibility, and it communicates directly to players who might otherwise blame the server unfairly.

Plus, there's a psychological element. When players can see the server is struggling but you're actively working to fix it (and the metrics improve), they're way more patient. When they understand performance issues are temporary spikes rather than constant problems, they stick around. Transparency builds trust, and metrics are the most transparent thing you can give.

Actually, this is one of those tools that feels optional until you run a server, then it becomes indispensable.

Installing TabTPS on Your Server Type

TabTPS supports multiple server platforms, which is huge. Whether you're running Paper (the most common choice for survival servers), Sponge, Fabric, or NeoForge, there's a version for you.

For Paper servers, the installation is straightforward. Download the plugin JAR from the GitHub releases, toss it in your plugins folder, and restart the server. That's it. If you're setting up a new server from scratch, tools like the Server Properties Generator can help you configure basic server settings quickly, so you can focus on installing performance monitoring like TabTPS afterward.

1. Download TabTPS JAR from the GitHub releases page
2. Place the JAR in your /plugins directory
3. Restart your server
4. Navigate to /plugins/TabTPS/ and customize configs as needed

The Fabric and NeoForge versions require Fabric API as a dependency (at least for Fabric), so make sure that's installed first. That setup's the same conceptually, just make sure you're grabbing the right build for your platform and Minecraft version. This project supports Minecraft 26.1.2 and several earlier versions, so check the releases page to grab the one that matches your server version.

The Main Features That Matter

TabTPS has more granular control than you'd expect from a "show me numbers" plugin.

Display Configurations: You can create custom display configs in the config folder, and assign different ones to different permission groups. Maybe admins see detailed performance metrics, but regular players just see a simple TPS indicator. Or maybe you change the display based on server load. The flexibility is there. You can even customize what information gets displayed where, which matters more than it sounds when you're trying to keep your UI clean.

Themes: There's a theming system for colors. Not critical, but nice if you want the metrics to match your server's brand or just make them easier to read at a glance.

The /tickinfo and /mspt Commands: These show you a breakdown of what's eating CPU time on each tick. Is it the main game thread? Plugin overhead? Mob pathfinding? You get numbers. It won't pinpoint exactly which plugin is the culprit (you'd need more advanced profiling tools for that), but it narrows the field faster than guessing.

Ping Display: The /ping, /ping [player], and /pingall commands show player latency. This is useful for diagnosing whether lag is server-side or player-side. If everyone reports lag but ping numbers are normal, it's definitely your server. If everyone's ping spikes together, someone on the network's having a rough time.

Memory Info: The /memory command shows how much RAM different parts of the JVM are using. This is less useful for casual servers but genuinely helpful if you're trying to figure out why your server is eating 12GB of RAM when you allocated 8GB. You can see garbage collection pressure, heap usage, and spot memory leaks before they become critical.

Configuration Tips and Common Gotchas

One thing that catches people off guard: the display configs use a permission system. By default, everyone gets tabtps.defaultdisplay, which works fine. But if you start creating custom configs, remember that only players with the associated permission will use that config.

If a player has permission for multiple configs, their priority setting in the main config determines which one kicks in. This is intentional, but it trips people up because they assume the last permission wins.

If you're running permissions via LuckPerms or another plugin, make sure your permission nodes are actually being applied. I've seen servers where the display just doesn't show up, and it's because the permission wasn't synced properly. Double-check your permissions setup if the metrics aren't appearing.

The reload command (/tabtps reload) lets you update configs without restarting, which is handy. But be aware that some changes might require a full restart to take effect properly, depending on what you're modifying. When in doubt, restart.

One more thing: the tab display works best when you're not already using massive portions of the tab list for other plugins. If you've got a huge scoreboard or banner system that uses the tab list, TabTPS needs space to work with. It's not incompatible, but you'll want to plan your layout. If you're designing a custom look for your server, consider whether player names, team displays, and performance metrics can coexist without cluttering the screen.

For smaller servers, consider starting with a simple action bar display instead of reworking your entire tab list. It's less intrusive, gives everyone the info they need, and you can always expand it later. You could also use the Minecraft Text Generator to create custom formatting for your other server messages, keeping everything visually cohesive.

Alternatives and When They Matter

Spark is legendary in the server admin community for performance profiling. If you need deep CPU and memory analysis, Spark is probably better. But Spark is more for admins diving into logs and data; TabTPS is for real-time visibility that everyone sees. They actually work well together. Spark diagnoses the problem. TabTPS shows it to your players.

There are a few other monitoring plugins out there, but most solve a different problem. GeyserMC has some performance monitoring, but it's coupled to Bedrock support, so only relevant if you're running a hybrid server. ProtocolLib can help with network profiling, but again, different tool for a different job.

Honestly, TabTPS fills a pretty specific niche (real-time metrics everyone can see), and the alternatives either overlap too much or solve a different problem. For what it does (showing metrics your players can see without needing external dashboards), it doesn't have a direct competitor in the plugin ecosystem. That's actually why it's remained relevant for so long.

The project itself is well-maintained, currently supports Minecraft 26.1.2, and the 320 GitHub stars reflect a solid community that actually uses it. Written in Java with an MIT license, it's transparent and free to use on any server type that supports the plugin API.