⚔️ 1tk v1.0.0

1tk is a lightweight one-tap kill troll plugin for Bukkit, Spigot, Paper, and Purpur servers. Give selected players the ability to instantly kill allowed mobs or players with a normal melee hit.

Troll Plugin: 1tk is made for playful server trolling, staff jokes, and private/friends-only chaos.

Note: Player toggle data is stored separately in plugins/1tk/players.yml. The config.yml file is only for plugin settings.

⚠️ Version Compatibility Notice

One JAR for supported servers. 1tk uses the classic Bukkit plugin API and avoids Paper-only plugin loading features for broader compatibility (bugs may appear though).

🚧 Development & Support

1tk is currently in active development. More quality-of-life options, command polish, and configuration features may be added in future updates. (Source code will be published later)

For support, bug reports, or feature ideas, join the Discord Server.

🛑 Prerequisites

• Bukkit-family server: Built against Spigot API 1.8.8-R0.1-SNAPSHOT.
• Java 8+: The plugin compiles to Java 8 bytecode for wider server compatibility.
• Operator or permission access: Admin commands require 1tk.command.

🚀 Features

• ⚔️ One-Tap Toggle: Enable or disable one-tap kill for one player or every online player.
• 🛡️ Immune Players: Protect specific players from being one-tapped.
• 💾 UUID Storage: Saves enabled and immune players by UUID in players.yml.
• 🎛️ Configurable Rules: Decide which game mode combinations can one-tap players or mobs.
• 💬 Configurable Death Messages: Replace vanilla one-tap player death messages to avoid duplicate chat lines.
• 🐺 Vanilla Mob Deaths: Mobs keep their normal Minecraft death messages.
• 🔄 Live Reload: Use /1tk reload to reload config.yml and players.yml without restarting.
• 📡 Status Command: Use /1tk status to check version, update status, rules, and stored player counts.
• ⌨️ Smart Tab Completion: Suggests subcommands, players, *, true, and false.

📋 Commands & Permissions

Legacy command: /1tk <player|*> <true|false> still works, but /1tk toggle ... is preferred.

⚙️ Configuration (config.yml)

# 1tk configuration
#
# Player toggle state is stored separately in plugins/1tk/players.yml.

# Check for future plugin updates from Obsyron.
# Set enabled to false if you do not want 1tk to contact the update URL.
updates:
  enabled: true
  notify-ops-on-join: true

# One-tap rules. These only apply to players who have one-tap enabled.
# Immune players in plugins/1tk/players.yml cannot be one-tapped.
rules:
  survival-can-kill-survival-players: true
  creative-can-kill-survival-players: true
  survival-can-kill-mobs: true
  creative-can-kill-mobs: true

# Replaces one-tap death messages.
# Vanilla one-tap player death messages are suppressed first so they do not appear twice.
# If enabled is false, one-tap player deaths will be silent.
# Mobs keep their normal vanilla death messages.
# Placeholders: %victim%, %killer%, %victim_type%
death-messages:
  enabled: true
  show-killer: false
  player-message: "%victim% died"
  player-message-with-killer: "%victim% got one tapped by %killer%"

💾 Player Data (players.yml)

1tk stores player state in a separate data file:

enabled-players: []
immune-players: []

Both sections store UUIDs, not player names. This keeps data working even if a player changes their Minecraft username.