Direct answer
Sculk components respond to vibrations, redstone and game events. Dense sensor arrays or continuous activity can create repeated state changes.
How to check it
- Find whether the lag occurs near sculk contraptions, Deep Dark structures or custom datapack detection systems.
- Profile while sensors are triggered repeatedly and compare with a quiet period in the same chunks.
- Check whether observers or command blocks are re-triggering sensors, amplifying updates in a loop.
Example: A sculk-based door that activates once per player is different from a sensor–observer feedback loop repeatedly triggering itself. Inspect activation frequency and neighboring updates.
What to change
Space or isolate unintended feedback paths, avoid needless repeating vibration triggers and throttle plugin actions that process every event.
Software and version notes
Changing sculk physics or replacing sensors can break player traps and redstone logic. Avoid undocumented fork-specific optimization keys.
Verify the result
Confirm alarms, doors or minigames still respond to intended vibration events after measuring lower update spikes.