Minecraft Server Item & Dropped Entity Optimization: Stop Item Lag from Destroying Your Server

# Minecraft Server Item & Dropped Entity Optimization: Stop Item Lag from Destroying Your Server

Dropped items and experience orbs are among the most commonly overlooked performance drains on Minecraft servers. A single player farming a mob grinder or crop farm can spawn thousands of item entities within minutes — and if your server isn't configured to handle them efficiently, your TPS will crater fast.

This guide covers exactly how dropped item entities work at the server level, which config settings actually matter, and how to tune your server to handle heavy item loads without ruining gameplay.

Why Dropped Items Kill TPS

Every dropped item on the ground is a tracked entity. The server must:

• Update its position each tick
• Check for nearby items to merge with
• Check for nearby players to collect it
• Broadcast its state to nearby clients
• Eventually run its despawn timer

At scale — think 5,000 dropped items in an active mob farm — this becomes a significant fraction of your main thread's tick budget. Combined with XP orbs (which behave similarly but are even more numerous), this can shave 5–10 TPS from a server that's otherwise well-optimized.

Key Config Files and Settings

bukkit.yml — Despawn Rates and Merge Ranges

This is your first stop. Open bukkit.yml and look for the spawn-limits and item-despawn-rate settings:

spawn-limits:
  monsters: 70
  animals: 10
  water-animals: 5
  water-ambient: 20
  ambient: 15

tick-per:
  animal-spawns: 400
  monster-spawns: 1
  water-spawns: 1
  ambient-spawns: 1
  autosave: 6000

More importantly, under world-settings:

world-settings:
  default:
    item-despawn-rate: 6000

The default 6000 ticks equals 5 minutes. For servers with heavy farms or frequent PvP, consider reducing this to 3000 (2.5 minutes) or even 1200 (1 minute) in specific worlds. Be cautious — players do notice shorter despawn windows on survival servers.

spigot.yml — Merge Radius

This is one of the highest-impact settings for item lag:

world-settings:
  default:
    merge-radius:
      item: 2.5
      exp: 3.0

Increasing item to 3.5 or 4.0 means nearby dropped items get merged into stacks faster, dramatically reducing the total entity count. exp can safely go up to 4.0 or 5.0 without meaningful gameplay changes.

Note: Setting these too high (e.g., 8.0+) can cause items to visually teleport or merge unexpectedly in tight spaces. Stay reasonable.

paper-world.yml (or paper-world-defaults.yml in newer Paper builds)

Paper adds granular control over item and entity behavior:

entities:
  spawning:
    count-all-mobs-for-spawning: false

misc:
  update-pathfinding-on-block-place: true

entity-per-chunk-save-limit:
  experience_orb: 16
  arrow: 16
  fireball: 8
  small_fireball: 8
  snowball: 8
  ender_pearl: 8
  thrown_exp_bottle: 8
  item: 32

The entity-per-chunk-save-limit section is critical. It caps how many of each entity type gets saved to disk per chunk. If a chunk has 10,000 XP orbs somehow, this prevents them from bloating your world files and re-loading on the next startup.

Also check:

alt-item-despawn-rate:
  enabled: true
  items:
    COBBLESTONE: 300
    NETHERRACK: 300
    DIRT: 300
    GRAVEL: 300
    SAND: 300

The alt-item-despawn-rate feature in Paper lets you define per-item-type despawn timers. Worthless bulk items like cobblestone, dirt, and gravel can despawn in 300 ticks (15 seconds) while valuable items keep the full 5-minute window. This is one of the best features for farm-heavy servers.

purpur.yml — Additional Item Controls

If you're running Purpur, you get even more fine-grained options:

world-settings:
  default:
    gameplay-mechanics:
      item-entity-max-age: 6000
    mobs:
      zombie:
        drop-chance:
          equipment: 0.0

Reducing equipment drop chances on mobs is a sneaky but effective way to reduce item spam in mob farms without changing item despawn rates globally.

Practical Strategies for Farm-Heavy Servers

1. Use Hoppers Aggressively Near Farms

Hoppers collect items from the world instantly when items land on them. Well-designed farms that funnel drops directly into hoppers produce zero item entities. If players are building item farms that spray drops everywhere, encourage better farm design or use a plugin like ClearLagg (carefully configured) to handle cleanup.

2. ClearLagg Configuration (If You Use It)

If you use ClearLagg, avoid the default broadcast-spam configuration that annoys players. Instead, configure it to only clear items in specific worlds or only when item count exceeds a threshold:

auto-clear:
  worlds:
    - world_nether
  interval: 180
  count-threshold: 2000
  broadcast: false

Never blindly clear all entities — this will remove villagers, farm animals, and other important entities if misconfigured.

3. Limit XP Orb Count with Paper

XP orbs are notorious because mob farms produce enormous quantities. In paper-world.yml:

entities:
  spawning:
    experience-merge-max-value: 100

This merges XP orbs together up to a max value of 100 XP per orb, drastically reducing orb count in active grinders.

Diagnosing Item Lag

Before tuning blindly, verify that items are actually your problem. Use /spark to profile your server:

/spark profiler --thread *

Look for EntityTickList or Entity.tick in the flame graph. If item entities are taking more than 5% of your tick time, the optimizations above will make a real difference.

Tools like [PulseNode](https://pulsenode.tech) can help you correlate TPS drops with player activity spikes — useful for identifying when and where item accumulation events occur across your server's history.

Quick Reference: Recommended Values

| Setting | Default | Recommended |

|---|---|---|

| bukkit.yml item-despawn-rate | 6000 | 3000–6000 |

| spigot.yml merge-radius.item | 2.5 | 3.5–4.0 |

| spigot.yml merge-radius.exp | 3.0 | 4.0–5.0 |

| paper alt-item-despawn-rate (junk) | disabled | 300 ticks |

| paper experience-merge-max-value | 0 (off) | 100 |

| paper entity-per-chunk-save-limit item | unlimited | 32 |

Conclusion

Dropped item and XP orb optimization is low-effort, high-reward work. A few config changes across bukkit.yml, spigot.yml, and paper-world.yml can recover significant TPS on farm-heavy survival or SkyBlock servers — without any noticeable gameplay impact for your players.

Start with merge radius and alt-item-despawn-rate, profile with Spark after changes, and iterate from there. If you want a clear picture of how these changes affect your server's TPS over time, [PulseNode](https://pulsenode.tech) gives you real-time and historical performance graphs so you can see exactly what's working.