jhxp

How to install the MTA:SA Linux server on Debian 6.0 (squeeze) and 7.0 (wheezy) on both 32 and 64bit flavours Here is the tutorial for installing MTA:SA linux server on a freshly installed Debian 6.0 (also named squeeze) or Debian 7.0 (wheezy). This tutorial covers both the 32bit and the 64bit flavours of these Debian OSes. Note: this tutorial is based on a MTA:SA 1.3.1 / 1.3.2 server, but it should be fine for future versions as well. Just edit the version numbers accordingly and use correct URLs for newer files. Requirements In order to install MTA:SA linux server, you need to have a Debian 6.0 or 7.0 linux machine with shell access (ssh). It does not matter whether it is physical or virtual, however a physical dedicated server is recommended for performance. Minimal hardware server requirements: * Intel/AMD (x86-compatible) CPU with at least 1.0GHz of core speed * at least 192MB of RAM * at least 200MB of free disk space * an active network connection with all the needed ports opened - server can be set up to run on LAN or on the Internet You will also need a root access for installing system packages. If you do not have it, you can ask your server administrator to install the packages for you - that should be fine as well as it is just a one-time action. Lastly, you should have some basic knowledge of the Linux operating system in order to install and use your MTA:SA server on Linux. I will explain most of the commands in shell code comments - #comment, but I assume that you already know how to perform simple file operations (such as copying, renaming, deleting or editting files) on a Linux shell prompt. 1. How to find out which OS flavour you have Simply log in to your shell account, then type this command in the shell prompt: uname -a; #show operating system information cat /etc/debian_version; #show Debian version number If you have a 32-bit Debian 6.0, this is what you will get: However if you have a 64-bit Debian 6.0, you will get this: It looks a bit different for Debian 7.0: 32bit: 64bit: In summary, if you get i686 in a uname -a reply, it means you have a 32bit Debian, and if you get x86_64 - it means it is a 64-bit Debian. If you receive a different reply (like armel, mips or other) , you can not run the mtasa server. 2. Installing the required software packages Okay, now that you know what OS version and flavour you have, you have to install the needed system packages to your Debian. You can find the instructions for each version below. a) Debian 6.0 "squeeze" The steps are the same for both flavours. 32-bit - list of required packages 64-bit - list of required packages You need to have root permissions to do the following commands. Use the right list as shown above instead of LIST_OF_PACKAGES (if you have a 32bit Debian, you only install the packages listed for 32bit; if you have 64bit Debian, you only install the packages list for 64bit): apt-get update; #first, lets update the list of packages apt-get upgrade; #upgrade the currently installed packages if needed; type Y when asked apt-get -y install LIST_OF_PACKAGES; #install the required packages for your flavour b) Debian 7.0 "wheezy" The steps are different for 32 bit and 64 bit flavours: * 32bit - list of required packages You need to have root permissions to do the following commands. Use the list shown above instead of LIST_OF_PACKAGES: apt-get update; #first, lets update the list of packages apt-get upgrade; #upgrade the currently installed packages if needed; type Y when asked apt-get -y install LIST_OF_PACKAGES; #install the required packages -------------------- * 64-bit - list of required packages You need to have root permissions to do the following commands. Use the list shown above instead of LIST_OF_PACKAGES: apt-get update; #first, lets update the list of packages apt-get upgrade; #upgrade the currently installed packages if needed; type Y when asked dpkg --add-architecture i386; #add the i386 architecture so the ia32-libs package can be installed apt-get update; #update the list of packages so the ia32-libs package is included in the list apt-get -y install LIST_OF_PACKAGES; #install the required packages (eg. 'apt-get -y install zip unzip ia32-libs lib32ncursesw5 lib32readline5 screen' for 32bit debian.) Additional packages might be needed for the third party server modules. Should you want to use one, please consult the documentation for such module to find out which packages are required. 3. Installing the MTA:SA server You are now ready to install the MTA:SA server application to your machine. Go to your home directory and download the server files. You can find the most up-to-date needed files here: http://linux.multitheftauto.com/ (linux server, config files and resources) Make sure to modify the version numbers and URLs! cd ~; #go to your home directory mkdir mtasa; #create a directory for the mtasa server cd mtasa; #go to the newly created directory #-INSERT CORRECT URLs HERE- wget -O mtasa-linux-server.tar.gz [url=http://linux.multitheftauto.com/dl/132/multitheftauto_linux-1.3.2.tar.gz;]http://linux.multitheftauto.com/dl/132/multithef ... .2.tar.gz;[/url] #download the main MTA:SA linux server archive and save it as mtasa-linux-server.tar.gz wget [url=http://linux.multitheftauto.com/dl/132/baseconfig.tar.gz;]http://linux.multitheftauto.com/dl/132/baseconfig.tar.gz;[/url] #download the server config files wget -O mtasa-resources.zip [url=http://mtasa-resources.googlecode.com/files/mtasa-resources-r926.zip;]http://mtasa-resources.googlecode.com/f ... -r926.zip;[/url] #download the server resources archive and save it as mtasa-resources.zip #----------------------------------- tar -zxf mtasa-linux-server.tar.gz; #uncompress the MTA:SA server archive mv multitheftauto_linux-1.3.2 mtasa-server; #renames the server directory unzip -q mtasa-resources.zip -d mtasa-server/mods/deathmatch/resources/; #uncompress the server resources to the correct MTA:SA server directory tar -zxf baseconfig.tar.gz; #uncompress default server configuration files mv baseconfig/* mtasa-server/mods/deathmatch; #move default server configuration files to the correct MTA:SA server directory rmdir baseconfig; #remove a now empty directory rm baseconfig.tar.gz mtasa-resources.zip mtasa-linux-server.tar.gz; #removes the installation files - they are not needed anymore 4. Configuring the server You should configure the server before you run it. Go to your home directory ( ~/ ), then go to mtasa/mtasa-server/mods/deathmatch directory. If you are unsure how to do it, you can use the description below: cd ~; #go to your home directory cd mtasa/mtasa-server/mods/deathmatch; #go to the newly created directory nano mtaserver.conf; #start the NANO text editor and load the mtaserver.conf file Now make some changes to the file (eg. change the server name), then save it by holding the Control key, then pressing the O key. You will be asked for a filename - just press the Enter key to overwrite the file. However, if you made a mistake and do not want to save the file, hold the Control key and press C key, then hold Control key, press X key, and then N key. You can start over by launching the nano editor again as above. Once you have configured the server, you are ready to start it. 5. Running the server cd ~; #go to your home directory cd mtasa/mtasa-server/; #go to the mtasa server directory ./mta-server; #start the server If it works okay, it will look like this: (the text 'Server started and is ready to accept connections' will be shown in the console) Alright, now if you disconnect from the shell, your server will be stopped as well. If you want to keep your server to be running when you log out from your shell, you need to stop it now by typing 'quit' in the server console (or by pressing Control key, then C / Ctrl+C). Start it instead by using this: cd ~; #go to your home directory cd mtasa/mtasa-server/; #go to the mtasa server directory screen -dmS mtasa ./mta-server; #start the server using the SCREEN application - screen name: mtasa, start screen in background This will make the server start in the background. If you need to open the server console, you can do that by using this command: screen -r PROCESS_ID #reattaches to the specified screen session To find out the screen process id, you can use screen -ls command: (if there is just one screen running, you can reattach to it by just using the screen -r command) If you need to put your server to keep running in the background again, you can detach from your screen session by using the Ctrl+A+D hotkey, or just by closing PuTTY. To stop the server, reattach to your screen session and type 'quit' in the server console (might want to repeat it few times if it does not work), then type 'exit' in the screen session console. If the server has crashed, you need to stop the screen session the server is running in. Use the screen -ls command to find the process id of the session, then use the kill PROCESS_ID to stop it (or kill -9 PROCESS_ID if it did not stop it). 6. Finished! That is all. Your MTA:SA server is all set up and running properly. Please make sure you read the general Server Manual wiki article to understand how the server works and how to use it.

