Créer son serveur sur MTA

!TASO

Membre
Inscription
11 Juillet 2013
Messages
318
Réactions
24
Points
9 066
Yop tous le monde ! Donc je décide de créer ce petit tuto pour vous aider (j'espère ) à créer votre propre serveur ! Bien sur le serveur sera sous votre connexion, si vous héberger ( Sur un hébergeur ) votre serveur sa sera pratiquement pareil sauf que ça se fera à partir du FTP et non votre dossier mta.
Donc allez c'est partie !

Première étape lorsque vous avez télécharger mta assurez vous d'avoir choisie " Client & Server " ( Si ce n'est pas le cas re-télécharger MTA et choisissez l'option " Server " seulement ). Ensuite il vous faudra hamachi. ( Facilement trouvable sur google ). Si vous avez tous ça vous pouvez créer votre serveur en suivant le tutoriel ! Je vous conseille aussi de télécharger notepad++.

Deuxième étapes :
Rendez-vous ou vous avez installer MTA, Ensuite allez dans le dossier server, ici on peut voir plusieurs truc :
Un dossier " dumps " qui j'avoue je ne sait pas a quoi il sert, ensuite il y'a plusieurs dll et MTA server.exe qui nous servira a démarrez notre serveur lorsque l'on aura tous réglez !
Maintenant allez dans le dossier mods & ensuite deathmatch, c'est ici que tous se passe pratiquement.
Je ne vais pas vous expliquez le rôle de tous les dossier cars leurs nom explique déjà assez a quoi ils servent.

Ouvrez hamachi et créez un réseau, peut importe le nom & mdp.

Ouvrez le fichier mtaserver.conf ( Je vous conseille Notepad++ )
Et normalement vous aurez ceci :
<config>

<!-- This parameter specifies the name the server will be visible as in the ingame server browser
and on Game-Monitor. It is a required parameter. -->
<servername>Le nom de votre serveur</servername>

<!-- ONLY USE THIS PARAMETER IF YOU ARE SURE OF WHAT YOU ARE DOING - it is generally only
needed for professional servers and should be left blank otherwise.
This parameter specifies the IP to use for servers that have multiple IP addresses. If left
blank, it will default to server's standard local IP address. -->
<!-- SERVERIP SHOULD BE LEFT BLANK UNLESS YOU ARE SURE OF WHAT YOU ARE DOING -->
<serverip>Votre IPv4 ( Il faut la copier depuis hamachi ( Clic droit sur votre pseudo ) )</serverip>
<!-- WARNING: SETTING serverip AND THEN ASKING FOR SUPPORT CAN CAUSE DEATH OR INJURY -->

<!-- This parameter specifies the UDP port on which the server will be accepting incoming player
connections; default value: 22003. It is a required parameter. -->
<serverport>22003 ( Port de base, laissez le tel quel )</serverport>

<!-- This parameter specifies the number of maximum player slots available on the server; default
value: 32. It is a required parameter. -->
<maxplayers>32 ( Le nombre max de joueurs que vous voulez sur votre serveur je vous conseille maximum 10, car c'est sur votre connexion )</maxplayers>

<!-- This parameter specifies whether the builtin http server is enabled.
The builtin http server is used for webadmin and (if httpdownloadurl is empty) resource downloads.
Values: 0 - disabled , 1 - enabled ; default value: 1. Optional parameter. -->
<httpserver>1</httpserver>

<!-- This parameter specifies the TCP port on which the server will be accepting incoming http
connections. It can be set to the same value as <serverport>. It is a required parameter
if <httpserver> is set to 1. -->
<httpport>22005</httpport>

<!-- If set, this parameter specifies the external URL from which clients will be able to download
needed resources ingame. If not set (or the external URL files are incorrect), resource downloads
are switched to the internal http server. -->
<httpdownloadurl></httpdownloadurl>

<!-- This parameter specifies whether the client files for hosting on an external web server should be
automatically copied into mods/deathmatch/resource-cache/http-client-files/
Only relevant if <httpdownloadurl> is set.
Values: 0 - disabled , 1 - enabled ; default value: 1. Optional parameter. -->
<httpautoclientfiles>1</httpautoclientfiles>

<!-- This parameter is deprecated. Please use httpmaxconnectionsperclient instead-->
<httpconnectionsperclient></httpconnectionsperclient>

<!-- This parameter limits the number of http connections each client can make. Depending on the type
of http server that is used, a lower figure may reduce download timeouts.
Available range: 1 to 8. -->
<httpmaxconnectionsperclient>5</httpmaxconnectionsperclient>

<!-- This parameter limits the number http connections that an IP can initiate over a short period of time.
Available range: 1 to 100. default value: 20 -->
<httpdosthreshold>20</httpdosthreshold>

<!-- This parameter lists the IP addresses that are to be excluded from http dos threshold limits.
e.g. 88.11.22.33,101.2.3.4 -->
<http_dos_exclude></http_dos_exclude>

<!-- By default, the server will block the use of customized GTA:SA data files. -->
<!-- To allow specific client files, add one or more of the following: -->
<!-- <client_file name="data/carmods.dat" verify="0"/> -->

<!-- Comma separated list of disabled anti-cheats.
For details see
e.g. To disable anti-cheat #2 and #3, use: 2,3 -->
<disableac></disableac>

<!-- Comma separated list of enabled special detections.
A special detection is a type of anti-cheat for (usually) harmless game modifications.
Competitive servers may wish to enable special detections, but most servers should leave this setting blank.
For details see
e.g. To enable special detection #12 use: 12 -->
<enablesd></enablesd>

<!-- This parameter specifies whether communications between the server and client is encrypted.
Encryption can help prevent network data being viewed and modified.
Values: 0 - disabled , 1 - enabled ; default value: 1. Optional parameter. -->
<networkencryption>1</networkencryption>

<!-- Minimum client version. Clients with a lower version will not be allowed to connect. After
disconnection, clients will be given an opportunity to download an update.
If left blank, this setting is disabled and there are no restrictions on who can connect.
Version numbers are described here:
and look like this: 1.1.0-9.03100.0
Note that this setting only determines if the client should be prompted to update. The actual
build number they receive will be the highest available. See: -->
<minclientversion>1.3.5-9.06250</minclientversion>

<!-- This parameter specifies if/when the <minclientversion> setting is automatically updated.
Keeping <minclientversion> updated can help reduce cheating.
Note: The instant setting (2) is only recommened for competitive servers.
Values: 0 - disabled, 1 - enabled (delayed by a few days), 2 - enabled (instant) ; default value: 1. -->
<minclientversion_auto_update>1</minclientversion_auto_update>

<!-- Recommended client version. When connecting, if clients have a lower version, they will be given
the option to download an update. If left blank, this setting is disabled.
Note that this setting only determines if the client should be prompted to update. The actual
build number they receive will be the highest available. See: -->
<recommendedclientversion></recommendedclientversion>

<!-- This parameter can be used to make the server report to Game-Monitor master servers, allowing it to
be visible in the ingame server browser. An additional UDP port needs to be available for this to
work (value from <serverport> + 123 , so on a default <serverport> value 22003 the right port
will be 22126 ). Available values: 0 - disabled , 1 - enabled. Optional parameter, defaults to 0. -->
<ase>1</ase>

<!-- This parameter allows you to disable LAN broadcasting. -->
<donotbroadcastlan>0</donotbroadcastlan>

<!-- If set, players will have to provide a password specified below, before they can connect to the
server. If left blank, server doesn't require a password from them. -->
<password>Ici vous pourrez mettre un mot de passe sur votre serveur si vous le souhaitez</password>

<!-- This parameter reduces the server's bandwidth usage by using various optimizations.
Values: none, medium or maximum ; default value: medium -->
<bandwidth_reduction>medium</bandwidth_reduction>

<!-- The following ???_sync_interval parameters determine the time in milliseconds between certain
network packets being sent. More information on how each settings works is available here:
-->
<!-- Player sync interval. Default: 100 -->
<player_sync_interval>100</player_sync_interval>
<!-- Lightweight (player) sync interval. Used when players are far apart. Default: 1500 -->
<lightweight_sync_interval>1500</lightweight_sync_interval>
<!-- Camera sync interval. Default: 500 -->
<camera_sync_interval>500</camera_sync_interval>
<!-- Ped sync interval. Default: 400 -->
<ped_sync_interval>500</ped_sync_interval>
<!-- Unoccupied_vehicle sync interval. Default: 400 -->
<unoccupied_vehicle_sync_interval>1000</unoccupied_vehicle_sync_interval>
<!-- Keysync mouse rotation sync interval. For limiting key sync packets due to mouse movement. Default: 100 -->
<keysync_mouse_sync_interval>100</keysync_mouse_sync_interval>
<!-- Keysync analog movement sync interval. For limiting key sync packets due to joystick movement. Default: 100 -->
<keysync_analog_sync_interval>100</keysync_analog_sync_interval>

<!-- This parameter can improve the reliability of shots when using certain weapons. However, it uses more bandwidth.
Values: 0 - disabled , 1 - enabled ; default value: 0. -->
<bullet_sync>0</bullet_sync>

<!-- This parameter sets the amount of extrapolation that clients will apply to remote vehicles. This can reduce
some of the latency induced location disparency by predicting where the remote vehicles will probably be.
Depending on the gamemode, an incorrect prediction may have a negative effect. Therefore this setting
should be considered experimental.
Available range: 0 to 100. Default - 0 -->
<vehext_percent>0</vehext_percent>

<!-- This parameter places a limit on how much time (in milliseconds) the vehicle extrapolation will attempt to
compensate for.
Only relevant if <vehext_percent> is greater than zero.
Available range: 50 to 500. Default - 150 -->
<vehext_ping_limit>150</vehext_ping_limit>

<!-- This parameter can reduce the delay of player actions appearing on remote clients by 2 frames (approx 50ms).
Due to the impact this may have on shot lag compensation, it should be considered experimental.
Values: 0 - disabled , 1 - enabled ; default value: 0. -->
<latency_reduction>0</latency_reduction>

<!-- Specifies the location and file name of this servers unique private key.
This is used to prevent private files saved on the client from being read by other servers.
More infomation about client private files can be found here:
Keep a backup of this file in a safe place. Default value: server-id.keys-->
<idfile>server-id.keys</idfile>

<!-- Specifies the location and name of the main server log file. If left blank, server won't be saving this file. -->
<logfile>logs/server.log</logfile>

<!-- As well as the main log file, login successes and failures are logged here for easy reviewing of security issues.
If left blank, this file is not used -->
<authfile>logs/server_auth.log</authfile>

<!-- Specifies the location and name of the file used to log database queries.
The server command 'debugdb' sets the amount of logging. -->
<dbfile>logs/db.log</dbfile>

<!-- Specifies the location and name of the file used to log loadstring function calls.
If left blank or not set, no logging is done. -->
<!-- <loadstringfile>logs/loadstring.log</loadstringfile> -->

<!-- This parameter specifies the location and name of the Access Control List settings file. If left
blank, server will use acl.xml file, located in the same folder as this configuration file. -->
<acl>acl.xml</acl>

<!-- Specifies the location and name of the debugscript log file. If left blank, server won't be saving this file. -->
<scriptdebuglogfile>logs/scripts.log</scriptdebuglogfile>

<!-- Specifies the level of the debugscript log file. Available values: 0, 1, 2, 3. When not set, defaults to 0. -->
<scriptdebugloglevel>0</scriptdebugloglevel>

<!-- Specifies the level of the html debug. Available values: 0, 1, 2, 3. When not set, defaults to 0. -->
<htmldebuglevel>0</htmldebuglevel>

<!-- Specifies the frame rate limit that will be applied to connecting clients.
Available range: 25 to 100. Default: 36. -->
<fpslimit>36 ( Ici c'est le fps max, je vous conseille vers les 60 pour une bonne fluidité sur votre serveur )</fpslimit>

<!-- Specifies whether or not players should automatically be logged in based on their IP adresses -->
<autologin>0</autologin>

<!-- This parameter specifies whether or not to enable player voice chat in-game
Values: 0 - disabled , 1 - enabled -->
<voice>0</voice>

<!-- This parameter specifies the sample rate for voice chat. 'voice' parameter must be set to 1 for this to be effective.
Higher settings use more bandwidth and increase the sampling quality of voice chat
Values: 0 - Narrowband (8kHz), 1 - Wideband (16kHz), 2 - Ultrawideband (32kHz). Default - 1 -->
<voice_samplerate>1</voice_samplerate>

<!-- This parameter specifies the voice quality for voice chat. 'voice' parameter must be set to 1 for this to be effective.
Higher settings use more bandwidth and increase the the overall quality of voice chat
Available range: 0 to 10. Default - 4 -->
<voice_quality>4</voice_quality>

<!-- Specifies the voice bitrate, in bps. This optional parameter overrides the previous two settings.
If not set, MTA handles this automatically. Use with care. -->
<!-- <voice_bitrate>24600</voice_bitrate> -->

<!-- This parameter specifies the path to use for a basic backup of some server files.
Note that basic backups are only made during server startup. Default value: backups -->
<backup_path>backups</backup_path>

<!-- This parameter specifies the number of days between each basic backup.
Backups are only made during server startup, so the actual interval may be much longer.
Setting backup_interval to 0 will disable backups
Available range: 0 to 30. Default - 3 -->
<backup_interval>3</backup_interval>

<!-- This parameter specifies the maximum number of backup copies to keep.
Setting backup_copies to 0 will disable backups
Available range: 0 to 100. Default - 5 -->
<backup_copies>5</backup_copies>

<!-- This parameter specifies when the internal sqlite databases should be defragmented.

Values: 0 - Never, 1 - On server start only after basic backup, 2 - On server start always. Default - 1 -->
<compact_internal_databases>1</compact_internal_databases>

<!-- Specifies the module(s) which are loaded with the server. To load several modules, add more <module>
parameter(s). Optional parameter. -->
<!-- <module src="sample_win32.dll"/> -->
<!-- <module src="sample_linux.so"/> -->

<!-- Specifies resources that are loaded when the server starts and/or which are protected from being stopped.
To specify several resources, add more <resource> parameter(s). -->

<resource src="admin" startup="1" protected="0" />
<resource src="defaultstats" startup="1" protected="0" />
<resource src="helpmanager" startup="1" protected="0" />
<resource src="joinquit" startup="1" protected="0" />
<resource src="mapcycler" startup="1" protected="0" />
<resource src="mapmanager" startup="1" protected="0" />
<resource src="parachute" startup="1" protected="0" />
<resource src="performancebrowser" startup="1" protected="0" />
<resource src="resourcebrowser" startup="1" protected="1" default="true" />
<resource src="resourcemanager" startup="1" protected="1" />
<resource src="scoreboard" startup="1" protected="0" />
<resource src="spawnmanager" startup="1" protected="0" />
<resource src="voice" startup="1" protected="0" />
<resource src="votemanager" startup="1" protected="0" />
<resource src="webadmin" startup="1" protected="0" />

<!-- play is the default freeroam gamemode. Remove the following line to prevent it from starting. -->
<resource src="play" startup="1" protected="0" />
Ici a la place de "play" vous pourrez mettre le mode sur lequel vous voulez que votre serveur se lance, exemple : "deathmatch", "race" toujours entre " " c'est très important !

</config>
Voilà c'est a peut près tous ce que vous devez savoir sur le mtaserver.conf

Maintenant votre serveur est près ! Ce qui nous amènes a la troisièmes étapes !

Troisièmes étapes nous pouvons lancer notre serveur mes avant ça on vas se mettre admin sur notre serveur quand même !
Donc quittez en sauvegardant le mtaserver.conf pour ensuite ouvrir ( Avec notepad++ ou bloc note ) acl.xml
Pour l'acl je ne vais pas vous expliquez car c'est vraiment quelque choses de très galère a comprendre je vais juste vous expliquez comment mettre des gens admins, modérateur ou smod.
Donc vous voyez plusieurs group name mes comme on est les créateurs du serveur on ce mets admins, donc dans le group name admin vous allez ajoutez cette phrase :
<object name="user.VotrenomdecompteIG"></object>
Oui vous n'avez pas encore de compte sur votre serveur mes sa vas arrivez vous inquiétez pas !

Votre serveur est près vous pouvez maintenant l'allumer grâce au mtaserver.exe.
Connectez vous sur votre serveur, faite /register Le nom de compte que vous avez mits dans l'acl ( sans espace ) et votre mot de passe.

Ensuite /login Nomdecompte mot de passe.

Donc voilà nous venons de voir comment créer son serveur, j'éditerais ce poste pour rajouter quelque truc utile, comme ajoutez des maps, des scripts ou encore un tutoriel pour savoir comment mapper.
Si vous avez des questions/problèmes n'hésite pas à les posez :)
Merci de laissez un petit j'aime.
 

H4DZR

Membre
Inscription
31 Mai 2017
Messages
1
Réactions
0
Points
14
J'aimerais savoir comment ont peut faire un serveur MTA, pour faire du mapping avec des potes...
 

bloodz

Membre
Inscription
24 Février 2018
Messages
1
Réactions
0
Points
14
J'ai un problème : Quand j'arrive sur le serveur, je me fais kick d'entrée alors que je suis le créateur :/
 
Haut