---
type: Log
title: Trigger Spawn Design Log
description: Chronological record of significant Trigger Spawn design decisions.
---

# Trigger Spawn Design Log

## 2026-08-08 — Initial user stories

- Target Spigot 26.2 and Java 17 with a Gradle and Gitea Actions pipeline modeled on `spigot-event-producer`.
- Unlock `/spawn` after the first observed Warden, Ender Dragon, or Wither kill.
- Use real elapsed time for cooldowns, with defaults of eight, four, and one hour as unique boss kills accumulate.
- Support administrator-defined cooldown grants, complete access resets, and bans.
- Maintain a separate circular spawn area in each world, with a default radius of 20 blocks and safe randomized destinations.
- Require a stationary three-second warm-up that is cancelled by walking to another block, jumping, falling, teleportation, or world changes.

## 2026-08-08 — Progression reminders and rewards

- Remind players with incomplete progression that remaining unique boss kills permanently reduce the `/spawn` cooldown.
- Clear the active cooldown immediately after each newly credited unique boss kill.
- When cooldown prevents `/spawn`, explicitly report that it is unavailable and show the remaining wait in a friendly format.

## 2026-08-08 — Build and release foundation

- Added the Java 17 Gradle project targeting Spigot API 26.2, with JUnit 5 verification and versioned resource processing.
- Added Gitea CI and semantic-release workflows modeled on `spigot-event-producer`.
- Documented local builds, public releases, and the required `RELEASE_TOKEN` repository secret.