⚙️ Configuration

⚙️ Configuration

vLives is highly configurable through three main files located in your /plugins/vLives/ folder.

config.yml

This is the main configuration file for core plugin mechanics.

YAML

# The number of lives a player starts with on their first join.
starting-lives: 5

# The maximum number of lives a player can have. Set to -1 to disable the limit.
max-lives: 10

# The duration of the ban when a player runs out of lives.
# Format: <number><s/m/h/d> for seconds, minutes, hours, or days.
ban-duration: "12h" # 12 hours

# If true, players who run out of lives are teleported to a set location instead of being banned.
# You must set the location with /lives setbanlocation
server-ban-area: true

# A list of commands that banned players are still allowed to use.
# Must include the initial slash.
command-whitelist-for-banned:
  - "/login"
  - "/register"
  - "/helpop"

boosters.yml

This file allows you to create an unlimited number of custom boosters.

YAML

# This file contains all booster definitions for the vLives plugin.
boosters:
  # This is the unique ID for the booster. Used in /lives booster give
  life_save_50:
    # PERSONAL or GLOBAL
    type: PERSONAL
    # Duration in seconds. -1 for single-use/permanent.
    duration: 1800 
    # Contains the booster's effects. The key name (e.g., "chance") defines the effect.
    effect:
      # chance: Chance (0.0 to 1.0) to not lose a life on any death.
      chance: 0.5 
    # The item representation of the booster.
    item:
      name: "&bBooster: Angel's Grace (30m)"
      material: "FEATHER"
      glow: true
      lore:
        - "&7Grants you a 50% chance to"
        - "&7not lose a life upon death."
      # This NBT tag is crucial for the plugin to identify the item.
      nbt:
        vives_booster_id: "string:life_save_50"

  double_lives_kill:
    type: GLOBAL
    duration: 3600
    effect:
      # multiplier: Multiplies the base lives gained on a PvP kill.
      multiplier: 2.0
    item:
      name: "&cGlobal Booster: Bloodlust (1h)"
      material: "NETHER_STAR"
      # ...
      nbt:
        vives_booster_id: "string:double_lives_kill"

messages.yml

This file (or one with a similar name) controls every message sent by the plugin. All messages support standard Minecraft color codes (&a, &l, etc.) and a variety of placeholders.

---

💎 Item Creation

You can create incredibly detailed items in your boosters.yml file using the item section. This system supports a wide range of properties.

Example of a Complex Item

This example shows a player head item with a custom name, lore, enchantments, flags, and NBT data.

YAML

boosters:
  super_booster:
    type: PERSONAL
    duration: 600
    effect:
      chance: 1.0
    item:
      # The material, using official Bukkit Material names.
      material: "PLAYER_HEAD"
      # The display name of the item. Supports color codes.
      name: "&d&lSuper Booster of Life Saving"
      # The amount of items to give.
      amount: 1
      # The lore of the item. Each line is an element in the list.
      lore:
        - "&7This is a very powerful booster."
        - "&eGuarantees you will not lose a life"
        - "&eon your next death."
      # Makes the item glow as if enchanted.
      glow: true
      # Hides default text like "Unbreakable" or enchantments.
      flags:
        - "HIDE_ENCHANTS"
        - "HIDE_UNBREAKABLE"
      # Makes the item unbreakable.
      unbreakable: true
      # For player heads, this uses the skin of the specified player.
      # You can also use the %player% placeholder here in certain contexts.
      skull-owner: "Notch"
      # The NBT tag used to identify this as a booster.
      nbt:
        vives_booster_id: "string:super_booster"

---

📜 Permissions

Control access to vLives features with these permission nodes.

Permission Node	Description	Default
vLives.user	Grants access to basic player commands like /lives and /lives history.	All Players
vLives.admin	Grants access to all administrative commands.	OP Only

Exporter vers Sheets

Suggestion: For more fine-grained control, you can use a permissions plugin to grant specific admin commands, such as vLives.reload or vLives.booster.give.⚙️ Configuration

vLives is highly configurable through three main files located in your /plugins/vLives/ folder.

config.yml

This is the main configuration file for core plugin mechanics.

YAML

# The number of lives a player starts with on their first join.
starting-lives: 5

# The maximum number of lives a player can have. Set to -1 to disable the limit.
max-lives: 10

# The duration of the ban when a player runs out of lives.
# Format: <number><s/m/h/d> for seconds, minutes, hours, or days.
ban-duration: "12h" # 12 hours

# If true, players who run out of lives are teleported to a set location instead of being banned.
# You must set the location with /lives setbanlocation
server-ban-area: true

# A list of commands that banned players are still allowed to use.
# Must include the initial slash.
command-whitelist-for-banned:
  - "/login"
  - "/register"
  - "/helpop"

boosters.yml

This file allows you to create an unlimited number of custom boosters.

YAML

# This file contains all booster definitions for the vLives plugin.
boosters:
  # This is the unique ID for the booster. Used in /lives booster give
  life_save_50:
    # PERSONAL or GLOBAL
    type: PERSONAL
    # Duration in seconds. -1 for single-use/permanent.
    duration: 1800 
    # Contains the booster's effects. The key name (e.g., "chance") defines the effect.
    effect:
      # chance: Chance (0.0 to 1.0) to not lose a life on any death.
      chance: 0.5 
    # The item representation of the booster.
    item:
      name: "&bBooster: Angel's Grace (30m)"
      material: "FEATHER"
      glow: true
      lore:
        - "&7Grants you a 50% chance to"
        - "&7not lose a life upon death."
      # This NBT tag is crucial for the plugin to identify the item.
      nbt:
        vives_booster_id: "string:life_save_50"

  double_lives_kill:
    type: GLOBAL
    duration: 3600
    effect:
      # multiplier: Multiplies the base lives gained on a PvP kill.
      multiplier: 2.0
    item:
      name: "&cGlobal Booster: Bloodlust (1h)"
      material: "NETHER_STAR"
      # ...
      nbt:
        vives_booster_id: "string:double_lives_kill"

messages.yml

This file (or one with a similar name) controls every message sent by the plugin. All messages support standard Minecraft color codes (&a, &l, etc.) and a variety of placeholders.

---

💎 Item Creation

You can create incredibly detailed items in your boosters.yml file using the item section. This system supports a wide range of properties.

Example of a Complex Item

This example shows a player head item with a custom name, lore, enchantments, flags, and NBT data.

YAML

boosters:
  super_booster:
    type: PERSONAL
    duration: 600
    effect:
      chance: 1.0
    item:
      # The material, using official Bukkit Material names.
      material: "PLAYER_HEAD"
      # The display name of the item. Supports color codes.
      name: "&d&lSuper Booster of Life Saving"
      # The amount of items to give.
      amount: 1
      # The lore of the item. Each line is an element in the list.
      lore:
        - "&7This is a very powerful booster."
        - "&eGuarantees you will not lose a life"
        - "&eon your next death."
      # Makes the item glow as if enchanted.
      glow: true
      # Hides default text like "Unbreakable" or enchantments.
      flags:
        - "HIDE_ENCHANTS"
        - "HIDE_UNBREAKABLE"
      # Makes the item unbreakable.
      unbreakable: true
      # For player heads, this uses the skin of the specified player.
      # You can also use the %player% placeholder here in certain contexts.
      skull-owner: "Notch"
      # The NBT tag used to identify this as a booster.
      nbt:
        vives_booster_id: "string:super_booster"

---

📜 Permissions

Control access to vLives features with these permission nodes.

Permission Node	Description	Default
vLives.user	Grants access to basic player commands like /lives and /lives history.	All Players
vLives.admin	Grants access to all administrative commands.	OP Only