Commands & Permissions

🧾 Commands & Permissions

📘 Introduction

This page provides a complete list of all commands and their associated permissions for the NameGradient plugin.

Commands are split into two categories:

• Player Commands – for regular users.

• Admin Commands – for staff or server operators.

---

🎮 Player Commands

Command	Description	Permission Node
/gradient	Opens the main gradient menu.	namegradient.open

---

---

🛠️ Admin Commands

Command	Description	Permission Node
/namegradient help	View help message	namegradient.help
/namegradient info [player]	Check a player's information	namegradient.info
/namegradient reload	With this command you can reload the configuration files.	namegradient.reload
/namegradient remove (type) [player]	Remove specific player data	namegradient.remove
/namegradient removeall (player)	Completely eliminate a player.	namegradient.removeall
/namegradient set (type) [player] {ID} [Optional Styles]	Set a gradient to an online or offline player	namegradient.set
/namegradient transfer (type) [From] [To]	Transfer data from one player to another	namegradient.transfer
/namegradient openmenu [player] [Type]	Allows you to open menus to connected players.	namegradient.open
/namegradient export (value)	Exports the data stored in the database in a json file.	namegradient.export
/namegradient import (value)	Import the json file that is generated when exporting.	namegradient.import

​

---

📂 Custom Menu Commands

These commands allow direct access to specific plugin menus through configurable commands. You can enable or disable each command, define aliases, set permissions, and choose which menu to open.

Each custom command is defined in the custom-commands section of the config file.

🔧 Configuration Example

custom-commands:
  chat-gradient:
    enabled: true
    name: chatcolor
    aliases:
      - "ccolor"
      - "chatg"
    permission: gradient.chat.open
    open-menu: "gradientchat"

🧩 Explanation of Fields

• enabled: Whether the command is active (true or false).

• name: The actual command players will use (e.g. /chatcolor).

• aliases: Optional alternative names (e.g. /ccolor, /chatg).

• permission: The permission node required to execute the command.

• open-menu: The ID of the menu to open. Options: main, gradientchat, gradientname, history.

✅ Example

With the configuration above, a player with the gradient.chat.open permission can open the Chat Gradient Menu by using:

/chatcolor
/ccolor
/chatg

📋 Field Summary Table

Field	Type	Description
enabled	Boolean	Enables or disables the custom command.
name	String	Main command name players will use.
aliases	List	Alternative command names players can use.
permission	String	Required permission node for the player to use the command.
open-menu	String	ID of the menu to open. Valid values: main, gradientchat, gradientname, history.

---

🕘 History Permissions

The history menu displays previously used gradients. To control how many entries a player can view, use the permission format:

namegradient.history.amount.<number>

Where <number> is the maximum number of entries the player can see.

The plugin will check for an exact permission match, and if not found, it will look for the next highest available value, up to 28, which is the hard limit of the menu.

✅ Example Permissions

Permission	Description
namegradient.history.amount.3	Allows viewing up to 3 previous gradients.
namegradient.history.amount.10	Allows viewing up to 10 previous gradients.
namegradient.history.amount.28	Allows viewing the full history (28 items).

ℹ️ If the player does not have any permissions, the downgrades will not be stored.