Add a /prime, which opens an gui where players can select the join messgae when they join and leave, and die. OPs can add messages and delete/edit them. Also do so staff can blacklist users from this if they abuse it
There are no projects in this workspace yet. Is this for an existing project you can add here, or should we create a new one? If new, should it be a Minecraft plugin or mod?
plugin
I’ve started building the plugin with /prime message selection, OP-managed message lists, and staff blacklist controls. I’ll verify the build once the implementation is finished.
I’ll create the plugin metadata and default messages, then add persistent selection/blacklist handling, /prime administration commands, and a click-safe GUI with join/quit/death event integration.Created the /prime system in eight files.
Players get a paginated GUI to choose join, quit, and death messages. Their choices are saved in
data.yml.Messages are configurable in
config.yml. Staff withprime.admincan add, edit, or delete them using/prime admin add|edit|delete; the default message cannot be deleted.Staff with
prime.staffcan use/prime blacklist <player>and/prime unblacklist <player>. Blacklisted players cannot open the GUI, and their events use the plugin’s standard messages.Added GUI click protection, tab completion, player feedback, and permissions that grant administrative access to OPs by default.
No build was attempted.
The PrimeMessageGUI plugin built successfully.
Players can use /prime to select join, quit, and death messages. Staff with prime.admin can manage message options, and staff with prime.staff can blacklist or unblacklist players. Options and selections persist in YAML files.
Do so it's supports Essentialsx
I’ve started adding optional EssentialsX compatibility so Prime’s selected join and quit messages continue to work alongside EssentialsX, without making EssentialsX a required dependency.
Declare Prime to load before the optional
Essentialsplugin, without requiring it.Run Prime’s join and quit message handlers at
HIGHESTso selected messages take precedence over EssentialsX’s event changes.Leave death handling, selection, blacklist behavior, and commands unchanged.Updated
plugin.ymlandPrimeListener.java.
Prime now declares loadbefore: Essentials, which keeps the ordering optional: Prime works without EssentialsX, and does not add an EssentialsX dependency. Its join and quit handlers now run at HIGHEST, so Prime’s selected messages override EssentialsX’s earlier event changes. Death messages, selection, blacklists, and commands are unchanged.
No build was attempted.
EssentialsX compatibility is in place, and the plugin builds successfully. Prime loads before the optional Essentials plugin and applies selected join/quit messages at highest event priority. EssentialsX is not required; Prime remains functional without it.
No files in this session