☰

Corrupted Plugin Config

A plugin fails to load and the log shows a YAML parse error. Its config file has invalid formatting, almost always an indentation or syntax mistake, that the YAML reader cannot understand.

What does this error mean?
Most plugins store settings in .yml files, and YAML is strict about indentation and structure. A SnakeYAML parse error means the file is not valid YAML, so the plugin cannot read its settings and refuses to enable. 
SnakeYAML parse error
Most Common Causes
  • Tabs used instead of spaces for indentation (YAML forbids tabs).
  • Inconsistent indentation between lines.
  • Unquoted special characters or stray colons.
  • A missing or extra space after a colon.
  • A truncated file from a crash during save.
How To Diagnose
  1. Read the error, it usually gives the line and column of the problem.
  2. Open the file and check that line for tabs or bad indentation.
  3. Run the file through a YAML validator.
  4. Compare against the plugin's default config structure.
Recommended Fixes
  • Fix the indentation
    Replace tabs with spaces and align nested keys consistently.
  • Quote tricky values
    Wrap values containing colons or special characters in quotes.
  • Validate the YAML
    Use a YAML linter to confirm the file parses before restarting.
  • Regenerate the config
    Delete (or rename) the file so the plugin recreates a clean default, then reapply your settings.
Analyze My Log
Frequently Asked Questions

YAML treats tabs as invalid indentation. Always use spaces.

The parse error normally prints the exact line and column, start there.

Yes, the new file is default. Back up the old one and copy your values back in carefully.