docs(vt): owner decision — no interop; slice 9 dropped, all plugins rewritten against acdream's own API
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
parent
d078863306
commit
bda8745448
3 changed files with 6 additions and 3 deletions
|
|
@ -26,6 +26,8 @@ implementation order.
|
|||
| 08 | [UI views](08-ui-views.md) | Every control of the nine tabs and three secondary views (type, geometry, binding), VVS control semantics our markup must offer, the markup extension needed (multi-column lists) | `uTank2.ViewXML.*.xml`, VVS `HudList/HudCombo/HudTabView`, `Decal3XMLParser.cs` |
|
||||
| 09 | [commands and interop](09-commands-and-interop.md) | The `/vt` verb table (~48 documented + 15 parser-only), chat sinks and dedup, the three-tier export API, Classic Looter SPI, MosswartMassacre's real usage | `uTank2/PluginCore.cs`, `d5.cs`, `ah.cs`, `eExternalsPermissionLevel.cs` |
|
||||
|
||||
**Owner decision 2026-09-06 — no interop.** All plugins are rewritten for acdream against its own API (VTank depends on Decal hooking the client; acdream controls it by API). Doc 09's export-API, relay and Classic Looter SPI sections are historical context, not a build target.
|
||||
|
||||
**Owner amendment 2026-09-06 — metas and navs use metaf `.af`.** Docs 06 §1
|
||||
and 07 §1 document VTank's binary `.nav`/`.met` layouts; MossTank does not
|
||||
implement them. It reads and writes the human-readable metaf format (the
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue