dmg
8e2d86b2cc
BREAKING CHANGE: New releases require Java 25/Purpur 26.2 and use purpur-trigger-spawn-<version>.jar. Runtime TriggerSpawn identity, persisted progression/cooldowns and world spawn settings remain unchanged. Replace the old JAR rather than installing both distributions.
1.3 KiB
purpur-trigger-spawn agent entrypoint
The canonical stories, engineering guidance, and all process documents are in the private SoMC OKF wiki.
Before work, read the sibling ../somc-okf/index.md, ../somc-okf/processes/index.md, ../somc-okf/projects/purpur-trigger-spawn/index.md, engineering.md in that project section, and relevant ../somc-okf/user-stories/purpur-trigger-spawn/ stories. Also follow the parent workspace AGENTS.md when present.
For standalone checkouts, start at the project page and shared process. Obtain wiki access before feature work; do not recreate a local knowledge bundle. Source builds do not require private wiki access.
Development follows Development cycle: approved stories, failing tests, passing implementation, verification, then source/wiki commit and push. GitOps updates are committed locally without pushing; only Do release authorizes a reviewed GitOps push.