Clumps 26.2.1: Minecraft XP Orb Server Setup Guide

Minecraft Java server utility

Clumps groups nearby experience orbs into fewer entities and changes pickup so a touched group is collected immediately. The current Minecraft 26.2 release is 26.2.1 for Fabric and NeoForge. The creator’s modern-version guidance says installation is required on the server for 1.17 and newer; a player joining that server does not need a matching client JAR for the core behavior.

Current 26.2 file choice

Install the file that matches the server loader, not the client launcher’s unrelated profile. For a single-player world, the integrated server is part of the client process, so placing the correct JAR in that instance is how the modern server-side behavior can run.

What a useful test must prove

A smoother-looking pile of orbs is not enough. The test must also show that the expected experience total remains. Choose one repeatable source with a known output, record the player’s starting level and progress, collect the result, and compare the total under the same conditions. Avoid random mob drops for the first pass because variable rewards make differences hard to interpret.

Clumps can reduce the number of orb entities in a dense area, but MineBrush has not benchmarked a tick-rate improvement on this server. Farm design, entity counts, CPU scheduling, view distance, loader, and other mods can dominate performance. Treat the project’s purpose as a reason to measure, not a guaranteed FPS or TPS result.

Safe install and server baseline

1. Stop the server cleanly and make a restorable world and configuration backup. For single-player, use the MineBrush modded-world backup checklist.
2. Confirm Minecraft 26.2 and the active loader. Add Clumps 26.2.1; add Fabric API only for the Fabric route.
3. Start the server and read the log for a successful load before allowing the normal player group to join.
4. Use a disposable test area. Record starting XP, create the same fixed reward, count or observe the orb grouping, then collect everything.
5. Restart once and repeat. If possible, compare server tick data under the same farm and player conditions rather than comparing unrelated sessions.

Diagnose missing grouping, delayed pickup, or XP mismatch

If orbs do not group, confirm the mod is actually in the server or integrated-server instance and appears in the startup log. A client-only install will not change a remote server. Check that the file name matches Fabric or NeoForge 26.2 and remove duplicate Clumps JARs from older versions.

If pickup behaves strangely, retest with one player and a fixed reward while disabling only other XP-altering mods. Magnet, skills, claim, event, or farm mods may intercept or transform XP. If the total differs, stop the test and preserve the world copy, logs, starting values, and exact mod list. Do not continue operating an automated farm until the reward path is understood.

Measure the right server outcome

For performance work, record average and worst tick time, player count, loaded chunks, view distance, the exact XP event, and the observation window. Compare the same saved world and farm state before and after. Client FPS is not a substitute for server tick data, and a quiet test with no active farm cannot represent the high-orb condition Clumps is meant to address.

Watch the log for repeated entity or mixin errors and check memory and CPU saturation during both runs. One shorter spike does not establish a durable improvement. If the host automatically restarts or changes resource limits, discard that comparison and repeat under controlled conditions.

Rollback and evidence boundary

Stop the server, archive the log and configuration, remove the Clumps JAR and any dependency no remaining mod uses, then restore the baseline test. Keep the backup until normal saves and XP events have been observed after rollback.

• Clumps creator releases and installation guidance
• Creator source repository and issues

MineBrush rechecked creator metadata on August 28, 2026. We did not run a server, count entities, or measure TPS. Exact XP preservation, farm compatibility, hosting impact, pickup timing, and mod interactions remain unknown until reproduced.