43 lines
2.8 KiB
Markdown
43 lines
2.8 KiB
Markdown
---
|
||
type: Log
|
||
title: Spigot Base Design Log
|
||
description: Chronological record of material decisions affecting the Spigot Base design.
|
||
---
|
||
|
||
# Spigot Base Design Log
|
||
|
||
## 2026-08-09 — Initial progression design
|
||
|
||
- Base progression is sequential: Base I establishes a base, Base II provides navigation, Base III provides personal teleportation, and Base IV permits visitor teleportation.
|
||
- Every secondary progression path requires Base I.
|
||
- A base is cylindrical and begins with a 10-block radius and a vertical extent 25 blocks above and below its set Y coordinate.
|
||
- Only Survival-mode activity contributes progress; repeatedly placing and breaking blocks is permitted.
|
||
- Flight is limited to the base, includes a five-block horizontal warning buffer, and can be toggled by the player.
|
||
- Player-facing administration will initially use commands rather than an inventory UI.
|
||
- The build and release pipeline will follow the neighboring Trigger Spawn project pattern.
|
||
|
||
## 2026-08-09 — Implementation started
|
||
|
||
- Approved implementation begins with the tested Gradle/Spigot foundation, validated configuration, and durable player state.
|
||
- Feature work will proceed incrementally using tests before implementation where practical.
|
||
|
||
## 2026-08-09 — Core implementation checkpoint
|
||
|
||
- Implemented UUID-keyed YAML state, validated configuration, Base I–IV progression, base sizing, particle navigation, controlled base flight, personal and visitor teleportation, progress feedback, and initial administrative commands.
|
||
- Added Gradle, Spigot metadata, Gitea CI/release workflows, and project documentation based on Trigger Spawn.
|
||
- Verified the implementation with `./gradlew clean check jar`: 34 tests passed and the plugin JAR was produced successfully.
|
||
- User stories remain in progress pending live-server integration verification and completion of runtime administrative configuration editing.
|
||
|
||
## 2026-08-09 — Navigation preference fix
|
||
|
||
- Added explicit, idempotent `/basenavigation on` and `/basenavigation off` modes with autocomplete while retaining no-argument toggling.
|
||
- Preserved a disabled navigation preference during later grass-or-dirt progression instead of forcing navigation back on.
|
||
|
||
## 2026-08-09 — Initial release scope completed
|
||
|
||
- Added live, validated, persisted numeric configuration updates through `/baseadmin config`.
|
||
- Added administrative progress-counter updates, prerequisite-aware level changes, cooldown clearing, and cascading path resets.
|
||
- Made progression materials, visitor currency, boss-bar duration, particle count, and title timing configurable.
|
||
- Preserved unknown forward-compatible YAML fields for retained player records while continuing to reject invalid progression state.
|
||
- Completed and verified all approved user stories with the automated Gradle check lifecycle.
|