Skip to content

Configuration

alexisleder edited this page Nov 8, 2026 · 10 revisions

Configuration

LederProtections creates its files under plugins/LederProtections/.

File Purpose
config.yml Main features, rules, integrations, limits and safety settings.
menus.yml Layouts, icons, text, external-pack presentation and gui-style.
stones.yml Stone types, radii, materials, prices, permissions and upgrades.
lang/es.yml Spanish messages.
lang/en.yml English messages and fallback.
protections.yml Managed protection data; do not edit while the server is running.
public-protections.yml Public profiles, favorites and visit metadata.

Missing bundled keys are merged safely on startup and /lep reload; existing custom values are preserved and backups/default snapshots are maintained. Keep your own server backup before every update.

Reloading

/lep reload

Reload refreshes configuration, language, stones, rules, public-directory settings, holograms and optional compatibility hooks. Use a full restart after installing/removing dependencies or for major production changes.

PlaceholderAPI

compatibility:
  hooks:
    placeholderapi:
      enabled: true
      register-expansion: true
      cache-duration-ms: 1000
      async-timeout-ms: 100

The expansion is internal and persistent; no eCloud download is required. cache-duration-ms accepts 0..5000, and async-timeout-ms accepts 10..1000. See PlaceholderAPI.

Public directory

public-protections:
  enabled: true
  default-visibility: "private"
  default-category: "other"
  allow-coowner-editing: false

New/existing protections remain private until their owner publishes them. The same section controls text limits, allowed icons, categories, search, favorites, visit counters, teleport warmup/cooldown and welcome-message cooldowns. See Public Directory.

Environment policies

The default environment policies are denied inside protections. Individual protections can inherit these defaults or override them from the Environment GUI. Boundary protection still prevents fire and explosions from crossing between a protection and the outside, or between different protections.

environment:
  enabled: true
  defaults:
    hostile-spawning: "deny"
    tnt-explosions: "deny"
    creeper-explosions: "deny"
    other-explosions: "deny"
    fire-spread: "deny"

enabled: false disables these internal flag decisions but does not disable the separate protection-boundary barriers. See Rules System.

Holograms

holograms:
  enabled: true
  default-enabled: true
  height: 1.8
  view-distance: 32
  line-width: 240
  lines:
    - "&bBienvenid@ a {title}"
    - "&7Dueño: &f{owner}"
    - "&8{x}, {y}, {z}"
    - "&7{description}"
  • enabled is the global switch.
  • default-enabled applies only when a protection's individual state is DEFAULT.
  • At most 12 lines are loaded, with at most 256 characters per line.
  • Height, view distance and line width are validated to safe ranges.

See Holograms for variables and behavior.

The default background panel is disabled while text shadow remains enabled. Existing custom holograms.lines values are preserved by the safe config updater.

The bundled config.yml documents the full native variable list above holograms.lines. It includes {title}/{name}, {owner} (protection owner), {user} (player viewing the hologram), {id}, {type}/{type_id}, {world}, {x}/{y}/{z}, {stone_x}/{stone_y}/ {stone_z}, {size_x}/{size_y}/{size_z}, {description}, {visibility}, {category} and {visits}. Hologram lines support legacy color/format codes, for example &bCasa.

The default lines above do not include {user} or PAPI tokens, so they use one shared display per protection. With PlaceholderAPI enabled, a line containing %expansion_placeholder% or native {user} activates private per-viewer rendering. PAPI values then use the viewer's context and refresh on movement or reload, without a repeating scan. See Holograms.

If a pre-existing custom line used {user} for the owner, replace it with {owner}. Custom holograms.lines are preserved and are not rewritten.

Category head textures

Set public-protections.categories.<id>.head-texture to a 64-character textures.minecraft.net hash. Invalid/blank values use the category's configured material. This does not require an external plugin or runtime catalogue request; see Public Directory.

Metrics

LederProtections embeds bStats (plugin ID 34348) for aggregate technical statistics. No custom player or protection metrics are added. To opt out, set enabled: false in the shared plugins/bStats/config.yml; this disables bStats for all plugins on that server.

Recommended workflow

  1. Stop or stage the server.
  2. Back up plugins/LederProtections/ and the world.
  3. Edit YAML with spaces, never tabs.
  4. Start the server or run /lep reload.
  5. Review validation warnings and run /lep check.
  6. Test creation, access rules, teleport and any enabled integrations.

1.5.0 upgrade / Actualización

  • gui-style moves to menus.yml with backups. Existing explicit menu values win.
  • The global actionbar section is removed. Notifications follow movement/teleport destinations immediately; personal notification preferences still work.
  • Detection-only hook toggles and old local pack URL/hash/profile settings are removed.
  • Nonempty legacy flags.profiles remain supported; empty defaults are removed.
  • LP includes no pack and sends no download prompt. External packs remain optional.
  • Invalid menu reloads keep the last valid layout/style. Do not replace a customized file wholesale just to update: inspect the generated backups and merge intentional changes.

Configuration Files contains the exact downloadable 1.5.0 defaults, examples and Spanish instructions. PlaceholderAPI cache/timeouts are advanced settings; normally leave them unchanged.

Clone this wiki locally