Server Guide VC GTA MTA

 
Latest Forum Posts:
Author
Returning Member Thread
 
 

0.5 VC Server Guide

For those who are finding it hard to set up a server, then here is a guide for your own help. Its important you follow all instructions carefully to get all things adjusted correctly.

Windows 2000, Windows XP and Windows Server 2003 users must have administrator privaledges to install software. Therefore you'll need to check if you are an administrator, or you'll need to contact the administrator to install the software for you. To check, simply go to Control Panel -> User Accounts. From here you should see if you are an administrator

Download the server software. Browse to http://www.multitheftauto.com/ and go to "Archive." From here you can find the software.

Look for the server installer, not the client. For Windows users, download the package illustrated in the screenshot below.

Extracting the server setup program. Once the download is complete, double click the ZIP file on your desktop. Depending on which archiving software you are using, it should give you an option to extract the file. In my example, I'm using WinRAR. It is similar for most other software, just extract it straight to the desktop.

The setup. Run the EXE file on your desktop and you should be presented with a wizard which looks like this:

As you can see above, I'm using the default path which is already entered. You're probably best off if you leave this and let it install to the defualt directory, but if you specifically need to install it to another folder/drive, then you may browse and select the location. Complete the installation and move onto the next step.

Browse to the directory you installed the server. By defualt, it should be as follows:

Code:

C:Program FilesMulti Theft Auto

Once you are here, the folder should look (something) like this. Don't worry if you don't have all the files you see in my screenshot, this is normal.

Configuring the server. There are 2 ways to configure the server, either using the Server Config Tool. I would suggest using this as it has a GUI and is very simple to use. Double click on MTAServerConfigTool.exe and it should run. Note: you may encounter an error like the one below:

To get rid of this, simply delete MTAServerConfigTool.exe.manifest and it should sort the problem out. Run the Config Tool again and it will work.

Open mtaserver.conf with Notepad and you should see this:

From here you can edit all the settings. The only ones you should need to edit are ServerName, ServerPort, ServerPassword (if you want it private), AdminPassword and AdminPlusPassword. Of course, it's up to you what you want to do. Once you've finished editing it, save it and close it.

Running the server. After running the config tool/editing the config manually, double click on MTAServer.exe. This should bring up a DOS window with some text on like this:

This is what you are supposed to see, so don't panic. As long as this window is open, the server is running.

You may also want to apply Server Patch 1 which you can also obtain from the download page. To install the server patch one, simply download it, extract it from the ZIP file and copy the EXE into the directory where you installed the server. It should overwrite the old EXE and provides a fix to the memory leak that was first found when 0.5 was released.

If you have completed all of the above steps, your server should work. If you can connect to it but people on the Internet can't, then you may need to open the gameport through your router/firewall. The gameport is the one you specified in the config (2003 by default). If you don't know how to port forward, consult your router's manual. People without a router need not to worry about this. If you are running a firewall, there should be an option to allow direct connection on specified ports, this is where you'll need to enter the port.

If people say they can't see your server on the ASE server browser, you need to do the above except to the gameport+123 (so for example if my gameport is 2003, I need to forward 2126 so that the server can report to ASE).