Direct answer

Multiple loaded dimensions or plugin worlds can add entities, chunks, tickets and scheduled work. The impact depends on what remains active, not merely the count of world folders.

How to check it

  1. List all worlds or dimensions loaded by your server or world-management plugin; compare with folders on disk.
  2. Record active players, force-loaded chunks, farms and per-world plugin tasks before and during a slow period.
  3. Collect a spark profile under peak use and look for work from specific dimensions or plugins; compare with /spark tps.
  4. Test in staging whether disabling a truly unused world reduces tick work; do not assume a folder may safely be deleted.
/spark tps
/spark profiler start --timeout 120

What to change

Reduce unnecessary loaded chunks, unattended farms and world-specific scheduled tasks before lowering global gameplay settings. If you retire a world, export and verify a backup first and follow the world-management plugin’s documented unloading procedure.

Software and version notes

Vanilla dimensions, Multiverse-style worlds and modded dimensions have different loading rules. World count alone is not an official capacity metric.

Verify the result

Under comparable players and activity, compare TPS/MSPT and world-related hotspots; confirm portals, teleports and data persistence still work.

References