User:Anarchid/OmniCommanderDesign

Historically ZK has had several commander chassis to provide variety for a bunch of reasons:

• Initially it was the only way to provide commander variety (because procedural generation of unitdefs was not available)
• Later, because while `unitdefs_post`solved the former problem, the models existed, and provided some, albeit visual feedback on what the commander was
• Even later, as commanders became mostly "dynamic", for the same legacy reasons
• No model that would display more useful information than the current system exists.

This is bad for several reasons:

• Significantly initially different chassis are pregame RPS in several situations - such as Recon commander's jump available at level zero, or Support commander's build range
• This provides useful visual representation only for one important commander ability - jump - while all other abilities are essentially hidden.

This is my attempt to figure out a design for an unified commander chassis. That requires the model problem to be solved, but fortunately, models are not primordial words of god; they can be made just like the current four models were.

Design Design

Before approaching the design of this thing, it is useful to approach the design of designing this thing.

1. As with current commander design requirements, this design should not have degenerate, overpowered or useless paths.
2. For transition from chassis to modules entirely, the first level-up should be important enough to encompass all of the variety in current chassis and first-morph modules
   1. With the following criterion, this also means that the first morph should make commanders very *visibly* different as well.
3. As much interesting information about the commander as possible should be meaningfully visible on the commander body.
   1. This intrinsically suggests tying commander modules to their respective body parts, and maybe even have body part based equipment slots
   2. Current stackable or weapon modules are insufficient to encompass this. A "subsystem module" approach like in Aquanim's draft may be useful.
   3. The important qualitatively difference items should take priority. Guns and jump ability are first tier; everything else is secondary or tertiary.
4. The technical considerations of the omni-commander model should be considered at every step
   1. The model should be reasonably easy to modify and generally as low-maintenance as possible
   2. Replacement or refund of current commander skins should be considered and made as easy as possible
   3. Additional types of "hats" could be considered