
Quizy Combat Log
QuizyCombatLog: A powerful yet lightweight combat logging solution that prevents unfair PvP disconnects. Features multi-combat tracking, customizable timers, inventory protection, and sleek action bar displays to enhance your server's PvP experience.
2.0
Compatibility
Changes
🗡️ QuizyCombatLog
📝 Description
QuizyCombatLog is a powerful and lightweight combat logging plugin that prevents players from logging out during PvP combat. With customizable features and messages, it helps maintain fair play on your server.
⚡ Features
• Multi-combat system (tracks multiple opponents) • Customizable combat duration • Configurable inventory drop system • Action bar timer display • Command blocking during combat • Configurable unblocked commands • Custom messages with color support • Death handling system • Combat log punishment system
🛠️ Commands
/qcl help - Shows help menu
/qcl reload - Reloads the plugin configuration
/qcl combattime <seconds> - Sets combat timer duration
/qcl inventorydrop <true/false> - Toggles inventory drop on combat log
🔧 Configuration
# Combat Configuration
combat:
# Duration of combat tag in seconds
duration: 10
# Whether to drop player's inventory when they combat log
inventory-drop: true
# List of commands that can be used during combat
unblocked-commands:
- "show"
- "123"
- "qcl"
- "help"
# Custom Messages Configuration
messages:
combat-started: "&4&l⚔ &8» &7You have entered &d&lcombat&7! &8(&7Do not log out&8)"
combat-ended: "&2&l✔ &8» &7You are no longer in &dcombat&7!"
command-blocked: "&4&l✖ &8» &7Commands are &ddisabled &7during combat!"
player-combat-logged: "&4&l☠ &8» &d{player} &7has combat logged!"
# Action Bar Configuration
actionbar:
format: "&d&lCOMBAT &8» &f{time}s"
🎯 Features Explained
1️⃣ Multi-Combat System
- Tracks multiple combat opponents simultaneously
- Independent timers for each combat engagement
- Shows lowest remaining time in action bar
2️⃣ Inventory Protection
- Configurable inventory drop system
- Option to keep inventory on combat log
- Prevents item loss when protection is enabled
3️⃣ Command Management
- Blocks commands during combat
- Configurable whitelist for allowed commands
- Prevents teleportation and escape commands
4️⃣ Visual Feedback
- Action bar timer display
- Custom color-coded messages
- Combat status notifications
📋 Permissions
quizycombatlog.admin:
description: Allows access to admin commands
default: op
quizycombatlog.reload:
description: Allows reloading the plugin
default: op
🚀 Installation
- Download the plugin
- Place in your plugins folder
- Restart the server
- Configure in config.yml
- Reload if needed
⚙️ Default Configuration
The plugin comes with a balanced default configuration suitable for most servers. All settings can be customized in the config.yml file.
🔍 Support
For support, bug reports, or feature requests: • Join our Discord: [Your Discord Link] • Create an issue on GitHub: [Your GitHub Link]
📝 Notes
- Compatible with Spigot 1.8+
- Lightweight and optimized
- Regular updates and support
- No dependencies required
🎮 Usage Example
When a player enters combat:
- Combat timer starts
- Action bar shows remaining time
- Blocked commands are disabled
- Combat ends when timer expires or player dies
- If player logs out during combat:
- Inventory drops (if enabled)
- Death occurs (if enabled)
- Server broadcast message
💡 Tips
- Configure unblocked commands based on your server's needs
- Adjust combat duration for balanced gameplay
- Customize messages to match your server's theme
- Use color codes for better visibility
🔄 Updates
Stay tuned for regular updates and new features!
JOIN DISCORD
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:l0a93yFd:DANuI2vx"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:l0a93yFd:DANuI2vx"
}
