Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Use Quake's console variables approach for all customizable settings #1071
Quake 3 and some other games use console variables (cvars) to store their settings. This allows to change every single value from an ingame console and tweak the game to a degree which is almost impossible to provide with a GUI-only implementation.
Here is an example of a Quake 3/OpenArena configuration file: https://gist.github.com/Hiradur/9c396b54ea4213d0de62
@only-a-ptr already mentioned something similar before and I also think this would be nice to have in RoR. Implementing this would require a lot of monkey typing though, I assume.
I don't recall suggesting anything similar, however, it's VERY tempting. I've seen this type of configuration in many respectable engines, using it would improve our image. And I do like the technical side of it.
As a matter of fact, RoR internally works halfway this way. Our "RoR.cfg" is parsed into a hashmap and it's values are accesse by our *SETTING() macros from anywhere. However, AFAIK there's no console integration and due to the simplistic implementation (everything's stored as string in
Using the Quake approach would mean to ditch our
Anyway, I like the idea.
I recall you talking about making the ingame settings more accessible for experimentation, but maybe you had something completely different in mind.