RunicGateway/runicnpc-rust
3
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases 2 Wiki Activity

feat!: RunicNPC v1.0.0, edge → main (runicnpc 9e step 3, merge 1 of 3) #19

Merged
whitlocktech merged 39 commits from edge into main 2026-10-09 07:20:03 +00:00
Conversation 0 Commits 39 Files Changed 17 +3 -2
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit 89df052d7d - Show all commits

5
README.md
View File

@@ -7,7 +7,7 @@ works on its own, and on a [Runic Gateway](https://gitea.whitlocktech.com/RunicG
website authors its NPC profiles and events use its NPCs. The plan of record, stage by stage, is
[`docs/runicnpc/PLAN.md`](https://gitea.whitlocktech.com/RunicGateway/docs/src/branch/main/runicnpc/PLAN.md).
> **Status: stage 9, hardening for v1.0.0.** The NPC, its profiles, placements and routes; factions,
> **Status: v1.0.0, stage 9's release.** The NPC, its profiles, placements and routes; factions,
> fights, escorts and tethers; bosses and passive NPCs; loot. Admins use the `/rnpc` commands, other
> plugins the API (version 6). On a Runic Gateway server RunicNPC is **required** (D310): the website
> authors its profiles and faction table, edits its placements, and every NPC an event places is
@@ -184,7 +184,8 @@ and +5.2 ms fighting to the median frame. Load `tools/RunicNpcTest.cs` on a rig
Work lands on `edge` and is cut over to `main`; every releasable push to `main` tags and publishes a
release (`.gitea/workflows/release.yml`). The version comes from Conventional Commits since the
last tag. `v1.0.0` is stage 9's release, the one `module-rust` then requires.
last tag. `v1.0.0` is stage 9's release, the one `module-rust` requires; it was cut by a `feat!:`
commit, because the stages before it were all `feat:` and would have made it `v0.2.0`.
## Contributing