SawatoMosswartsEnjoyersClub/openac-mosswartmassacre
3
0
Fork 0
Code Issues Pull requests Projects Releases 2 Packages Wiki Activity Actions
Mosswart Massacre for OpenAC (owner-only)
29 commits 4 branches 2 tags 365 KiB
Find a file
Erik a9c6938f0e
Some checks failed
CI / build-and-test (pull_request) Failing after 47s
Details
CI / release (pull_request) Has been skipped
Details
Build, test and release on the club Gitea 
A Forgejo workflow builds and tests every push and pull request on the
club's docker runner. A v* tag also assembles the plugin zip, checks it
with OpenAC's own plugin checker, and publishes a Gitea release with the
zip, its checksum and plugin.json.

The checker refused the manifest: both permission notes were over the
launcher's 120-character limit. They are shorter now.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-26 16:00:00 +02:00
.forgejo/workflows Build, test and release on the club Gitea 2026-09-26 16:00:00 +02:00
src/OpenAC.MosswartMassacre Build, test and release on the club Gitea 2026-09-26 16:00:00 +02:00
tests/OpenAC.MosswartMassacre.Tests Show the backend socket's status and errors in chat, as the original did 2026-09-26 07:30:30 +02:00
tools Build, test and release on the club Gitea 2026-09-26 16:00:00 +02:00
.gitattributes Slice 2: telemetry, vitals, chat, spawn/portal, rare, kills and combat stats 2026-09-25 12:12:22 +02:00
.gitignore Build against plugin API 0.1.19-mm.1; item header words from the host 2026-09-25 12:58:43 +02:00
Directory.Build.props Build against the released OpenAC 0.1.19 plugin contract 2026-09-26 06:36:44 +02:00
Directory.Packages.props Skeleton: plugin root, backend socket, /mm router, settings, test harness 2026-09-25 12:03:00 +02:00
global.json Skeleton: plugin root, backend socket, /mm router, settings, test harness 2026-09-25 12:03:00 +02:00
NuGet.Config Skeleton: plugin root, backend socket, /mm router, settings, test harness 2026-09-25 12:03:00 +02:00
OpenAC.MosswartMassacre.slnx Skeleton: plugin root, backend socket, /mm router, settings, test harness 2026-09-25 12:03:00 +02:00
README.md One plugin-bar button and one tabbed window, as the original 2026-09-26 06:56:10 +02:00

README.md

Mosswart Massacre for OpenAC

A private OpenAC port of the Mosswart Massacre DECAL plugin: it streams telemetry, vitals, chat, inventory, combat and character stats to the Mosswart Overlord backend, shares vitals and debuffs across machines, runs the commands typed into the Overlord chat box, keeps the flag tracker and syncs metas.

The backend contract is fixed. Every frame this plugin sends or accepts is byte-for-byte what the DECAL plugin sent and accepted; the golden tests under tests/ pin each one. Change a frame only together with the backend.

Building

The plugin contract is AcDream.Plugin.Abstractions of the version named in Directory.Build.props (PluginApiPackageVersion), currently 0.1.19, the OpenAC 0.1.19 release. Put that release's package in packages-local/; an OpenAC client from 0.1.19 on loads the plugin.

gh release download v0.1.19 --repo eriknihlen/OpenAC -p "AcDream.Plugin.Abstractions.0.1.19.nupkg" -D packages-local
dotnet build OpenAC.MosswartMassacre.slnx
dotnet test OpenAC.MosswartMassacre.slnx

Installing

Copy src/OpenAC.MosswartMassacre/bin/<config>/net10.0/ (the dll, its .deps.json, Newtonsoft.Json.dll, plugin.json and the markup) into %LOCALAPPDATA%\acdream\plugins\openac.mosswartmassacre\.

First run

Streaming is off until you turn it on. The shared secret is never compiled in:

/mm ws secret <the backend's shared secret>
/mm ws enable

/mm help lists every command.

The plugin has one button on the plugin bar, MM. Its Metas tab downloads the club's metas and navs into the shared VTank profile folder the client configures (by default %LOCALAPPDATA%\OpenAC\vtank), under mosstank\metas and mosstank\navs, where MossTank loads them; the tab shows both folders.

Testing against a stand-in backend

tools/FrameRecorder accepts the plugin's socket like the backend does, records every frame to a JSON-lines file, relays share_* frames between subscribed clients as the backend does, and compares two recordings by frame shape:

dotnet run --project tools/FrameRecorder -- record 18765 frames.jsonl
/mm ws url ws://localhost:18765/websocket/
dotnet run --project tools/FrameRecorder -- compare decal.jsonl port.jsonl