Bundle canonical joinsigns.yaml #2

Merged
NotAlexNoyle merged 2 commits from agent/bundle-canonical-joinsigns into main 2026-07-22 20:21:32 -04:00
NotAlexNoyle commented 2026-07-22 20:20:41 -04:00 (Migrated from github.com)

What changed

  • Added the canonical joinsigns.yaml to src/main/resources so it is packaged into the plugin jar.
  • Updated JoinSignManager to extract the bundled file on first startup when no external joinsigns.yaml exists.
  • Preserved existing server configuration by never overwriting an existing file.

Why

config.yml is already shipped as a default resource, while joinsigns.yaml previously had to be created manually or generated in-game. Shipping the canonical join-sign registry makes a fresh deployment reproduce the intended single join sign automatically.

Canonical sign

  • World: world
  • Coordinates: 124, 80, -121
  • Lobby config: default

Validation

  • Reviewed the branch diff against main.
  • Confirmed the change is limited to the resource file and two lines of first-run extraction logic.
  • A local Gradle build could not be run in this environment because outbound repository access and GitHub CLI were unavailable.
## What changed - Added the canonical `joinsigns.yaml` to `src/main/resources` so it is packaged into the plugin jar. - Updated `JoinSignManager` to extract the bundled file on first startup when no external `joinsigns.yaml` exists. - Preserved existing server configuration by never overwriting an existing file. ## Why `config.yml` is already shipped as a default resource, while `joinsigns.yaml` previously had to be created manually or generated in-game. Shipping the canonical join-sign registry makes a fresh deployment reproduce the intended single join sign automatically. ## Canonical sign - World: `world` - Coordinates: `124, 80, -121` - Lobby config: `default` ## Validation - Reviewed the branch diff against `main`. - Confirmed the change is limited to the resource file and two lines of first-run extraction logic. - A local Gradle build could not be run in this environment because outbound repository access and GitHub CLI were unavailable.
Sign in to join this conversation.