CookieCTF| Capture the Flag | In Game Editor⚔️ icon

CookieCTF| Capture the Flag | In Game Editor⚔️ -----

An easy to use Capture the flag plugin for all servers (feel free to suggest features in my discord)



CookieCTF — Event-Grade Capture‑the‑Flag for Minecraft
a fork of RamCTF

CookieCTF is a lightweight, admin‑driven CTF plugin designed for events, tournaments, and community game nights. It focuses on quick setup, clear team tools, and reliable match flow rather than 24/7 minigame automation.

Important fit note:
  • This is excellent for events (manual control, configurable teams, clear start/stop, spectator tools).
  • This is not aimed at persistent minigame servers (no map rotation, no automated queueing/lobbies, no long‑term stats storage beyond the current match).
Highlights
  • Multi‑team CTF: up to 8 teams; enable/disable per event.
  • Team customization: Colors, optional team prefixes on nametags/tab, colored flag banners.
  • Two game modes:
    • POINTS: capture flags to score.
    • DEATH_FLAG: capturing a team’s flag eliminates that team. The game ends when one team remains.
  • Team Captains: per‑team count customization and extra hearts' selection.
  • Watchers (spectators): Spectating matches while teams are fighting.
  • Scoreboard: shows game timers, team scores, and supports out‑of‑game visibility (for admins'n'stuff).
  • Timers: pregame and in‑game optional per‑death respawn timer.
  • Kits: optional kits at game start and after respawn (configurable with drops behavior) (there can only be 1 kit).
  • Effects: optional effects for flag carriers.
  • Commands hooks: run server commands at start/end, per winner/loser team, per kill/death, and on so much more.
  • PlaceholderAPI expansion: placeholderAPI support for status, time, teams, colors, scores, and so much more.
Installation
  1. Place the CookieCTF jar in plugins/ and restart your Paper/Spigot server.
  2. Optional: install PlaceholderAPI for placeholders.
  3. Use /ccpanel to open the admin setup GUI.
Server target: api-version: 1.20.

Quick Start
  1. Open the admin panel: /ccpanel.
  2. Enable the teams you need and set team names/colors if desired.
  3. Set flag locations for enabled teams (either via GUI pages or):
    • /cccommand flag setflaghere <team> (uses your current position)
    • /cccommand flag setflagpos <team> <x> <y> <z> <world>
  4. Choose team assignment flow:
    • Admin‑assigned (manual)
    • Self‑pick: /cccommand team pick-self (+ announce /ccteam to players)
    • Auto‑assign (balanced): /cccommand team auto (or include/exclude variants)
  5. Start the match flow:
    • /cccommand game start → runs pregame if pregame timer > 0, otherwise starts game
  6. End anytime: /cccommand game stop (runs end hooks, teleports to end location if configured, clears teams).
Commands
  • /ccpanel — Admin setup panel (requires CookieCTF.admin).
  • /ccteam — Team selection GUI for players.
    • Other commands that do the same: teams, ccteams, team
  • /ccmatch — Quick match control panel (requires CookieCTF.match).
Admin command base (below you will find all the subcommands for this command):
  • /cccommand <team|game|flag|gamemode> … (requires CookieCTF.admin)
Team subcommands:
  • team add <player> <team> — Add player to team (or watch if spectator).
  • team remove <player> <team> — Remove from team (or remove watch if spectator).
  • team clear <all|team> — Clear everyone or everyone on one team.
  • team auto — Auto‑assign all unassigned players evenly across enabled teams (give or take a few if there's an uneven amount of players).
  • team auto-include — Auto‑assign only players with CookieCTF.team.include.
  • team auto-exclude — Auto‑assign everyone except players with CookieCTF.team.exclude.
  • team pick-self — Start self‑pick; players use /ccteam.
Game subcommands:
  • game start — Starts pregame or game depending on pregame timer.
  • game stop — Ends the game and runs end commands.
  • game points <add|remove> <team> <amount> — Adjust score in POINTS mode.
Flag/team setup subcommands:
  • flag enable <team> / flag disable <team> — Toggle team availability.
  • flag setflaghere <team> — Set base flag at your position.
  • flag setflagpos <team> <x> <y> <z> <world> — Set base flag by coordinates.
  • flag resetflagloc <team> — Clear flag for team.
  • flag setcolor <team> <name|R,G,B> — Set team color.
  • flag custom-spawn-enable|disable <team> — Toggle a team’s custom spawn.
  • flag custom-spawn-pos <team> <x> <y> <z> <world> — Set custom spawn.
  • flag custom-spawn-pos-reset <team> — Clear custom spawn.
Gamemode:
  • gamemode <death_flag|points> — Switch between modes.
Notes:
  • <team> accepts team0..team7, numeric 0..7, legacy red|blue, or the configured team name.
  • watch is a pseudo‑team to place a player into the watcher role.
Permissions
  • CookieCTF.admin — Admin access (default: op)
  • CookieCTF.team — Access team selection GUI (default: op)
  • CookieCTF.match — Access match panel (default: op)
  • CookieCTF.team.include — Eligible in auto‑include assignment (default: no one)
  • CookieCTF.team.exclude — Excluded in auto‑exclude assignment (default: no one)
PlaceholderAPI
Available placeholders:
  • %cookiectf_leading_team% — Leading team name or draw.
  • %cookiectf_losing_team% — Lowest‑score team or none.
  • %cookiectf_team% — Player’s team color code.
  • %cookiectf_team_kills% — Player’s kills this match.
  • %cookiectf_team_deaths% — Player’s deaths this match.
  • %cookiectf_status% — running or offline.
  • %cookiectf_time_remaining% — time remaining.
  • %cookiectf_player_team% — Player’s team name.
  • %cookiectf_player_captain% — true|false.
  • %cookiectf_player_team_score% — Player team’s score.
  • %cookiectf_[color]_score% — Shows the score for a specific team color
Event operations model
  • Admin‑driven lifecycle with GUIs: easy to configure quickly, run a single match, then reset.
  • Clear start/stop; players are automatically teleported and inventories can be managed.
  • Spectator “watchers” are safely isolated (no interactions, damage, block edits, or spectate‑TP).
  • Scoreboard and titles communicate progress clearly to participants or whole server (toggleable).
  • Minimal background automation: you keep control of maps, rotations, and schedule.
Reasons to not use it on minigame servers:
  • No automatic matchmaking/queues, no persistent arenas/rotations, no economy/progression systems.
  • Stats are match‑scoped (kills/deaths counters) and reset with the event.
Screenshots
  • Main Setup Panel: [​IMG]
  • Team Selection Menu: [​IMG]
  • Settings Panel: [​IMG]
  • Flag Menu: [​IMG]
Support
Resource Information
Author:
----------
Total Downloads: 298
First Release: Mar 8, 2025
Last Update: Sep 14, 2025
Category: ---------------
All-Time Rating:
2 ratings
Version -----
Released: --------------------
Downloads: ------
Version Rating:
----------------------
-- ratings