Source: Game configuration

[LogicAndTrick]

This issue will track implementation of settings and configuration for Source engine games.

What's needed:

• API to detect engine features - each engine will advertise which features it supports, and Sledge will automatically "downgrade" incompatible implementations when it compiles. Examples:
  • Displacements: Source supports them, but Goldsource maps will pre-compile into tetrahedrons
  • Instances: Newer Source supports them, older Source and Goldsource maps will perform instantiation on pre-compile
  • Entity I/O: Only Source games will show the entity I/O tabs
  • ... and so on.
• Automatic scanning & setup of installed games - this isn't required for Source support, but would help many people get Sledge configured properly
• Support for multiple Steam game libraries - Steam now supports custom install directories, Sledge must be aware of these and work correctly with games installed to custom game libraries
• Support for Source compile tools (tools specification, compiling using Source directories)

[BenVlodgi]

I suggest that when implementing instances:

• Sledge should have the option to collapse instances as a precompiler operation.

I know atleast for the Portal 2 compilers, compiling a map with instances screws up the instance's lighting (I don't know why). Its verifiable if you have a brush in an instance and a brush next to it in the map. The lighting should be smooth over the adjacent brushes, but the lighting will be brighter on one.