Understanding Tiquality: The Server-Side Tick Throttler for a Fair Minecraft Experience
Running a Minecraft server can be a delicate balancing act. A single player with an overly complex redstone contraption or an enormous mob farm can drag the server’s TPS (ticks per second) down, making the game lag for everyone. Tiquality steps in as a sophisticated solution, succeeding the popular LagGoggles mod. It’s designed to distribute server tick time fairly, ensuring that players who build responsibly enjoy a smooth 20 TPS, while those who push the limits face gradual throttling. The result is a server where everyone can play without one person’s creations ruining the fun for others.
What Tiquality Actually Does
Tiquality isn’t a simple entity-clearer like ClearLagg. Instead, it works as an intelligent update throttler. Every block and entity that needs to tick—whether it’s a furnace smelting, a crop growing, or a piston extending—gets assigned to a player’s personal tracker. The tracker monitors how much processing time each player’s creations consume. If a player’s builds start hogging resources, their allocated tick time shrinks gradually, potentially dropping their local TPS to 10 or lower. Meanwhile, other players remain unaffected, continuing at full speed.
This approach encourages server-friendly building without outright punishment. Players rarely notice Tiquality’s presence unless they’re the ones causing heavy load. In those cases, they can use the /tq claim command to quickly take ownership of an area, which helps Tiquality assign ticks correctly. The mod is server-side by default but supports clients too, making it versatile for LAN-hosted worlds or dedicated servers.
How Tick Distribution Works
At its core, Tiquality intercepts all calls to Block.randomTickBlock(), Block.updateTickBlock(), Entity.onUpdate(), and ITickable.tickTileEntity(). It uses a high-performance lookup to find the owner of a block or entity. Each owner’s tracker records the nanoseconds consumed by updates. Once a tracker exhausts its granted time for that tick, further updates are queued for the next tick. This ensures that no single player can monopolize the server’s processing power.
Interestingly, if a player isn’t using their full tick allocation, the leftover time is redistributed to others. Logged-out players’ blocks receive reduced tick time (configurable), and entities that move between chunks automatically adopt the dominant tracker of the new chunk. The dominant tracker is determined by the player with the most blocks in that chunk, meaning you naturally take control of an area by building in it.
Getting Started with Tiquality
Installation is straightforward. The mod comes in two variants: THIN and FAT. The FAT version includes the Mixin library, which Tiquality needs to function. If you already have a mod like SpongeForge that ships its own Mixin, choose the THIN release to avoid conflicts. For those who prefer a hassle-free setup, the mod can be easily installed via the foxygame.net launcher — a convenient, flexible, and modern Minecraft launcher where you can download mods right from the menu, saving you the trouble of manual file management.
Once installed, Tiquality begins working immediately. Newly generated areas won’t tick unless blocks are whitelisted in the configuration, so you’ll want to add natural processes like leaf decay and grass growth to the NATURAL_BLOCKS list. The default config is well-documented, and you can reload it at any time with /tq reload.
Commands and Permissions
Tiquality offers a suite of commands for both players and admins, each with specific permissions:
- /tq info – Diagnose whether a block can tick, showing its type, tracker, and status. Use it while standing on or looking at a block.
- /tq track – Assign a block to a player’s tracker without re-placing it. Great for importing existing builds.
- /tq claim [radius] – Claim an area for a player, up to a configurable maximum radius.
- /tq unclaim [radius] – Remove a claim (admin only).
- /tq setblock <feet|below> <type> – Change tick behavior for a specific block type. Types include DEFAULT, PRIORITY, TICK_DENIED, NATURAL, and ALWAYS_TICK.
- /tq setentity <entity_name> <type> – Similar to setblock, but for entities.
- /tq profile <seconds> [player] – Run a basic profiler on owned blocks to identify lag sources.
- /tq acceptoverride <player> and /tq denyoverride <player> – Manage overlapping claims.
Admins can fine-tune everything via the configuration file, adjusting the maximum claim radius, time granted per tick, and which blocks are always ticked or ignored.
Seamless Integration with Other Mods
Tiquality plays nicely with popular server tools. It automatically respects claims from GriefPrevention, GriefDefender, and FTB Utilities, locking the tracker to the claim owner. This means if you’re in a team base, the tick time is effectively pooled, allowing basemates to share resources. SpongeForge users get full permission and command support, along with customized ticking logic. Even LagGoggles integration is in the works, promising a visual interface for less technical players.
Common Pitfalls and Quick Fixes
If you notice blocks not ticking or fluids not flowing, the solution is usually a quick command. Stand on the affected block and use /tq info to check its status. If it’s not tracked, use /tq setblock below NATURAL to whitelist it. For fluids, stand in the liquid and run /tq setblock feet NATURAL. If the server TPS remains low after installing Tiquality, remember that chunk loading and post-world-tick processing are outside its control. You may need to adjust the TIME_BETWEEN_TICKS_IN_NS config value, but be cautious—raising it too high can slow the entire world.
Why Choose Tiquality Over Other Solutions?
Tiquality’s philosophy is fairness through accountability. It doesn’t delete entities or punish players arbitrarily. Instead, it makes the culprit face the consequences of their own actions while protecting everyone else. Its high-performance design uses bitshifting for lightning-fast lookups, ensuring minimal overhead. The mod stores data in the world folder under TiqualityStorage, keeping everything self-contained.
For modpack authors, Tiquality is a dream. You have full permission to include it, and pre-configuring it saves server admins countless hours. The mod’s developer actively encourages community input via GitHub issues and a Discord channel, ensuring that it evolves to meet real server needs.
Final Thoughts
Tiquality redefines how Minecraft servers handle lag by targeting the root cause—uneven tick distribution. It’s a must-have for any server where players push the boundaries of automation and redstone. With its robust configuration, seamless mod integration, and player-friendly commands, it strikes a rare balance between performance and gameplay fairness. Whether you’re an admin tired of chasing lag sources or a player who just wants a smooth experience, Tiquality delivers a smarter, more equitable server environment. Give it a try, and watch your server’s TPS stabilize while everyone gets the performance they deserve.