Frequently Asked Questions

MatchEd is written in Java, so you must install, or have installed, a Java Virtual Machine (JVM) to run it. Check out The Source for JavaTM Technology to find a suitable JVM for your system.

You don't have the java executable in your PATH. Make sure that you have java installed. If Java is installed, you must add the "bin" directory inside the Java installation into the PATH of your system.

Post your question in the User Help Forum.

Any plain text editor such as notepad, emacs or even vi :)

If you have a firewall, you will have to allow the Java process access.

/msg BotNick auth Password

First, you must auth as an admin, then: /msg BotNick nick NewNick

First, you must auth as an admin, then: /msg BotNick die

This will disconnect the bot from the server and close the Java JVM

This should be a step by step guide to getting it working ... NOTE: before you proceed, you WILL need rcon access to the server.

- Start the bot :)
- auth with the bot: /msg BotName auth AdminPassword (Where BotName is the name you set in the MatchEd.properties and the AdminPassword is the value from the properties file. NOTE: you should receive a notice from the bot that you have been authed.)
- if you haven't set the rcon password in the config file, then set the game servers rcon password into the bot using a private message: rcon_password rcon-password
- type !startcs (or the command you have for CommandStartCS in the properties file) (you should receive a notice saying that the match reporting has been started)

If the auto setup was successful, you can test all is working correctly. If it failed or the test failed, then you must direct the logs from the server to the bot. Before you do this, you need to know the IP address that the bot is running from and the port configured in the properties file for InPort. Using whatever rcon tool you prefer, run these commands on the server:

rcon log on
rcon logaddress_add 999.999.999.999 27777 (Where 999.999.999.999 is the IP of the machine running MatchEd and 27777 is the port number that MatchEd is listening to (set from InPort in MatchEd.properties)

Now to test that it works

You must first turn the logging on (if not already):

  rcon log on

Then you need to send the logs to MatchEd using the "rcon logaddress_add" command; eg:

  rcon logaddress_add 999.999.999.999 27777 (Where 999.999.999.999 is the IP of the machine running MatchEd and 27777 is the port number that MatchEd is listening to; set from InPort in MatchEd.properties).

Yes, the logs are still written as normal, sending them to MatchEd as well does not change that.

Turn on server say with !serversayon (or the command configured for CommandServerSayOn). With your rcon tool: rcon say test
If everything is OK, in your channel, you should see something like: SERVER: "test"
You can also change the map.

Make sure that you have "mp_logmessages 1" set. A good place to set this is in the server.cfg file.
Or, you might simply have forgotten to turn logging on on the server side: log on or rcon log on
Or, you may have colour blocking on the channel. If you do you can take off the colour blocking flag from the channel or remove the colours from the config.

You should set the "rcon logaddress_add" command in your server.cfg file so that it will always send the logs to MatchEd.