Jump to content

List of command-line options: Difference between revisions

From fCraft Wiki
No edit summary
mNo edit summary
Line 2: Line 2:


{|class="wikitable"
{|class="wikitable"
| align="right" | <code>--path=<path></code>
| align="right" style="min-width:130px" | <code>--path=<path></code>
| Working path (directory) that fCraft should use. If the given path is relative, it's computed against the location of fCraft.dll. If no path is given, location of fCraft.dll is used.
| Working path (directory) that fCraft should use. If the given path is relative, it's computed against the location of fCraft.dll. If no path is given, location of fCraft.dll is used.
|-
|-

Revision as of 08:01, 28 November 2012

In addition to many settings stored in config.xml, fCraft has several special options that can only be set via command-line switches:

--path=<path> Working path (directory) that fCraft should use. If the given path is relative, it's computed against the location of fCraft.dll. If no path is given, location of fCraft.dll is used.
--logpath=<path> Path (directory) where the log files should be placed. If the given path is relative, it's computed against the working path.
--mappath=<path> Path (directory) where the map files should be loaded from/saved to. This setting overrides MapPath key in config.xml. If the given path is relative, it's computed against the working path.
--config=<path> Path (file) of the configuration file, including the file name (typically "config.xml"). If the given path is relative, it's computed against the working path.
--norestart If this flag is present, fCraft will shutdown whenever it would normally restart (e.g. automatic updates or /restart command). This may be useful if you are using an auto-restart script or a process monitor. Even though the server will not restart, it still exits with a restart exit-code.
--exitoncrash If this flag is present, fCraft front-ends will exit at once in the event of an unrecoverable crash, instead of showing a message and prompting for user input. This is preferable when fCraft is managed automatically rather than manually.
--nolog If this flag is present, all logging is disabled.
--noconsolecolor If this flag is present, ServerCLI will not use any color codes in its console output.