No Quarter Mod
No Quarter Mod
From No Quarter Wiki
No Quarter b1.2.0 requires a valid 2.60b/d Enemy Territory installation.
Upgrade to 1.2.0
- Requires a valid No Quarter 1.1.1 installation (see below).
- Unpack the No Quarter 1.2.0 RAR archive, so you have all the files you need.
- In your "noquarter" directory, remove the old qagame and nq_bin_b1.1.1.pk3 files.
- Leave noquarter_b1.1.1.pk3 and noquarter_b1.1.0.pk3, as 1.2.0 is an upgrade, not a full installation, and still requires it.
- Place the new binaries you extracted from the RAR into the "noquarter" directory: noquarter_b1.2.0.pk3 and nq_bin_b1.2.0.pk3
- Add following pk3 to fix a missing texture bug http://res.mine.nu/nq/noquarter_b1.2.0_fix.pk3
- Depending on the server you're running No Quarter on, you will need to place the appropriate server binary qagame_mp into the noquarter directory.
- For Windows servers, place qagame_mp_x86.dll in the directory.
- For Linux servers, place qagame.mp.i386.so in the directory.
- For Mac servers, please wait. Server binaries coming soon.
- Start your server!
Upgrade to 1.1.1
- Requires a valid No Quarter 1.1.0 installation (see below).
- Unpack the No Quarter 1.1.1 RAR archive, so you have all the files you need.
- In your "noquarter" directory, remove the old qagame and nq_bin_b1.1.0.pk3 files.
- Leave the large noquarter_b1.1.0.pk3, as 1.1.1 is an upgrade patch, not a full installation, and still requires it.
- Place the new binaries you extracted from the RAR into the "noquarter" directory: noquarter_b1.1.1.pk3 and nq_bin_b1.1.1.pk3
- Depending on the server you're running No Quarter on, you will need to place the appropriate server binary qagame_mp into the noquarter directory.
- For Windows servers, place qagame_mp_x86.dll in the directory.
- For Linux servers, place qagame.mp.i386.so in the directory.
- For Mac servers (do any really exist? j/k), place qagame_mac.bundle in the directory.
- Start your server!
Omni-Bot Enabling
- Omni-Bot in NoQuarter requires NoQuarter 1.1.1.
- No Quarter 1.1.1 supports Omni-Bot 0.61.
- Download and install the appropriate Omni-Bot 0.60 installation from the Omni-Bot website http://omni-bot.com, then upgrade to 0.61.
- Copy the Omni-Bot weapon scripts into omni-bot/et/scripts/weapons
- Copy the Omni-Bot bot definition script "def_bot.gm" into omni-bot/et/scripts (overwrite original).
- Set the following CVARs in your startup script to enable Omni-Bot in No Quarter:
- set omnibot_enable "1"
- set omnibot_path "absolute-path-to-directory-where-omnibot_et.so-is-installed"
- Start server.
- To test your installation, use "/rcon <rconpass> bot addbot. If a bot shows up, you're set up properly! Continue to configure Omni-Bot script to your liking.
- Visit Omni-Bot wiki http://omni-bot.com/wiki for more information.
Omni-Bot 0.66 & NoQuarter 1.2.0 Linux server instructions
- Omni-Bot 0.66 requires No Quarter 1.2.0.
- Install NoQuarter 1.2.0 as per instructions, and make sure it is fully working first.
- If you have an older omnibot installation, you can safely remove all the old stuff (you do not need the omnibot folder for a server only installation, only the omni-bot folder), but keep any nav files or custom scripts.
- You can also safely remove any old omnibot stuff from inside the noquarter folder from an older installation, it is no longer needed.
- Unpack Omni-Bot 0.66 and copy ONLY the omni-bot folder into your base ET folder, ie the same folder that contains the etmain and noquarter folders.
Example showing permissions:
etserver@myserver:~/enemy-territory$
-rwxr--r-- 1 etserver etserver 209 2007-11-10 07:44 etded*
-rwxr--r-- 1 etserver etserver 693K 2007-11-10 07:40 etded.x86*
drwxr-xr-x 3 etserver etserver 856 2008-07-18 15:32 etmain/
drwxr-xr-x 2 etserver etserver 256 2007-11-10 07:44 etpub/
drwxr-xr-x 3 etserver etserver 528 2008-07-19 14:15 noquarter/
drwxr-xr-x 5 etserver etserver 192 2008-07-17 19:46 omni-bot/
drwxr-xr-x 2 etserver etserver 232 2007-11-10 07:40 pbsetup/
etserver@myserver:~/enemy-territory$
Note that the base ET installation folder in this example is ~/enemy-territory/.
- Edit noquarter.cfg and make sure you have set Omnibot_Enable 1 and set Omnibot_Path "/home/username/enemy-territory-folder/omni-bot/" set correctly. NOTE: You must have the trailing slash, and replace username with the user that the ETserver runs as, and enemy-territory-folder with the base folder that contains etmain noquarter and omni-bot. Make sure you do NOT have duplicates of those cvars as omnibot will not run.
- To auto load some bots on server start, edit /home/username/enemy-territory-folder/omni-bot/et/scripts/et_autoexec.gm, and change MinBots() and MaxBots() to a reasonable amount. As an example I use 6 and 8 respectively.
- Place any custom nav files into the /home/username/enemy-territory-folder/omni-bot/et/nav/.
- Start your server, bots should now be working.
- Visit Omni-Bot wiki http://omni-bot.com/wiki for more information.
Installation of 1.1.0
- No Quarter b1.1.0 requires a valid 2.60b/d Enemy Territory installation.
- Version 1.1.0 is completely repacked, thus, requires no previous installations.
- If you are running 1.0.4 or 1.0.2, remove all "noquarter_" and "nq_bin_" pk3 files and server binaries in your "noquarter" directory.
- Download No Quarter from the link above.
- Download the 1.1.0 full install.
- Make a subdirectory in your Enemy Territory installation folder named "noquarter".
- Unpack the No Quarter RAR archive, so you have all the files you need.
- Client-side assets (noquarter_b1.1.0.pk3) and binaries (nq_bin_b1.1.0.pk3) are BOTH REQUIRED for No Quarter to run, place them in your noquarter directory.
- Depending on the server you're running No Quarter on, you will need to place the appropriate server binary qagame_mp into the noquarter directory.
- For Windows servers, place qagame_mp_x86.dll in the directory.
- For Linux servers, place qagame.mp.i386.so in the directory.
- For Mac servers (do any really exist? j/k), place qagame_mac.bundle in the directory.
- Also, you need to replace the qagame_mac.bundle inside the Wolfenstein ET.app. Right click the Wolfenstein ET.app and select "Show Package Contents". Navigate into Contents, then Resources. Rename the qagame_mac.bundle to qagame_mac.OLD.bundle and copy the NQ qagame_mac.bundle into that folder.
- You should have 2 pk3 files and a server binary file in your 'noquarter' directory.
- Set up your server config. A example config has been supplied with the RAR archive. Modify it and make your own. Please remove the comments in your actual config too. There are CVAR docs on this site to assist you.
- Save this config in the noquarter directory as preferably "noquarter.cfg". In your main server.cfg, add the line "exec noquarter.cfg" or whatever you named the noquarter config file.
- Make sure you supply a redirect URL for clients to download the noquarter pk3 files. DO NOT USE SHITSTORM.ORG'S REDIRECT URL.
- Be sure to edit your startup script to point Enemy Territory at noquarter. Use "+set fs_game noquarter"
- Start your server!!!
- Also, encourage players to increase their com_hunkMegs to 128, as they could get errors on some maps, such as Fuel Dump. Increasing hunkMegs will prevent this.
- Make sure you are running a pure server with sv_pure 1. NQ will NOT run properly on unpure servers.
XPSave Conversion and Setup (MUST READ)
- XP Save is no longer handled by one massive file.
- For each player that connects, a tiny file is created just for them. Yes, lots of files, but less filesize and memory usage. Overall, its faster performance.
- To get the new XP save to actually work, you must create a directory on your server for the files to be saved.
- As an example, I named it "xpsave"
- Make sure it has proper permissions so ET can write files to it, CHMOD of 755 is usually good enough.
- Now, in your noquarter.cfg, add the cvar g_XPSaveDirectory and you must point it directly to the directory. Not a relative path like mapscripts where you could just set it to "xpsave". This needs an absolute path!
- So I set g_XPSaveDirectory "/home/shitstormNQ/.etwolf/xpsave"
- Don't use that path I used, set it to where you made your xpsave directory.
- For Windows servers, it could be something like g_XPSaveDirectory "C:/EnemyTerritory/noquarter/xpsave"
- Now, if you plan to have your current xpsave.cfg from converted to the new format so no one looses their precious XP, leave it where it was and leave the g_XPSaveFile cvar set to it.
- NQ 1.1.0 uses g_XPSaveFile just to find your old file and convert it to the new format.
- After conversion, xpsave.cfg will be renamed to xpsave.converted, so it won't be converted again after ever map change. If you ever need the xpsave again, just renamed the extension back to cfg.
- If running multiple servers, specify the same XP save directory to safely share XP between servers.
Major Features of No Quarter
- Originally based on ETPub, but with lots of changes, no player/kill ratings or ATB, overall less stat based.
- New weapons, including a Shotgun, BAR, StG44, Bazooka, and MP34.
- New skills up to level 9, including Pistol Executions and Battlefield Resuscitation (CPR)
- More shrubbot commands, including !pants, !glow, searchable !showbans, and !freeze
- New ranks, totalling 19, unlike the original 11. Rank ensignia now differs per team.
- Aura skills, much like RPGs, with region of effect.
- Insanity fun modes, including instant spawn, guided or homing rockets, panzer and mortar camera, and venom gun.
- New player face skins
- Fun new end game awards
- Visible player leaning
- Droppable weapons and droppable clips, for ammo sharing
- Underwater oxygen bar
- ETPro style head hitboxes
- Realism options, including realistic proning and no shooting while on ladders
- Customizable landmine and airstrike smoke color, per team
- Customizable weapon scripts
- Kicking - kick players, nades and airstrike cans with your foot
- Poison needles
- Throwing knives
- Omni-bot support
Copyright © by Wolfstuff All Rights Reserved. Published on: 2008-09-21 (4801 reads) [ Go Back ] |
