-
Notifications
You must be signed in to change notification settings - Fork 2
Other Settings Document
TRCStudioDean edited this page Jul 24, 2025
·
2 revisions
This is a configuration document about some other settings in the custom command configuration file, you can view a list of these settings and detailed setting specifications here.
- Description: Used to set JSON Components, using corresponding placeholders in various settings in this article can make them the corresponding JSON components. The JSON components set here will also be added to the plugin's JSON component list, meaning you can use this command to configure the JSON components set in the file anywhere.
- Specification:
#Note that component names cannot be duplicated!
JSON-Components:
[Component1]:
(Options...)
[Component2]:
(Options...)
...- Format:
[ComponentName]:
Placeholder: '[PlaceholderName]'
Text: '[DisplayText]'
#The content displayed when the mouse hovers over the text
HoverEvent:
#Available types: SHOW_TEXT, SHOW_ACHIEVEMENT, SHOW_ITEM, SHOW_ENTITY
# SHOW_TEXT: Display regular text
# SHOW_ACHIEVEMENT: Display achievement text
# SHOW_ITEM: Display item details
# SHOW_ENTITY: Display entity details
Action: SHOW_TEXT
Hover-Values:
- 'Example text'
ClickEvent:
#Available types: OPEN_URL, OPEN_FILE, RUN_COMMAND, SUGGEST_COMMAND, CHANGE_PAGE, COPY_TO_CLIPBOARD
# OPEN_URL: Click to open a URL link (for example: https://www.example.com/)
# OPEN_FILE: Click to open a file located in the local directory
# RUN_COMMAND: Click to run command
# SUGGEST_COMMAND: Click to fill the specified text into the input field
# CHANGE_PAGE: Click to change page (Book)
# COPY_TO_CLIPBOARD: Click to copy to clipboard
Action: RUN_COMMAND
Value: '/[ExampleCommand]'- Example:
JSON-Components:
'Help':
Placeholder: '%litecommandeditor_command_help%'
Text: '&a/litecommandeditor &6help'
ClickEvent:
Action: RUN_COMMAND
Value: '/litecommandeditor help'
HoverEvent:
Action: SHOW_TEXT
Hover-Values:
- '&bClick to view help'
- '&bUsage: &a/litecommandeditor &6help'-
Description: This option is used to manually create items with special parameters, making it convenient to directly use the NBT and other data of the item in the custom command configuration file.
Meanwhile, the command
/litecommandeditor itemcollectioncan also be used to serialize and save items in the game directly under this setting. - Specification:
#Basic setting specifications: (Note that item names cannot be duplicated!)
Item-Collection:
[Item1]:
(Options...)
[Item2]:
(Options...)
...- Format:
[ItemName]:
#Item's ID (Required)
Item: [ID]
#Item's data value (Optional)
#Commonly used in versions below 1.12, for example, the data value of the Golden Apple is 0, and the enchanted Golden Apple is 1
Data: [Value]
#Item's amount (Optional)
Amount: [Number]
#Item's display name (Optional)
Name: [Text]
#Item's lore (Optional)
Lores:
- [Text]
#Item's enchantments (Optional)
Enchantments:
- [EnchantmentName]: [Level]
#Item's attribute (Optional)
#Available types: HIDE_ENCHANTS, HIDE_ATTRIBUTES, HIDE_UNBREAKABLE, HIDE_DESTROYS, HIDE_PLACED_ON, HIDE_POTION_EFFECTS
Options:
- [AttributeName]
Unbreakable: [true/false]
#Custom model data (Optional)
Custom-Model-Data: [Number]
#Item model (Optional)
Item-Model: [Name] or [NamespacedKey]:[Name]
#Item's head owner (Optional)
#If this is a skull, you can fill in the name of its owner here
Head-Owner: [PlayerName]
#Item's head textures (Optional)
#If this is a skull, you can fill in the texture base64 value of its owner here
Head-Textures: [Base64Value] - Example:
Item-Collection:
'Example':
Item: DIAMOND
Amount: 64
Name: '&b&lSuper Diamond'
Lores:
- 'Example text'
Enchantments:
- 'MENDING': 1
Options:
- HIDE_UNBREAKABLE
Unbreakable: true
Custom-Model-Data: 1
Item-Model: minecraft:test
'Head':
Item: PLAYER_HEAD
Head-Owner: Steve
'Earth':
Item: PLAYER_HEAD
Head-Textures: 'eyJ0ZXh0dXJlcyI6eyJTS0lOIjp7InVybCI6Imh0dHA6Ly90ZXh0dXJlcy5taW5lY3JhZnQubmV0L3RleHR1cmUvZDdjYzY2ODc0MjNkMDU3MGQ1NTZhYzUzZTA2NzZjYjU2M2JiZGQ5NzE3Y2Q4MjY5YmRlYmVkNmY2ZDRlN2JmOCJ9fX0='