Direct answer

Arrow despawn is about how long certain projectiles remain in the world, not about preventing combat-related projectile processing.

How to check it

  1. Check the installed server type and current spigot.yml reference before assuming a despawn key is present.
  2. Use a controlled ranged-combat session and inspect projectile entities with Paper commands or spark, noting plugin-created projectiles.
  3. Compare arrows embedded in blocks against arrows actively flying; they do not have the same ongoing cost.

Example: An arena that constantly fires arrows at walls can accumulate embedded projectiles; first stop the needless firing or change the arena cleanup interval before shortening every player arrow’s lifetime.

What to change

If the server supports arrow despawn settings, test a modest change on a staging build. Remove unneeded projectile-spawning loops in plugins or command blocks first.

Software and version notes

Aggressive despawn can affect minigames, combat feedback, farms and retrieval of arrows. Spectral, trident and custom projectile behavior may use different rules.

Verify the result

Confirm combat remains correct and count retained projectiles after the same test duration.

References