Description.ext – Talk
No edit summary |
mNo edit summary |
||
| Line 10: | Line 10: | ||
The section about radio commands notes something like ''title = {$STR_RADIO_2};'' Is the title looked up in the stringtable.csv? And is it localized? This should perhaps be noted somewhere. -- [[User:Manny|Manny]] 17:50, 20 February 2007 (CET) | The section about radio commands notes something like ''title = {$STR_RADIO_2};'' Is the title looked up in the stringtable.csv? And is it localized? This should perhaps be noted somewhere. -- [[User:Manny|Manny]] 17:50, 20 February 2007 (CET) | ||
:: Where ever you see $STR_ means its to be looked up in the stringtable. Feel free to make a note. [[User:Hoz|hoz]] | |||
Revision as of 20:17, 20 February 2007
Well, I now saw three different definitions for respawn = value... I'm not too sure about the numbers anymore as I only used "group", "instant" and "base" so far. Also it's not sure that "side" works...
--Raedor 01:20, 2 June 2006 (CEST)
I'm looking for a place where the preprocessor commands (like #define and #include) can be explained but I don't know whether it should be added here in the description.ext article or in something config related or should we create a new article for this? But could someone else do this because the reason I'm asking is that I'm looking for an explaination for the #include command --T_D 00:37, 7 August 2006 (CEST)
- this should be listed as "Config.cpp Preprocess Commands" under the addons category and a 'related link' put in desc.ext. While doing so, there should also be an attempt to mention the macros (stupid word that) true false public and private.
--ook? 07:59, 7 August 2006 (CEST)
The section about radio commands notes something like title = {$STR_RADIO_2}; Is the title looked up in the stringtable.csv? And is it localized? This should perhaps be noted somewhere. -- Manny 17:50, 20 February 2007 (CET)
- Where ever you see $STR_ means its to be looked up in the stringtable. Feel free to make a note. hoz