Direct answer
Generating new villages, strongholds or modded structures can contribute to terrain-generation spikes. Profile new-chunk exploration before disabling structure generation or altering world settings.
How to check it
- Reproduce lag while entering previously unexplored terrain and compare against travel through existing chunks.
- Capture spark timing during generation and note whether structure placement or terrain workers appear in the workload.
- Record game version, datapacks, world-generation mods and the exact world seed if safe to share privately.
- Compare generation speed on a staging server with the same world-generation configuration.
What to change
- Pre-generate expected travel areas during maintenance if generation is a proven bottleneck.
- Reduce conflicting or exceptionally heavy world-generation datapacks/mods only after checking author compatibility.
- Treat disabling structures as a gameplay/world-generation decision: it may affect only newly generated terrain or require creating a new world.
Software and version notes
Existing structures remain in already-generated chunks; changing generator settings does not rewrite established terrain. New versions may change structure placement internals.
Practical example: Example: a modded server runs smoothly while players stay within explored chunks, but spikes when flying into unexplored territory. A profile showing generation workers suggests pre-generation; disabling all structures would change gameplay without proving the bottleneck. Test new chunks on a clone with the same datapacks.
Verify the result
- Check that desired structures still generate in new terrain.
- Measure reduced generation spikes under comparable exploration.