Submit or Build a Comp Package¶
A comp package is more than a weapon list.
A useful package explains what the formation is trying to do, what roles it needs, what assumptions it makes, and what kind of roster can execute it.
How to submit¶
Send comp-package submissions or questions on Discord: saadvii.
For best results, include the package data in a clean document, sheet, or message using the categories below. If the package uses private VODs or private guild context, anonymize player names, guild drama, private comms, and exact political context before sending it.
Minimum useful package data¶
| Area | Needed information |
|---|---|
| Formation identity | brawl, bomb, kite, control, ranged pressure, hybrid, or other |
| Role list | slots, role names, party layout, scaling order |
| Builds | weapon, armor, helmet, boots, cape, food, potion, important abilities |
| Support structure | healers, Locus/cleanse/shield/resistance, defensive tank coverage |
| Timing model | engage cycle, clump timing, damage timing, pressure windows |
| Terrain preference | open field, choke, gate, castle, territory, objective, kite route, etc. |
| Weaknesses | what counters it, what it struggles to execute, what happens when tools are missing |
| Training notes | common mistakes, VOD prompts, readiness requirements |
| Source context | VODs, testing, caller notes, patch date, or other evidence |
Public-package standard¶
A package should not be added publicly just because it is popular or sounds strong. It needs enough context to avoid misleading readers.
The public manual should teach principles. The Ledger can document packages when the data is reliable enough.
Package depth levels¶
| Level | Meaning |
|---|---|
| Full Doctrine Package | roles, builds, scaling, timing, terrain, support needs, weaknesses, drills, source context |
| Lite Comp Package | roles and builds with basic notes, not full doctrine |
| Build Sheet Only | builds listed without enough strategic context |
| Research / Placeholder | interesting idea that needs verification or testing |
Avoid these submissions¶
- "top guild plays it" with no role explanation
- weapon lists without support/healer assumptions
- patch-sensitive claims with no verification date
- private drama or named-player criticism
- one-fight examples presented as universal doctrine