dmg/spigot-base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 27 Wiki Activity

fix(settings): use static dialog command actions
Release / release (push) Successful in 2m55s
Details
CI / build (push) Successful in 1m16s
Details

Browse Source
This commit is contained in:
dmg
2026-08-25 19:06:05 -04:00
parent 8b3eaad253
commit bc2f9d8e25
4 changed files with 32 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
design/log.md
+7
View File
@@ -130,6 +130,13 @@ description: Chronological record of material decisions affecting the Spigot Bas
- Preserved unit-test coverage through server-independent dialog specifications and adapted Bukkit test fixtures to Purpur's registry-aware API behavior.
- Verified 128 tests and the Java 25 plugin artifact with `./gradlew clean check jar`.
## 2026-08-25 — Static dialog command actions
- Replaced macro command templates with static run-command actions for fixed dialog buttons.
- Added regression coverage for the generated run-command action and its unchanged command payload.
- Verified `/basesettings` opens without command exceptions on a local Purpur 26.2 build 2618 server.
- Verified the plugin artifact with `./gradlew clean check jar`.
## 2026-08-24 — Pocket Base mob portal travel
- Added five-tick collision scanning that transports non-player living mobs through active Pocket Base entrance and return portals.
design/user-stories/us-020-control-base-through-dialog-ui.md
+4 -2
View File
@@ -2,7 +2,7 @@
type: User Story
title: "US-020: Control a base through a dialog UI"
description: Let players inspect and control their base through Minecraft's native dialog interface.
status: in-progress
status: done
---
# US-020: Control a base through a dialog UI
@@ -21,7 +21,9 @@ As a **player**, I want a dialog-based base dashboard so that I can inspect prog
- [x] `ui` is offered through command autocomplete.
- [x] Non-player execution remains safely rejected.
- [x] Automated tests verify dialog routing and generated controls.
- [ ] The dialog uses Purpur's supported Paper dialog API and opens on the production Purpur 26.2 runtime without missing-class or command exceptions.
- [x] Fixed dialog commands use Purpur static run-command actions rather than macro templates.
- [x] A rendering regression test verifies fixed command buttons do not throw `No variables in macro`.
- [x] The dialog uses Purpur's supported Paper dialog API and opens on the production Purpur 26.2 runtime without missing-class or command exceptions.
## Related