Configuration

How to modify the configuration


You can modify the MoreCommands configuration in a config file called config.cfg (located in "minecraft_installation_folder/ config/morecommands"). The syntax for the file is the following: "SETTING=VALUE" which means that each line there is an identifier (e.g. "welcome_message") and the corresponing value after an equal sign. Some settings have to do with the so called "handshake". To use them I will shortly explain, what that is:

What is a "handshake"
Everytime you join a server which has MoreCommands installed, the server will send a message to the client requesting it to send a message back This is called a handshake and is needed to be sure if the client has the mod installed. If the client doesn't receive a handshake packet from the server or the other way around the client/server knows the the other side doesn't have the mod installed. This is important for some commands.

The settings are currently:

  • welcome_message
    Set the value to "true" or to "false" to tell the mod whether it shall displayer the loaded message ("MoreCommands vX.Y loaded")

  • enableGlobalVars
    Set the value to "true" or to "false" to tell the mod whether global variables should be allowed

  • enablePlayerVars
    Set the value to "true" or to "false" to tell the mod whether custom player variables should be allowed

  • enableGlobalAliases
    Set the value to "true" or to "false" to tell the mod whether global aliases should be allowed

  • enablePlayerAliases
    Set the value to "true" or to "false" to tell the mod whether custom player aliases should be allowed

  • serverMustHaveMod
    If this is set to "true" the client won't connect to any server that doesn't have MoreCommands installed

  • clientMustHaveMod
    If this is set to "true" the server won't accept any connection to clients that don't have MoreCommands installed

  • searchUpdates
    Set the value to "true" or to "false" to tell the mod whether it should search updates

  • startupTimeout
    Has to be a time in seconds, defaults to 10. On the client side startup commands are executed as soon as the client receives a
    handshake packet. But what is if the server doesn't have MoreCommands installed? If this is the case, the startup commands
    would never be executed. That's why there is a timeout which is 10 by default. You can modify this timeout with this setting.

  • startupCommands
    Specifies server executed startup commands. See Startup Commands fore more details

  • startupDelay
    Has to be a positive number (in seconds). Specifies the time to delay execution of startup commands

  • retryHandshake
    Sometims the handshake packet that the client sends back to the server doesn't arrive there. I have no explanation why this
    happens butthis is bad because the entire handshake fails because of that. If you set this setting to "true" or to "false"
    you can tell the mod toretry the handshake if it failed or not to do so, by default handshakes are retried.

  • handshakeRetries
    Has to be a number, defaults to 3. Tells the mod how often handshakes shall be retried if they failed.
    Works only if retryHandshake is set to "true".

  • handshakeTimeout
    Has to be a number, defaults to 10. Tells the mod how long in seconds it should wait before it makes the next attempt to
    do a handshake. Works only if retryHandshake is set to "true".

  • xrayUPS
    Has to be a number in seconds. Tells the mod how often per second it should update xray

  • useRegexCalcParser
    Has to be either "false" or "true" (default: "true"). Tells the mod whether it should use a regular expression
    calculation parser instead of a manual one.

  • strictEnchanting
    Has to be either "false" or "true" (default: "true"). Tells the mod whether the "enchant" command
    should do various applicability checks (e.g. max level, right item, etc.)

  • useExecRequests
    Tells whether to use Command Execution Requests. This means that when the /execute command is used, this property
    determines whether the command should directly be executed for other players or whether there should be a request
    to execute the command which the player can accept or deny. This has to be either "true" or "false" (default: "false")

  • minExecRequestLevel
    This is the minimum player permission level for a player to be allowed to accept or deny command execution requests
    This has to be a positive number and defaults to 2

  • maxExecRequests
    This is the maximum of command execution requests for a player. This has to be a positive number and defaults to 5

  • execRequestTimeout
    Tells after which time (in seconds) a command execution request times out. After that time, the request is automatically denied

  • prefixChannelName
    This has to be either "true" or "false" and tells whether the name of a Chat Channel should be prefixed before any message
    which is distributed on that channel (See Chat Channels for more details)