You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When this special argument is set, MESS will show a list of available arguments and then quit. All other arguments will be ignored.</p>
160
+
<h2id="-convert"><code>-convert</code></h2>
161
+
<p>
162
+
This switch enables file conversion mode. In this mode, map files can be converted to different formats. Supported formats are <code>.map</code> (both 'normal' and TrenchBroom files), <code>.rmf</code> (Hammer) and <code>.jmf</code> (J.A.C.K.). This mode also supports cordon areas and VIS group filtering. See <ahref="file-conversion.html">File conversion</a> for more information.</p>
163
+
<p>
164
+
Use <code>-convert -help</code> to show a list of available arguments for the convert mode.</p>
134
165
<h2id="-repl"><code>-repl</code></h2>
135
166
<p>
136
-
This special argument enables the interactive MScript interpreter mode. This starts a REPL (read-evaluate-print loop) that can be used to try out MScript, the scripting language that is embedded in MESS. If this argument is set, then all other arguments will be ignored.</p>
167
+
This switch enables the interactive MScript interpreter mode. This starts a REPL (read-evaluate-print loop) that can be used to try out MScript, the scripting language that is embedded in MESS. If this argument is set, then all other arguments will be ignored.</p>
137
168
<p>
138
169
While MScript is almost entirely expression-based, REPL mode supports assignments. For example, <code>a = 4 + 5</code> will store the result of the <code>4 + 5</code> expression in the variable named <code>a</code>. For convenience, the latest evaluation result is also stored in a special variable named <code>_</code>.</p>
This overrides the <code>mess.fgd</code> file path setting from the current configuration file. See <ahref="configuration-files.html#fgd-path">configuration file: fgd-path</a> for more information.</p>
These variables will be available in MScript expressions in the map properties and top-level entities of the input map. The input format is <code>"name1 = expression; name2 = expression;"</code>, and so on.</p>
159
190
<p>
160
191
These variables are added to the ones from the current configuration file. If multiple variables with the same name are specified, then the last value wins. Variables provided via the command-line always overwrite variables from the configuration file if they have the same name. See <ahref="configuration-files.html#variables">configuration file: variables</a> for more information.</p>
Global variables are available in MScript expressions anywhere, via the <code>getglobal</code>, <code>setglobal</code> and <code>useglobal</code> functions. Unlike variables, which are only available in the map properties and in top-level entities, globals are also available inside templates and template maps. The input format is <code>"name1 = expression; name2 = expression;"</code>, and so on.</p>
This overrides the maximum instances setting from the current configuration file. See <ahref="configuration-files.html#max-instances">configuration file: max-instances</a> for more information.</p>
203
+
<h2id="-norewrite"><code>-norewrite</code></h2>
204
+
<p>
205
+
This disables rewrite rules. Without rewrite rules, template entities won't be rewritten to macro entities, and template behaviors won't be applied, so this setting is mostly for testing and debugging.</p>
This overrides the log level setting from the current configuration file. Available log levels are <code>off</code>, <code>minimal</code>, <code>error</code>, <code>warning</code>, <code>info</code> (the default level) and <code>verbose</code>. See <ahref="configuration-files.html#log-level">configuration file: log-level</a> for more information.</p>
175
209
<h2id="input_path"><code>INPUT_PATH</code></h2>
176
210
<p>
177
-
This specifies the map file that must be processed by MESS. Supported formats are <code>.map</code>, <code>.rmf</code> and <code>.jmf</code>. The output format is always <code>.map</code>. This argument must come after all the other arguments (but before <code>OUTPUT_PATH</code>).</p>
211
+
This specifies the map file that must be processed by MESS. Supported formats are:<code>.map</code>, <code>.rmf</code> and <code>.jmf</code>. This argument must come after all the other arguments (but before <code>OUTPUT_PATH</code>).</p>
178
212
<p>
179
-
If the input file is a <code>.map</code> file and if no output path is set, then the input file will be overwritten.</p>
213
+
If the input file is a <code>.map</code> file and if no output path is set, then the input file will be overwritten. If the input file is a different format and if no output path is set, then a <code>.map</code> file with the same name as the input file will be created.</p>
180
214
<h2id="output_path"><code>OUTPUT_PATH</code></h2>
181
215
<p>
182
-
This tells where MESS will save the resulting map file. Specifying a custom output path is useful if you want to prevent MESS from overwriting the input file. This argument must come after all the other arguments.</p>
216
+
This tells where MESS will save the resulting map file. Specifying a custom output path is useful if you want to prevent MESS from overwriting the input file. This argument must come after all the other arguments. Supported formats are: <code>.map</code>, <code>.rmf</code> and <code>.jmf</code>.</p>
0 commit comments