Does it happen with any other games (or SA singleplayer)?

There you go. Enjoy. viewforum.php?f=168

Partial lists can be found here: https://wiki.multitheftauto.com/wiki/Changes_in_1.3.2 https://bugs.mtasa.com/changelog_page.php

If you need a new client, you can download it here: https://nightly.multitheftauto.com/ There are several versions available - either a 1.3.1 release candidate, which is fully compatible with the current version, or the development builds.

It may be caused by ssl. See if the regular http page ( https://wiki.multitheftauto.com ) works for you. https://www.mtasa.com as well as other mta pages do not work on Opera at the moment (v12.14, at least for me).

Done.

There is no need for the MLMs for the time being. You can request it again once there is enough activity in this subforum. Should there be an issue with a post or topic, please pm a moderator or use the Report this post button.

Enjoy. viewforum.php?f=166

You can read the interview here: http://www.gamers-association.com/2013/ ... interview/

Happy holidays! It does not look like the Mayans were right, so we can post another status update. And, we do have something interesting to tell indeed. We have an important announcement to make. On Sunday, 4th of November, 2012, we reached the moment we have longed for years. On that day, at 17.30 UTC we had over ten thousand concurrent players online on all MTASA servers around the world. That was more than the number of players combined playing GTA4 and EFLC on Steam at the time, or other hit titles such as Call of Duty: Black Ops or Total War: Shogun 2 (according to Steam Stats). This shows, that after all these years there is still a lot of interest in the older GTA games, especially the will to play them online with friends. This also shows that you guys appreciate what we do, and that makes us very happy! The current record is 11128 concurrent players, set on 22nd December, so there is still room to improve. We have made some progress towards the next release during these few months. Here is the list of changes made by our developers and contributors since 1.3.1: - Integrated GTA:SA downgrader into MTA:SA installer and added support for the downgrader for few more GTA:SA versions (including GamersGate v1.01) - Added vehicle component movement functions ( http://code.google.com/p/mtasa-blue/sou ... ail?r=4715 ) - Fixes for client and server crashes (including crashes related with setFarClipDistance() function, server closing, onResourceStop() and onClientColShapeHit events, and more) - Added a fix for dark cars - Fixed excessive CPU usage when the player is in a vehicle and the camera is pointing down - Engineless NRG-500 Variant should be fixed properly this time - Updated http download manager in the MTA:SA client - Added heat haze setting - Added readable depth buffer for shaders to access ( https://wiki.multitheftauto.com/wiki/DepthBuffer ) - Added getPlayerOxygenLevel, setPlayerOxygenLevel, engineGetModelLODDistance functions - Conformed client console log date format to ISO 8601 - Applied patches made by community members - Kenix (volk-rus), Jusonex, [GP_A]XetaQuake, rafalh - Included a new code signing certificate - Introduced a new account passwords hashing algorithm and added a sha256() hashing function More detailed list: http://code.google.com/p/mtasa-blue/sou ... start=4613 Additionally, a new resource was added to the resource pack: an Ingame Performance Browser. There were a handful of fixes and updates to to other resources too. http://code.google.com/p/mtasa-resource ... &start=882 r875+ That is all for now! Enjoy your Winter break.

Great, thanks for notifying us, Samer, but there was no need for a backseat moderation attempt to go along with that.

How about Johnline's tutorial? http://www.moddb.com/mods/multi-theft-a ... s-tutorial

cameron.sanchez , please refer to this thread: viewtopic.php?f=104&t=49114 ------------------------------------------------------------------------- To all other users: Please keep in mind that this patcher is no longer necessary for MTA:SA 1.5 and above. To downgrade your GTASA install, simply run the MTA:SA installer and it will do all the magic by itself. However, if the installer is not able to downgrade your GTASA copy due to an unknown version of your GTASA executable, please contact us and we will try to make it compatible with your version.

Yeah, yeah. No fighting, please.

Dodatkowo: https://nightly.multitheftauto.com/ports/

If you are not willing to read our advices, creating another thread about the same thing is not going to help. viewtopic.php?p=479260#p479260

https://wiki.multitheftauto.com/wiki/Ser ... forwarding Next time read it more carefully.

There is hardly anything personal in there, but okay. Posting it on forums might get more people to look at your problem.

Try using it then.

Sorry to say, but your machine is outdated and doesn't even meet GTA:SA minimal requirements (to be precise, the graphics card does not). I am kinda surprised that the graphics card still works, as technologically-wise it 's over 10 years old. https://wiki.multitheftauto.com/wiki/Cli ... quirements I recall playing GTA:SA on this card back in 2005, and it had a hard time with providing a good enough performance. You might try tweaking it and your OS for some extra performance bits, but probably that's all you can count on.

Are you using the official converter? http://files.mtasa.com/apps/1.0/raceconv.zip

https://wiki.multitheftauto.com/wiki/How_you_can_help

Mmm... that looks interesting. Wonder what could we add to it to make it more useful. Maybe latest resources/community integration?

What exactly are you having a problem with?