[/LEFT]
# PluginConflictDetector Configuration
# This plugin is read-only and safe to use on production servers.

# -----------------------------------------------------------------------
# Analysis Profile
# -----------------------------------------------------------------------
# Selects the default analysis profile. Each profile bundles a sensible
# set of defaults for a specific audience.
#
#   BASIC      — Commands, Dependencies, Services, Metadata only.
#                WARNING+ severity. SIMPLE output. Best for regular admins
#                who just want to know if something is visibly broken.
#
#   ADMIN      — All checkers enabled. WARNING+ severity. DETAILED output.
#                Recommended default for most server operators.
#
#   DEVELOPER  — All checkers + soft-dependency warnings + INFO level.
#                DETAILED output. For plugin developers debugging issues.
#
#   FULL       — Everything, every severity, TECHNICAL output.
#                Use for deep diagnostics or when filing a bug report.
profile:
  active: BASIC

  # Output mode controls how much detail appears in the HTML report.
  # Leave blank to use the profile's default.
  #   SIMPLE    — Type name + description only.
  #   DETAILED  — + Recommendation field. (ADMIN/DEVELOPER default)
  #   TECHNICAL — + Detail field, Type IDs, severity codes. (FULL default)
  output-mode: ""

  # Per-checker overrides — leave a key absent to inherit from the profile.
  overrides:
    # report-info: false
    # report-soft-deps: false
    # run-event-checker: true
    # run-permission-checker: true
    # run-jar-library-checker: true
    # run-log-analyzer: true
    # performance-listener-threshold: 15
    # max-chat-results: 20

# -----------------------------------------------------------------------
# General Settings
# -----------------------------------------------------------------------

# Directory where saved reports are written (relative to the plugin data folder).
reports-directory: reports

# Path to the server log file used by the log analyzer.
# Relative paths are resolved from the server's working directory.
# Change this if you run the server from a non-standard directory or use a wrapper.
log-file: logs/latest.log

# Log a brief summary to the console whenever an analysis is run.
log-to-console: true

# Default export format when using /conflictcheck save without a format argument.
# Options: txt, json, yaml, md, html
default-export-format: html

# -----------------------------------------------------------------------
# Whitelist / Ignore Rules
# Matching entries are silently dropped from the report.
# -----------------------------------------------------------------------
whitelist:
  # Plugin pairs whose mutual conflicts should be ignored.
  # Each entry is a list of exactly two plugin names (case-insensitive).
  # Example:
  #   plugin-pairs:
  #     - [EssentialsX, CMI]
  plugin-pairs: []

  # Bukkit service class names to ignore when checking duplicate providers.
  # Example:
  #   services:
  #     - "net.milkbowl.vault.economy.Economy"
  services: []

  # Event names whose listener-overlap findings should be suppressed.
  # Example:
  #   event-overlaps:
  #     - "PlayerMoveEvent"
  event-overlaps: []

  # Command alias names whose alias-conflict findings should be suppressed.
  # Example:
  #   alias-conflicts:
  #     - "tp"
  alias-conflicts: []

  # ConflictType names to suppress entirely.
  # Example:
  #   conflict-types:
  #     - "SOFT_DEPENDENCY_MISSING"
  conflict-types: []

  # Permission nodes whose conflict findings should be suppressed.
  # Example:
  #   permission-nodes:
  #     - "some.shared.permission"
  permission-nodes: []

[LEFT]