CHC | Custom Hit Command

CustomHitCommand: Unleash Dynamic Actions on Impact!












What is CHC?


Custom Hit Command let's you trigger specific commands every time you
hit an other player with a
chosen item group and/or a
single item(s) you marked before with /chc sethititem! This
lightweight and ️
highly customizable plugin is built for
Paper 1.21, ensuring
fast
performance and
seamless integration.



Key Features:

• Configurable Hit Item: Define which item group, single item, or external NBT tag triggers the action (e.g., all Iron Swords, marked Blaze Rods, or even plugins like DeluxeHub items via key=value)
  
  
• Dynamic Command Execution: Set any server command to run upon a successful hit. You can choose whether the command is executed by the attacking player or the console. Use the %hitted_player% placeholder to automatically insert the name of the player you hit (e.g., /duel %hitted_player%)

• Visual Hit Particles: Configure particle effects to appear at the location of the hitted player, adding a visually dynamic element to your commands

• Customizable Messages: Tailor nearly all plugin messages to match your server's style

• Enhanced Logging: An optional, enhanced logging system can be enabled to provide detailed debug information for troubleshooting

• Update Notifications: An automatic update checker can be configured to notify you in the console or directly in-game when a new version is available. It can be easily toggled on/off in the configuration

So what are you waiting for? Get Custom Hit Command now and bring a new layer of excitement to your server!

Commands & Permissions:
/chc reload | customhitcommand.reload
/chc sethititem | customhitcommand.sethititem
customhitcommand.update (for in-game update notifications)
customhitcommand.use (allows the use of the hit item (default true))
customhitcommand.admin (parent permission for all permissions)

Q&A:
Why is the compiled plugin (JAR file) larger than the source code on GitHub?
Our plugin includes dependencies like bStats as a dependency to gather anonymous usage statistics. When the plugin is compiled into a single JAR file, the bStats library (along with all its own dependencies) is packaged directly into the final plugin file. This process, called 'shading', makes the plugin self-contained which naturally increases the overall file size compared to just the raw source code.


Need Help?
Please, don't post bad ratings before asking for help! We're here to assist you.
If you encounter any problems, bugs, or have questions about the plugin, please don't hesitate to contact me directly or post in the plugin discussion section. I'll be happy to take a look and provide support! Your positive experience is our priority.