How to Reload Loop Commands After Editing the Config

Edit the Config First

Make your changes in config.yml — add a new loop, change a delay, or edit a command's text. Save the file completely before reloading. The plugin reads the file fresh on reload, so any unsaved edits won't take effect.

Run the Reload Command

Type /LoopCommandReload in chat if you're an operator, or run it from the server console. This re-reads the configuration and restarts the schedules for all loops without requiring a full server restart. You should see a confirmation message in chat or console indicating the reload succeeded.

Troubleshoot a Failed Reload

If the reload reports an error, the most common cause is a YAML formatting mistake — wrong indentation, a missing colon, or a tab character instead of spaces. Fix the formatting and reload again. If a specific loop stops firing after reload, confirm its name is still unique and its delay unit is valid. Reloading resets each loop's timer, so a loop that was partway through its delay will start counting from the beginning again. Keep a backup of a working config.yml so you can restore it quickly if an edit breaks the file.