mirror of
https://github.com/brues-code/ClassicAPI.git
synced 2026-11-16 16:10:36 +00:00
The intro claimed this client is the Vanilla game type, which read as a contradiction against the paragraph below it saying `_Vanilla` files are not used. Both are true: `_Vanilla` as a file suffix names the Classic Era client, while `vanilla` as a directive value names this client's game type. Drop the intro sentence, since the [Family] / [Game] table already states it where a reader can use it, and add a note about the shared word where the collision is first hit. Explain why `_Vanilla` and `_Classic` are skipped instead of saying only that they target an engine this build does not match, and state the consequence: an addon shipping just `_Vanilla` and `_Mainline` TOCs does not load at all, so it needs a `_ClassicAPI.toc`. List both flavor sets in probe order, and give the Bindings half the same shape as the TOC half. The `## Interface:` subsection showed a multi-version line and then said nothing about it. Say that the addon loads when 11200 appears anywhere in the list.