Format Gradient

🎨 Gradient Configuration Guide

This section explains how to define gradients in your menu, using either the basic or advanced format. Gradients allow you to create visually appealing colored text and items with optional requirements for unlocking them.

---

🔹 Basic Format

The basic format is simple and requires only the essential fields. You can use it to quickly set up a gradient display.

colors:
  - id: 1
    display_name: ⬛⬛⬛⬛⬛⬛⬛⬛⬛
    gradient: true
    permission: gradient.name
    patterns:
      - '#F2709C'
      - '#FF5733'
    style:
      - "STRIKETHROUGH"

Basic Field Descriptions:

• id: A unique identifier for this color/gradient entry.

• display_name: The text shown in the GUI. You can use placeholders like %player_name% or symbols.

• gradient: Set to true to apply a gradient effect to the display_name.

• permission: The permission required to unlock this gradient. Use none for free access.

• patterns: List of hexadecimal colors (e.g., #F2709C) that define the gradient.

• style: Optional. You can apply chat styles like BOLD, ITALIC, UNDERLINE, or STRIKETHROUGH.

---

⚙️ Advanced Format

Use this format to customize item visuals further with materials, glowing effects, model data, amount, and hidden attributes.

colors:
  - id: 1
    display_name: ⬛⬛⬛⬛⬛⬛⬛⬛⬛
    gradient: true
    permission: gradient.name
    material: BEDROCK
    glowing: true
    model_data: 0
    hide_attributes: true
    amount: 3
    patterns:
      - '#F2709C'
    style:
      - "STRIKETHROUGH"

Additional Fields:

• material: Sets the item material (e.g., BEDROCK).

• glowing: Makes the item glow if true.

• model_data: Custom model data ID for resource pack support.

• hide_attributes: Hides attributes like damage or armor.

• amount: Sets the item amount shown in the menu.

---

✅ Requirements (requirements) System

You can use the requirements section to make gradients unlockable only when specific conditions are met. This feature supports any PlaceholderAPI value (e.g., money, playtime, level).

📐 Requirements Structure

requirements:
  - placeholder: "%placeholder%"
    condition: "comparison"
    value: "expected_value"
    success: "✔ Message if requirement is met"
    fail: "✖ Message if requirement is not met"

🔑 Field Explanation:

• placeholder: Any valid PlaceholderAPI value.

  • Examples:

    • %vault_eco_balance% → player balance

    • %statistic_hours_played% → hours played

    • %player_level% → experience level

• condition: The logic for comparing values. Numerical Operators: >=, >, <=, <, ==, != Text Operators: =, !=, <- (contains), |- (starts with), -| (ends with)

• value: The value to compare against the placeholder result.

• success: Message shown in the item lore if the condition is met.

• fail: Message shown if the condition is not met.

---

💡 Example with Multiple Requirements

requirements:
  - placeholder: "%vault_eco_balance%"
    condition: ">="
    value: "1000"
    success: "#4FFD4A ✔ Enough money. &7[Completed]"
    fail: "#FC3A3A ✖ You need at least $1000. &7[Not Completed]"

  - placeholder: "%statistic_hours_played%"
    condition: ">="
    value: "5"
    success: "#4FFD4A ✔ Enough playtime. &7[Completed]"
    fail: "#FC3A3A ✖ You need to play at least 5 hours. &7[Not Completed]"

The gradient will only be available to players with at least $1000 and 5 hours of playtime.

---

🧠 Tips

• Make sure to install PlaceholderAPI and the required expansions (/papi ecloud).

• You can stack multiple conditions to create exclusive or achievement-based gradients.

• Use emojis and color codes to make lore messages more engaging.