feat(bridge): RunicNPC, the site's NPC profiles and placements (runicnpc stage 4) #22
Reference in New Issue
Block a user
No description provided.
Delete Branch "feat/runicnpc-stage4"
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?
What
This is the bridge's part of RunicNPC stage 4. It joins protocol 13, which is still unreleased (D248). The spec is docs
rust-link/PROTOCOL.md§19.12.integrations.runicNpc(loaded,version,api) is in hello and status. Hello is sent again when RunicNPC loads or unloads.npc.profiles: read the server's profiles, before the site adopts them (D244).npc.profiles.set: the push (D221).npc.placements: the list, with the routes and the cost warning.npc.placement, byop:add(from a map point, D245, D246),set,remove,rename,respawn.npc.errorwithrunicnpc-missing,runicnpc-old,malformed,not-foundorrefused, the last carrying RunicNPC's own sentence.npc.died(profile, name, owner, run or placement, killer, contributors),npc.health(a threshold) andnpc.placement.changed.world.placetakes aprofile(D243). The NPCs are RunicNPC's, owned by the run; revert goes throughRunicNpc_Despawn. New permanent reasons:runicnpc-missingandunknown-profile.attackerNpcandattackerProfile, beside the unchangedattackerName.player.tallygainsnpcProfileKills(D247).rg.npcin the console.overlay.tomldeclaresrunicnpc_api = 3, the release copies it into the manifest, andcheckPlugin.jsholds it equal toRunicNpcApiNeeded.Tested
checkPlugin.jspasses (51 hooks), with a check that catches arunicnpc_apimismatch.Pairs with
runicnpc-rust
feat/stage-4-api3, Rust-Link, Module-Rust and installerfeat/runicnpc-stage4, plus the docs PR.Checklist
Claude Code (Claude Opus 5.5). Commits carry theCo-Authored-Bytrailer.🤖 Generated with Claude Code
https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY