RunicGateway/Module-Rust
3
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases 4 Wiki Activity

feat(zones): a blank dome stack is 3 spheres, not 1 (runicnpc 9e, D326) #36

Merged
whitlocktech merged 1 commits from feat/9e-dome-stack-3 into edge 2026-10-09 06:29:28 +00:00
Conversation 0 Commits 1 Files Changed 2 +14 -2
wtclaude commented 2026-10-09 06:25:08 +00:00
Member
Copy Link

What & why

RunicNPC stage 9e, step 1 (docs/runicnpc/PLAN.md). In the 9d player session the org lead chose the default dome by eye at noon: 3 spheres. When the zone step's stack is left blank it now sends 3, and the field's hint reads "Left blank, 3". Steps saved with a blank stack draw 3 from their next run.

The wire is unchanged (D326: module only). The module always sends a stack, and the bridge's own default for a dome sent without one stays 1. No protocol bump.

Docs: RunicGateway/docs PR for 9e step 1 (D326–D328).

How it was tested

  • New test a dome with its stack left blank stacks 3 spheres (D326).
  • npm test in server/: 505/505 pass.

Checklist

  • I have read CONTRIBUTING.md.
  • The change builds and existing tests/checks pass locally.
  • I have added or updated tests/docs where it makes sense.
  • My commits are reasonably scoped with clear messages.

AI-assisted contributions (required)

  • No AI tools were used to produce this contribution.
  • AI tools were used. Tool(s): Claude Code (Claude Opus 5.5). I have reviewed and understand
    every change, and take responsibility for it. AI-authored commits are
    marked with a Co-Authored-By / Assisted-By trailer.

License

  • I agree that my contribution is licensed under this project's license
    (GNU GPL v3.0 or later), and I have the right to contribute it.

🤖 Generated with Claude Code

https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

## What & why RunicNPC stage 9e, step 1 (docs/runicnpc/PLAN.md). In the 9d player session the org lead chose the default dome by eye at noon: **3 spheres**. When the zone step's stack is left blank it now sends 3, and the field's hint reads "Left blank, 3". Steps saved with a blank stack draw 3 from their next run. The wire is unchanged (D326: module only). The module always sends a `stack`, and the bridge's own default for a dome sent without one stays 1. No protocol bump. Docs: RunicGateway/docs PR for 9e step 1 (D326–D328). ## How it was tested - New test `a dome with its stack left blank stacks 3 spheres (D326)`. - `npm test` in `server/`: 505/505 pass. ## Checklist - [x] I have read [CONTRIBUTING.md](CONTRIBUTING.md). - [x] The change builds and existing tests/checks pass locally. - [x] I have added or updated tests/docs where it makes sense. - [x] My commits are reasonably scoped with clear messages. ## AI-assisted contributions (required) - [ ] No AI tools were used to produce this contribution. - [x] AI tools were used. Tool(s): `Claude Code (Claude Opus 5.5)`. I have reviewed and understand every change, and take responsibility for it. AI-authored commits are marked with a `Co-Authored-By` / `Assisted-By` trailer. ## License - [x] I agree that my contribution is licensed under this project's license (**GNU GPL v3.0 or later**), and I have the right to contribute it. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
wtclaude added 1 commit 2026-10-09 06:25:13 +00:00
feat(zones): a blank dome stack is 3 spheres, not 1 (runicnpc 9e, D326)
All checks were successful
PR Checks / server-tests (pull_request) Successful in 32s
Details
PR Checks / frozen-manifest (pull_request) Successful in 1m13s
Details
PR Checks / client-build (pull_request) Successful in 7m49s
Details
e1789c1df4 
The org lead chose 3 by eye at noon in RunicNPC's 9d player session. The
zone step sends it when its stack is left blank, and the field's hint says
so. The wire is unchanged: the module always sends a stack, and the bridge's
own default for a dome without one stays 1.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
whitlocktech merged commit 65cef3e7c0 into edge 2026-10-09 06:29:28 +00:00
whitlocktech deleted branch feat/9e-dome-stack-3 2026-10-09 06:29:29 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something is not working
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
invalid
Something is wrong
question
More information is needed
wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
ksfixitman whitlocktech wtclaude
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: RunicGateway/Module-Rust#36
No description provided.
Delete Branch "feat/9e-dome-stack-3"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?