On 8 July 2011 03:02, uZu <u...@qlone.org> wrote: .. > Do you think that going to a coherent cvar > nameset could be valuable/useful for ioq3 ? And, in current state, is there > a (clean or immediate) way to support legacy cvars while adding/changing > some of them? I suppose that if some cvars are renammed, say 'scr_conspeed' > becomes 'cl_conSpeed' the need to support legacy users implies the need to > support legacy cvar names?
I don't know much of Quake3. But I suppose is possible to create a "alias" system where two names link to the same cvar. So you can have the legacy name, and other following a more logical sense. cvars interface with .cfg files. You can create a cvar named realxl_suck with value 1 and save it on the cfg file. So wen the engine realxl load, he will see this new cvar. Some compatibility with other engines exist has you may create some "cfg hell" on users that mix engines. This normally produce hard to debug problems, wen a "weird setting" in a cfg created by engine A crash engine B. The programmers on engine B will be absolutelly puzzled about why B is crashing.. until a analisys of the cfg file and step by step debugging blame the new setting. I don't know if this is a problem for quake3. Theres more than one engine in quake3? I suppose most people use ioQuake3, and only that one, so mixing engines with different cfg files parlances is not a problem. -- -- ℱin del ℳensaje. _______________________________________________ ioquake3 mailing list ioquake3@lists.ioquake.org http://lists.ioquake.org/listinfo.cgi/ioquake3-ioquake.org By sending this message I agree to love ioquake3 and libsdl.
