This plugin is available for 1.8 to the current MC version. If it does not work on any version, please contact the author for support.
Below is an example of what you can do with ACT
(Plugin does not include the modified chat box)
Custom Placeholders are ACT's way of splitting a chat format into parts. In each custom placeholder, you can have your own range of possible values like any placeholder, and you can have your own hover and click events.
(Plugin does not include the modified chat box)
You can use normal placeholders both inside and outside of custom placeholders, but you can't use custom placeholders inside another custom placeholder (due to possible looping).
You can identify the difference between a custom placeholder and a normal placeholder through the surrounding characters of it. A custom placeholder uses {} (curly brackets) to identify itself, and a normal placeholder uses %% (parentheses).
ACT Comes with two normal placeholders to start with, but it can be extended through the use of PlaceholderAPI. The two placeholders being %message% and %player_name%.
The default chat format has three custom placeholders in it. Those being a prefix, suffix, and colored name. The prefix and suffix are simply custom placeholders to identify rank, but the colored name can be used for cosmetic name coloring. A normal player only gets a grey name, while a donator can have red, green, or blue. (In the default config).
This can be customized however you like to be anything you could ever want. If you need help, you can contact the developer for any configuration help, however, be sure to include the files you want help with.
Below is an example of what you can do with Custom Placeholders.
To make a custom placeholder, all you need to do is copy and paste
an existing custom placeholderand then edit the values accordingly.
Here is a small guide on what certain values mean:
Here is a small guide on what certain values mean:
Spoiler
Here is a small sample of a custom placeholder.
prefix:
independentTextComponent : true
normal:
priority : 1
perm : act.prefix.normal
value : '&7 [N ]'
useGroupEvents : false
hoverText : '&7Click here to message the player.'
suggestCmd : '/msg %player_name% '
Let's go through this line by line.
The first one ("prefix:") is the id of the custom placeholder.
This is what you put in the curly brackets when you want to use it. (like this: " {prefix} ")
The "independentTextComponent" value is for if you want the custom placeholder to affect items outside of it. Basically, if you have a color in the custom placeholder, and you set this value to false, the color will affect text outside of the custom placeholder. Also note that it will not have the ability for hover and click events.
The "normal:" is a value for the custom placeholder. Whenever a custom placeholder is parsed, you might put something where the custom placeholder was.
If the player has the permission (specified in the "perm" value), then the custom placeholder will be set to the value in "value:"
However, if the player has another custom placeholder with a higher priority (in the "priority" value), then that will override if that have that permission.
Basically, as long as you set the perm to be the permission required for the value, and the priority increments (1 to 2 to 3 etc), then you should be okay. If you need help, fell free to contact the developer.
Now for the last 3. The "useGroupEvents" specifies if the custom placeholder should use the chat events (click and hover), that is used in the group. If "true" then it will override whatever events are set for the custom placeholder with the events that is set for the group. If "false" then it will set the events to be the next to values.
The "hoverText" value is text shown whenever the message is hovered over.
The "suggestCmd" is the text used whenever the player clicks the message. It will put the text into the chat box automatically. (but not automatically ran).
Code (YAML):
prefix:
independentTextComponent : true
normal:
priority : 1
perm : act.prefix.normal
value : '&7 [N ]'
useGroupEvents : false
hoverText : '&7Click here to message the player.'
suggestCmd : '/msg %player_name% '
The first one ("prefix:") is the id of the custom placeholder.
This is what you put in the curly brackets when you want to use it. (like this: " {prefix} ")
The "independentTextComponent" value is for if you want the custom placeholder to affect items outside of it. Basically, if you have a color in the custom placeholder, and you set this value to false, the color will affect text outside of the custom placeholder. Also note that it will not have the ability for hover and click events.
The "normal:" is a value for the custom placeholder. Whenever a custom placeholder is parsed, you might put something where the custom placeholder was.
If the player has the permission (specified in the "perm" value), then the custom placeholder will be set to the value in "value:"
However, if the player has another custom placeholder with a higher priority (in the "priority" value), then that will override if that have that permission.
Basically, as long as you set the perm to be the permission required for the value, and the priority increments (1 to 2 to 3 etc), then you should be okay. If you need help, fell free to contact the developer.
Now for the last 3. The "useGroupEvents" specifies if the custom placeholder should use the chat events (click and hover), that is used in the group. If "true" then it will override whatever events are set for the custom placeholder with the events that is set for the group. If "false" then it will set the events to be the next to values.
The "hoverText" value is text shown whenever the message is hovered over.
The "suggestCmd" is the text used whenever the player clicks the message. It will put the text into the chat box automatically. (but not automatically ran).
There are a few extra commands that I added such as:
/mutechat
/slowchat
/clearchat
They are all configurable in the configuration
The main command is /act.
/act reload - Reloads the configuration and all player info
/act reload <player name> - Reloads a specific player's group
/act <command> - Executes like any other command above, just in case you have a plugin overriding that one. (eg: /act slowchat)
(ChatControl has some of these, but they are sub-cmds)
It is recommended that you use this alongside
Placeholder API and ChatControl.
ChatControl allows for the MANY normal features of a chat plugin all in one including anti spam, anti cap, announcer, etc.
Placeholder API allows for the placeholder integration between plugins for prison ranks, pex groups, and more.
(Neither plugin is required for this plugin to function.)
If you want a GUI to choose between permissions that can be bound to custom placeholders (prefixes,etc),
try out my other plugin, GUI Perms.
I would recommend to get DeluxeChat or ChatControlPro if this does not suit your needs.
Support can be found through Direct Messaging me on Spigot.
Quick facts
- Edition: Minecraft Java
- File type: .jar
- Minecraft versions listed: 1.8, 1.12, 1.15
- How to install: Install the matching mod loader (Forge, Fabric or NeoForge) for your Minecraft version. → Download the .jar. → Put it in the .minecraft/mods folder and launch that loader profile.
- Where to get it: Opens on Spigot — not every file is mirrored on our own servers.
Install steps are the general flow for this file type — How to install Minecraft Java mods & modpacks walks through it step by step.
AdvancedChatTorch - Advanced JSON Chat Formatting - FREE is a free Minecraft Java mod. Compatible with Minecraft 1.8, 1.12, 1.15. Downloaded 5,618 times (via Spigot). Download it and open it directly in the game.