Nous allons voir l'installation de Metamod Source :
Exemple : notre installation se base sur l'utilisateur userjeux et le répertoire serveur de jeux se trouve dans le répertoire de l'utilissateur comme suite .
/home/userjeux/jeux/steam/css/serveur_1
Nous allons voir l'installation de UNRAR sous linux :
#apt-get install unrar
Installation de Metamod Source :
Metamod est un plugin permettant de faire fonctionner des Mod de jeu comme GunGame, V.I.P mod, GoreMod, ZombieMod, Deathmatch et bien d'autre.
Télécharger Metamod puis uploader metamod_1_10-linux.tar.gz dans /home (par exemple) puis le dézippé :
# tar -xvzf metamod_1_10-linux.tar.gz
Vous obtenez le dossier metamod_1_10 dans lequel se trouve le dossier addons.
1- Si le dossier addons EXISTE : copier seulement son contenu dans css/cstrike/addons comme ceci
#cp -R /home/metamod_1_10/addons/metamod /home/userjeux/jeux/steam/css/serveur_1/css/cstrike/addons
2- Si le dossier addons N'EXISTE PAS : copier le répertoire addons dans css/cstrike/ comme ceci
#cp -R /home/metamod_1_10/addons /home/userjeux/jeux/steam/css/serveur_1/css/cstrike/
-< INSTALLATION >-
Éditez le fichier gameinfo.txt dans css/cstrike/
#nano /home/userjeux/jeux/steam/css/serveur_1/css/cstrike/gameinfo.txt
et ajouter cette ligne (en rouge) comme ci dessous. (ATTENTION lors d'une mise à jour STEAM, le fichier gameinfo.txt est remplacé par celui d'origine, donc, vous devez rajouter cette ligne après chaque mise à jour STEAM)
GameBin |gameinfo_path|addons/metamod/bin
Fichier gameinfo.txt
"GameInfo" { game "Counter-Strike Source" title "COUNTER-STRIKE'" title2 "source" type multiplayer_only nomodels 1 nohimodel 1 nocrosshair 0 advcrosshair 3 bots 1 hidden_maps { "test_speakers" 1 "test_hardware" 1 } nodegraph 0
FileSystem { SteamAppId 240 // This will mount all the GCFs we need (240=CS:S, 220=HL2). // // Setup engine search paths. // // If a search path contains "_english", and the current language is not english, then // another search path will be inserted above the english one by replacing "_english" with // the appropriate language. // // To debug how the engine has parsed this file, type "path" at the console. // // Search paths are relative to the base directory, which is where hl2.exe is found. // // |gameinfo_path| points at the directory where gameinfo.txt is. // |all_source_engine_paths| points at the directory cintaining HL2 shared content. // SearchPaths {
// First, mount all user customizations. This will search for VPKs and subfolders // and mount them in alphabetical order. The easiest way to distribute a mod is to // pack up the custom content into a VPK. To "install" a mod, just drop it in this // folder. // // Note that this folder is scanned only when the game is booted. game+mod cstrike/custom/*
// We search VPK files before ordinary folders, because most files will be found in // VPK and we can avoid making thousands of file system calls to attempt to open files // in folders where they don't exist. (Searching a VPK is much faster than making an operating // system call.) game+mod cstrike/cstrike_english.vpk game+mod cstrike/cstrike_pak.vpk
game |all_source_engine_paths|hl2/hl2_textures.vpk game |all_source_engine_paths|hl2/hl2_sound_vo_english.vpk game |all_source_engine_paths|hl2/hl2_sound_misc.vpk game |all_source_engine_paths|hl2/hl2_misc.vpk GameBin |gameinfo_path|addons/metamod/bin
platform |all_source_engine_paths|platform/platform_misc.vpk
// Now search loose files. We'll set the directory containing the gameinfo.txt file // as the first "mod" search path (after any user customizations). This is also the one // that's used when writing to the "mod" path. mod+mod_write+default_write_path |gameinfo_path|.
// Add the cstrike directory as a game search path. This is also where where writes // to the "game" path go. game+game_write cstrike
// Where the game's binaries are gamebin cstrike/bin
// Last, mount in shared HL2 loose files game |all_source_engine_paths|hl2 platform |all_source_engine_paths|platform
// Random files downloaded from gameservers go into a seperate directory, so // that it's easy to keep those files segregated from the official game files // or customizations intentially installed by the user. // // This directory is searched LAST. If you visit a server and download // a custom model, etc, we don't want that file to override the default // game file indefinitely (after you have left the server). Servers CAN have // custom content that overrides the default game files, it just needs to be // packed up in the .bsp file so that it will be mounted as a map search pack. // The map search pack is mounted at the top of the search path list, // but only while you are connected that server and on that map. game+download cstrike/download } } }
|
Sauvegarder.
EXEMPLE
Si vous avez installé MANI_ADMIN_PLUGIN :
Editez le fichier css/cstrike/addons/metamod/metaplugins.ini
#nano css/cstrike/addons/metamod/metaplugins.ini
et ajouter à la fin du fichier la ligne ci-dessous.
addons/mani_admin_plugin/bin/mani_admin_plugin_mm
Ce qui nous donne :
fichier metaplugins.ini
;If your plugin came with a .vdf file, you do not need to use this file. ; ;List one plugin per line. Each line should contain the path to the plugin's binary. ;Any line starting with a ';' character is a comment line, and is ignored. ; ;You do not need to include the _i486.so or .dll part of the file name. Example: ; addons/sourcemod/bin/sourcemod_mm ;You may also put an alias in front of the file, for example: ; sm addons/sourcemod/bin/sourcemod_mm ;Will allow you to use "meta load sm" from the console. ; ;********* LIST PLUGINS BELOW *********** addons/mani_admin_plugin/bin/mani_admin_plugin_mm
|
Sauvegarder
Rebooter votre serveur de jeu
