Skip to content

FAQ

Jump to bottom
EmilDeuOfficial edited this page Aug 18, 2026 · 2 revisions

FAQ

Mobs aren't spawning in my registered chunks. What's wrong?

Check these things in order:

  1. Is ChunkTicker active? Run /ct status. It should say AKTIV.
  2. Is the chunk actually registered? Run /ct list and verify the chunk coordinates.
  3. Mob cap - if you have many chunks loaded, the global mob cap is distributed across all of them. Fewer total loaded chunks = more mobs per chunk. Try reducing the number of registered chunks.
  4. Gamerules - make sure doMobSpawning is true (/gamerule doMobSpawning true).
  5. Light level - hostile mobs only spawn in darkness (light level ≤ 0). Make sure your farm is dark enough.
  6. Biome - some mobs are biome-specific (hoglins spawn only in Crimson Forest, etc.).

Iron golems aren't spawning in my farm.

Iron golem spawning depends on villager mechanics, not normal mob spawning:

  • Villagers must be in the same entity-ticking chunk → ✅ ChunkTicker ensures this
  • At least 10 villagers must be panicking (or the village must meet the bed/door threshold in older versions)
  • Villagers need to have worked and slept recently - this requires the chunk to have been ticking long enough after registration

If golems aren't spawning right after registering the chunk, wait a few in-game days. Villager state (sleep/work cycles) accumulates over time.

How many chunks can I register?

There is no hard plugin limit. However, every entity-ticking chunk has a real performance cost - each loaded chunk runs entity AI, mob spawning checks, Redstone updates, etc. every server tick.

As a rough guideline:

  • 1–10 chunks → negligible impact
  • 10–50 chunks → small impact, monitor TPS
  • 50+ chunks → significant impact, only use if hardware allows

Use /ct status to see how many chunks are currently active.

What happens to registered chunks when the server stops?

When the server stops, ChunkTicker's onDisable() removes all tickets cleanly. The chunk list in config.yml is not deleted. When the server starts again, tickets are re-applied automatically (if global-enabled: true).

What happens when I run /ct off?

All active chunk tickets are removed immediately. Chunks may unload naturally after that. The chunks list in config.yml is preserved. Running /ct on (or restarting with global-enabled: true) restores everything.

Can I register chunks in the Nether or The End?

Yes. Stand in the Nether or End dimension and run /ct set. The world name (world_nether, world_the_end, or your custom world name) is saved automatically.

The plugin says "NMS-Reflection fehlgeschlagen" in the console.

This is not an error - it's an informational message that only appears in certain configurations. ChunkTicker still falls back to the Paper API and works correctly.

Does this work with Purpur or Pufferfish?

Yes. Both are Paper forks that preserve the Paper API. ChunkTicker has been tested to load correctly on these platforms.

Does this work with Folia?

No. Folia uses a completely different threading and chunk loading model that is incompatible with Paper's chunk ticket API.

The server TPS dropped after registering chunks.

Each registered chunk adds CPU load because entities tick every server tick in those chunks. Possible solutions:

  • Reduce the number of registered chunks
  • Reduce the radius when using /ct set [radius]
  • Use /ct off to temporarily pause all tickets
  • Upgrade your server hardware or reduce other plugins' load

Can I edit config.yml while the server is running?

Yes, but you must run /ct reload afterwards for the changes to take effect. For safety, it is recommended to only manually edit config.yml while the server is stopped.

Clone this wiki locally