From b44282071cd49a227176e6e975b7bd2a13fef431 Mon Sep 17 00:00:00 2001 From: Erik Date: Sun, 6 Sep 2026 21:35:18 +0200 Subject: [PATCH] =?UTF-8?q?docs(vt):=20owner=20clarification=20=E2=80=94?= =?UTF-8?q?=20VTank=20has=20no=20real=20API;=20acdream=20may=20create=20it?= =?UTF-8?q?s=20own=20plugin=20API=20later?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Fable 5.1 --- docs/plans/2026-09-06-campaign-vt-vtank-oracle.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/plans/2026-09-06-campaign-vt-vtank-oracle.md b/docs/plans/2026-09-06-campaign-vt-vtank-oracle.md index 4d344b0e..83a56310 100644 --- a/docs/plans/2026-09-06-campaign-vt-vtank-oracle.md +++ b/docs/plans/2026-09-06-campaign-vt-vtank-oracle.md @@ -20,7 +20,7 @@ catalog. | Files | Drop-in compatibility for `.usd` profiles and `.utl` loot profiles (load unchanged; settings keep VTank's names). **Metas and navs use metaf `.af` (owner, 2026-09-06 amendment):** MossTank reads and writes the human-readable metaf format for both metas and nav routes and does NOT implement binary `.met` or author `.nav`; conversion to/from VTank's binaries is the metaf tool's job. Reference parser: `C:\Users\erikn\source\repos\metas\metaf_monolithic.py` (port of `metaf.cs`, GPLv3 — read, never paste), with 148 real `.af`, 25 `.met`, 130 `.nav` files beside it. Memory: `claude-memory/reference_metaf_af_format.md`. | | Knowledge base | Full catalog with decompile citations BEFORE implementation. | | Platform | Linux is a first-class target: no `System.Drawing`, no GDI+/Windows fonts, no Windows-only paths or registry, no COM. The plugin stays BCL-only per `AcDream.Plugin.Abstractions`. | -| Interop | **NONE (owner, 2026-09-06): "We should not do any interops. All plugins will have to get rewritten for acdream." VTank relies on Decal hooking/injecting the client; acdream controls the client through its own API.** No VTank export-API surface, no Decal-shaped relay, no compatibility layer for existing Decal plugins (MosswartMassacre, UtilityBelt, Mag-Tools are rewritten as acdream plugins when wanted). KB doc 09's interop sections stay as historical context only. Any future plugin-to-plugin need is designed on its own merits, host-mediated. | +| Interop | **NONE (owner, 2026-09-06): "We should not do any interops. All plugins will have to get rewritten for acdream." VTank relies on Decal hooking/injecting the client; acdream controls the client through its own API.** No VTank export-API surface, no Decal-shaped relay, no compatibility layer for existing Decal plugins (MosswartMassacre, UtilityBelt, Mag-Tools are rewritten as acdream plugins when wanted). KB doc 09's interop sections stay as historical context only. VTank has no real API — what KB 09 calls its "export API" is a reflection relay behind a signed handshake that every real consumer bypassed. If acdream plugins ever need to talk to each other, acdream creates its own plugin API later, on its own terms ("we can of course create one later on"). | ## The oracle (local, never committed)