Skip to main content

Configuration files

EventDirector stores most of its behavior in configuration files.

The exact file names can vary depending on the build, but a typical setup may include:

  • main configuration;
  • messages;
  • events;
  • GUI configuration;
  • backup data;
  • internal plugin data.

Editing configuration files​

When editing files manually:

  1. stop the server or make sure the plugin will not overwrite the file;
  2. create a backup;
  3. edit carefully;
  4. check YAML indentation;
  5. restart or reload;
  6. read the console;
  7. test the edited event.

YAML basics​

YAML is sensitive to indentation.

Use spaces, not tabs.

Good example:

example:
  enabled: true
  message: "Hello player!"

Bad example:

example:
	enabled: true

Tabs can break YAML parsing.

For important changes:

  1. create a backup;
  2. copy the event file;
  3. edit the copy;
  4. test it privately;
  5. enable it only when ready.

Configuration safety​

warning

A small YAML mistake can prevent an event from loading. If a file stops working after an edit, restore the last working backup or compare the file with a working example.

Files generated by the plugin​

Some files are managed internally by EventDirector. Do not manually edit internal data files unless you know what they are used for.