GodPowers

GodPowers introduces a dynamic PvP progression system where killing players rewards survivors with temporary potion effects, immunities, and visual effects.

Core Progression

• Stage Progression: Each player kill increments your kills counter. Your stage is calculated as: stage = min(max-stage, floor(kills / kills-per-stage)).
• Abilities per Stage:
  • Potion Effects: Configure custom potion effects (e.g., speed, strength, resistance, regeneration) per stage.
  • Lava & Fire Immunity: Cancel lava and fire damage.
  • Fire Ring: Renders a ring of flame particles that ignites nearby enemies.
• Power Decay: Every set interval, active players with kills lose one stage's worth of kills, or reset to 0 (based on configuration).
• Death Reset: Dying resets the player's stage and kills to 0 if reset-on-death is enabled.
• Combat-Log Guard: PvP damage tags both players for a configurable duration. Logging out while tagged inflicts death, dropping loot and crediting the killer.
• Action Bar Indicator: Shows the player's current stage with a custom prefix (⚡ God Power — Stage N) when stage > 0.
• Persistent Storage: Saves player statistics directly to the player's PersistentDataContainer (PDC). Survives server restarts and requires no database.

Commands support full tab-completion:

| Command | Permission | Description |
|---|---|---|
| /gp stats | None | Shows your own kills and stage. |
| /gp stats <player> | godpowers.admin | Shows another online player's stats. |
| /gp reload | godpowers.admin | Reloads config.yml (changes to tasks schedule require restart). |

Custom Configuration (config.yml)

Configure the kills per stage, maximum stage, decay tasks, combat logging, and effect profiles:

# Example settings from GodPowers
kills-per-stage: 5
max-stage: 5
reset-on-death: true

decay:
  interval-seconds: 300
  reset-completely: false

combat:
  tag-duration-seconds: 15
  punish: KILL

Installation

1. Download the GodPowers.jar file.
2. Place it in your server's plugins/ folder.
3. Start the server once to generate the default config.yml.
4. Edit the configuration file to your liking, then run /gp reload.

Requirements

• Paper 1.21.1+ (API 26.1.2 or newer)
• Java 25 or newer