# Changelog ## Version 1.2 ### New Features #### Combat Restrictions System A comprehensive system to restrict items and abilities while players are in combat: - **Trident (Riptide) Restrictions** - Option to fully disable tridents with Riptide enchantment during combat - Configurable cooldown for tridents when not fully disabled - Velocity reduction as backup prevention if riptide somehow triggers while disabled - **Elytra Restrictions** - Option to disable elytra gliding while in combat - Players cannot start gliding, but won't be forcefully unglided mid-flight - **Ender Pearl Restrictions** - Option to fully disable ender pearls during combat - Configurable cooldown for pearls when not fully disabled - Uses native Minecraft cooldown indicator in hotbar - **Firework Rocket Restrictions** - Option to fully disable firework rockets (elytra boosting) during combat - Configurable cooldown for fireworks when not fully disabled - Uses Paper's PlayerElytraBoostEvent for accurate detection #### Native Cooldown Indicators - All item cooldowns now display using Minecraft's native cooldown animation in the hotbar - Disabled items show a persistent cooldown that refreshes while in combat - Cooldowns are automatically cleared when leaving combat #### Dynamic Config Updates - Config changes now apply immediately to players already in combat - Re-enabling an item mid-combat clears the disabled cooldown - Disabling an item mid-combat applies the cooldown immediately ### New Config Options ```yaml # Disable tridents (Riptide) while in combat disable-tridents: true # Cooldown for tridents while in combat (seconds, 0 = no cooldown) # Only applies if disable-tridents is false trident-cooldown: 10 # Disable elytras while in combat disable-elytras: true # Disable ender pearls while in combat disable-pearls: false # Cooldown for pearls while in combat (seconds, 0 = no cooldown) # Only applies if disable-pearls is false pearl-cooldown: 10 # Disable firework rockets while in combat disable-fireworks: false # Cooldown for fireworks while in combat (seconds, 0 = no cooldown) # Only applies if disable-fireworks is false firework-cooldown: 10 ``` ### Bug Fixes - Fixed trident blocking where holding right-click would eventually allow riptide - Fixed ender pearl cooldown not applying after throwing - Fixed firework rockets not propelling players when cooldown was enabled - Fixed cooldowns not clearing when items were re-enabled mid-combat - Fixed cooldowns not applying when items were disabled mid-combat --- ## Version 1.1 ### New Features #### Ally System - Players can now add allies who won't trigger combat when nearby - `/ally add <player>` - Send an ally invite to another player - `/ally remove <player>` - Remove a player from your allies - `/ally list` - View your current allies - `/ally accept <player>` - Accept a pending ally invite - `/ally deny <player>` - Deny a pending ally invite - Configurable maximum number of allies per player - Ally invites expire after configurable duration - Mutual ally system - both players must accept to become allies ### Bug Fixes - Fixed various command handling issues - Improved combat detection reliability - Fixed edge cases with player disconnection during combat --- ## Version 1.0 ### Initial Release - Proximity-based combat detection system - Combat timer with action bar display - Zombie log system for combat logging - Configurable radius, timer duration, and death type - Admin commands for managing combat state

# ⚔️ Danger Log > **Combat logging protection for Minecraft Paper 1.21+ servers** --- ## 📖 Overview **Danger Log** is a powerful combat logging protection plugin that prevents players from escaping PvP situations by disconnecting. When a player logs out during combat, a zombie NPC spawns in their place — if the zombie dies, so does the player! --- ## ✨ Features ### 🎯 **Combat Timer System** - Players within a configurable radius receive a combat timer in their action bar - Timer displays as `20/20` and stays at max while enemies are nearby - Timer counts down when players leave combat range - Logging out with an active timer = **combat logging** ### 🧟 **Combat Log Protection** | Mode | Description | |------|-------------| | **ZOMBIE** | Spawns a zombie NPC with the player's name. If killed, drops all loot. | | **INSTANT** | Immediately kills the player upon combat logging. | ### 🤝 **Ally System** - Team up with friends to avoid triggering each other's combat timers - Clickable invite system with expiration - Configurable max allies per player ### 💾 **Persistence** - Zombies survive server restarts - Player inventories are safely stored - All data saved to files ### 🎮 **Smart Detection** - Only affects **Survival** mode players - Creative, Spectator, and Adventure players are ignored - Bypass permission available for staff --- ## 📋 Commands ### 🔧 Admin Commands *Requires `dangerlog.admin` permission (default: OP)* | Command | Description | |:--------|:------------| | `/dangerlog on` | Enable the plugin | | `/dangerlog off` | Disable the plugin | | `/dangerlog reload` | Reload configuration | ### 👥 Ally Commands *Available to all players* | Command | Description | |:--------|:------------| | `/ally invite <player>` | Send an ally request | | `/ally accept [player]` | Accept a pending invite | | `/ally remove <player>` | Remove an ally | | `/ally list` | View your allies | --- ## 🔑 Permissions | Permission | Description | Default | |:-----------|:------------|:--------| | `dangerlog.admin` | Access admin commands | **OP** | | `dangerlog.bypass` | Bypass combat log system | **false** | --- ## ⚙️ Configuration ```yaml # =========================================== # DANGER LOG CONFIGURATION # =========================================== # Combat detection radius (in blocks) radius: 30 # Combat timer duration (seconds) timer-duration: 20 # ------ DEATH TYPE ------ # ZOMBIE = Spawns NPC zombie # INSTANT = Kills player immediately death-type: ZOMBIE # ------ ZOMBIE SETTINGS ------ # How long before zombie auto-expires (-1 or 0 = never) # Minimum: 10 seconds zombie-log-timer-max: -1 # ------ ALLY SYSTEM ------ # Enable/disable allies allow-allies: true # Max allies per player (-1 or 0 = unlimited) max-allies: 6 # Ally invite duration (seconds) invite-duration: 120 # ------ GENERAL ------ # Plugin enabled state enabled: true ``` --- ## 🎬 How It Works ``` 1️⃣ Two players enter combat range (30 blocks) ↓ 2️⃣ Both see combat timer: [20/20] ↓ 3️⃣ Timer stays at max while in range ↓ 4️⃣ Player leaves range → timer counts down ↓ 5️⃣ Player logs out with active timer ↓ ┌─────────────────────────────────────┐ │ ⚠️ COMBAT LOG DETECTED! │ │ Zombie spawns at logout location │ │ Chat: "Player has logged out in │ │ combat." │ └─────────────────────────────────────┘ ↓ 6️⃣ If zombie is killed → loot drops ↓ 7️⃣ Player rejoins → DEATH SCREEN ``` --- ## 🧟 Zombie NPC Details | Property | Value | |:---------|:------| | **Name** | Player's name (bold red) | | **AI** | Disabled | | **Burns in Sun** | No | | **Health** | Same as player at logout | | **Drops** | Player's full inventory | | **Despawns** | Never (unless configured) | --- ## 📁 Data Files | File | Purpose | |:-----|:--------| | `config.yml` | Plugin configuration | | `allies.yml` | Stored ally relationships | | `zombies.yml` | Active combat log zombies | --- ## 💡 Tips - **For SMP servers:** Set `zombie-log-timer-max` to `-1` so zombies stay forever - **For minigames:** Use `INSTANT` death-type for immediate punishment - **For teams:** Enable allies with a reasonable `max-allies` limit - **For staff:** Give `dangerlog.bypass` permission to moderators --- ## 📞 Support Having issues? Contact the developer! --- **Made with ❤️ by CrystalPT**