NotTodo

• (1-1) Adding too many library dependencies
  • No more external shared library dependency, except when there's a strong need
  • Additional rarely-used library ends up as larger Windows distribution file, most part of which are never used, and longer start-up time
• (1-2) Support for more image formats
• (1-3) Emphasizing features and customizability over quality and aesthetics
• (1-4) No polygonal models

Gameplay (things that could be considered cheating)

• (2-1) Showing others' (especially those of the opponents) weapons in the scoreboard
• (2-2) Reducing weapon spreads (As of the version 0.1.1 OpenSpades' spread/recoil pattern is mostly identical to that of that of the original client.)
• (2-3) Rendering cartoon-like outlines around objects

Protocol Restrictions (.75/.76β Compatible Mode)

• (3-1) Showing your teammate's health or block count (The piqueserver/pyspades servers don't send them.)

Technical Restrictions

• (4-1) Physically-based translucent voxels
  • Requires costly order independent transparency or volumetric rendering
  • Alternatives: (a) sprites (b) ModelRenderParams::ghost
  • That being said...
    • Possibly could use http://www.iquilezles.org/www/articles/volumesort/volumesort.htm , as the voxels are aligned to a grid, and ordered in a grid.
    • Or any cheap OIT
• (4-2) Non-cubic voxels (Unsupported by KV6, VXL nor VOXLAP)

Coding Style

• (5-1) Adding more global variables without a strong justification and adequate documentation on regard to their role and thread safety

Other Restrictions

• (6-1) Adding an anti-cheat system like VAC or PunkBuster (Commercial solutions cost too much for a nonprofit project, and it's very likely that they're unusable in open-source projects.)