User:Stoned-Aimlezz
From Omni-bot Wiki
Welcome to the user page of me, Stoned-Aimlezz where you will find some -hopefully- usefull links for Omni-bot and Wolfenstein:Enemy Territory.
At the moment, i am trying to add as usefull as possible information to the Omni-bot Wiki in general and especially to the Omni-bot F.A.Q. page(s). Gradually sort(ing) (=learning) the Wiki-markup out, for now i'm battling with tables.
About Me
I started out with FPS because of my brother playing Quake in the days of the grappling hook and it then got me infected too. After that i rolled into good old Wolfenstein and eventually fell in luv with WOLF:ET from the start.
I always enjoyed online gaming, in the days of Wolfie and the start of ET i played a lot of hours and had a great fun time.
Nowadays i hardly play ET online anymore, too occupied with so called 'work'. Mostly when time allows, i am just playing around with my own (home) server, having fun with ET & all mods which all got installed gradually after testing one after the other with Omni-bot.
Because of my nephew who found editing scripts horrific i made a small in game menu for Omni-bot to add the bots to the game and for some waypoint functions. Anyways it's just fun to tweak 'm in a lot of ways, into -trying- to let 'm do what you want 'm to do. Now thats a way of explaining it.
Thanks to everyone who contribute(s)(d) to Omni-bot via the forum & Wiki. Kisses and hugs to the Omni-bot dev team, thank you for bringing us Omni-bot and for your time & effort put into it to actually make something like this work.
How To Run Omni-bot Home Server
F.Y.I : This below part is now a part of the Omni-bot F.A.Q.
Here's a small description on how to make a quick -vanilla ET + Omni-bot server on your Win32 home computer.
At least how i did it. You should be able to view and edit waypoints with it.
If not already :
- Install Wolfenstein:Enemy Territory
- Run the patch 2.60b
- Install Omni-Bot See Also : Step by Step
(aug-2-2007 : 0.66 Stable)
(aug-2-2008 : 0.70 Stable)
When the above is installed you'll see a new shortcut in your Start Menu : Omni-Bot ET.
The new shortcut is also on your desktop.
When you click on this shortcut you will start Enemy Territory with the mod : Omni-bot.
In this way you will still have to go through the ingame menu to host and or play on your own server.
To avoid this hassle every time here below there's the double click way to start your own server. Make a shortcut like this on your desktop or wherever you want :
"C:\Program Files\Wolfenstein - Enemy Territory\ET.exe" +set dedicated 0 +set fs_game omnibot +set com_hunkmegs 72 +exec server.cfg
- +set dedicated 0 *a server, to be played on as well by the server host (=you)
- +set fs_game omnibot *set gametype
- +set com_hunkmegs 72 *allocates a certain amount of memory for map and item loading.
- +exec server.cfg *server settings, your server configuration file
More and in depth info on running a Wolfenstein:Enemy Territory server :
Advanced Wolfenstein: Enemy Territory Server Setup Guide
There's also a pdf file for download.
How To Quickly Add The Omni-bots To Your server
There are -in short- 3 ways :
- Via the : MinBots & MaxBots Omni-bot commands *set in your et_autoexec.gm.
- Via the 'bot addbot' console command, f.e to add a Axis Covert type : "\bot addbot 1 5 Covert-Axis"
- Via a omni-bot.cfg, a file in which you put the above 'bot addbot' command as many times you want a bot with a selected class.
- NOTE : ET Pub has the Cvar : g_bot_minPlayers
Example omni-bot.cfg :
// start // bot addbot <team> <class> <name> // save f.e as : omni-bot.cfg -in same folder where your server.cfg is- // put the line : exec omni-bot.cfg in your server.cfg to add bots automatic on map start // First kick the old, ones. bot kickall bot addbot 1 1 Soldat-Axis bot addbot 1 2 Sani-Axis bot addbot 1 3 Engi-Axis bot addbot 1 4 Leut-Axis bot addbot 1 5 Covert-Axis bot addbot 2 1 Soldier-Allied bot addbot 2 2 Medic-Allied bot addbot 2 3 Engi-Allied bot addbot 2 4 Leut-Allied bot addbot 2 5 Covert-Allied // eof
VSP
For now look here : VSP Stats
Interesting Omni-bot Wiki Links
Chatty bot profile by IRATA
Omni-bot User:IRATA has made a nice profile to make a 'Chatty bot' here on the Omni-bot Wiki.
Talking bot script by D00d
A script that is meant to make the bots a little more "communicative" here on the Omni-bot Wiki.
Team door script goal for covert ops bots (ET) by D00d
The Omni-bot User:D00d has also been working on a slightly modified version of the use switch goal that can be used as a team door goal for covert ops. The team door thread is started from a modified version of the disguise goal: Once the bot is disguised, it will try to open a team door and do something. Team doors are added to a map exactly like switches: There must be named waypoints and a Map.Teamdoors table in the map script. As a proof of concept, D00d has made a version of the Caen2 waypoints and script that allows disguised Axis Covert bots to finish the map! This is experimental, but the versions D00d has published here have been tested relatively thoroughly and shouldn't be crash-prone. Download the waypoints/script and D00d's modified disguise_goal.gm: caen2 disguise.zip
More Omni-bot Wiki Links
Map Scripting Tools Enemy Territory
Roll The Dice -Goto A Random Page
Write data into mysql db via Exec cmd (SQL Inserts from GM)
See Also
Little web site (ET + Omni-bot related)
Sorted Wiki Tables Testing Grounds
Sorted Waypoint Table
| Map | Map URL | WP URL | Author | Gm Script | Current Owner | Notes |
|---|---|---|---|---|---|---|
| Adlernest | [1] | INC | crapshoot / blindman | yes | crapshoot | included in 0.66 release |
| Battery | ET | INC | crapshoot / Jaskot | yes | crapshoot | included in 0.66 release |
| Braundorf_b4 | [2] | INC | crapshoot | yes | crapshoot | included in 0.66 release |
| Caen | [3] | INC | crapshoot | yes | crapshoot | included in 0.66 release |
| ET Ice | [4] | INC | crapshoot | yes | crapshoot | included in 0.66 release |
| Frostbite | [5] | INC | crapshoot | yes | crapshoot | included in 0.66 release |
| Fueldump | ET | INC | crapshoot / Jaskot | yes | crapshoot | included in 0.66 release |
| Goldrush | ET | INC | crapshoot / Jaskot | yes | crapshoot | included in 0.66 release |
| Oasis | ET | INC | crapshoot / Jaskot | yes | crapshoot | included in 0.66 release |
| Radar | ET | INC | crapshoot / Jaskot | yes | crapshoot | included in 0.66 release |
| Railgun | ET | INC | crapshoot / Jaskot | yes | crapshoot | included in 0.66 release |
| Venice | [6] | INC | crapshoot | yes | d00d | included in 0.66 release |
The only thing added to get it to sort : {|class="wikitable sortable"
Compatibility Omni-bot + Mod Version
| Omnibot | Jaymod | ET pub | NQ |
|---|---|---|---|
| 0.5.2 | 2.0 | 0.7.0 | tbd |
| 0.5.3.2 | tbd | 0.7.1 | tbd |
| 0.5.3.2 | tbd | 0.7.2 | tbd |
| 0.60 | 2.1.2 | 0.7.3 | 1.1.1 |
| 0.61 | 2.1.2 | tbd | 1.1.1 |
| 0.61 | 2.1.4 | tbd | 1.1.1 |
| 0.65 | 2.1.5 | tbd | tbd |
| 0.66 | 2.1.6 | 0.8.1 | tbd |
| 0.66 | 2.1.7 | 0.8.1 | tbd |
Lost ? IRA's NQ piece ?
The Piece below is from the NQ Wiki : Revision as of 09:45, 30 April 2007.
This version of the document contains some extra (usefull) info for the NQ mod users, added by IRATA [*] --> Set write permission on Omni-Bot waypoint-folder.
This info got removed from NQ Wiki in newer versions of the document for unknown reasons.
Info on this topic on the Omni-bot forum : Set write permission
Go To this version on the : NQ Wiki
f.i. Check the Top Left corner for more versions of this document.
No Quarter b1.1.1 requires a valid 2.60b/d Enemy Territory installation.
- Current Version:
*Download No Quarter 1.1.1 Update - 4.5 MB
*Download No Quarter 1.1.1 Patch (Omni-Bot Servers ONLY) - 1.94 MB
- Older Versions:
*Download No Quarter Mod 1.1.0* - 18.20 MB
*Download No Quarter Mod 1.0.4 Update* - 4.56 MB (Requires 1.0.2 installation)
*Download No Quarter 1.0.4 Full - 23.9 MB
*Download No Quarter 1.0.2 - 22.8 MB
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 No Quarter requires Omni-Bot 0.6 or greater.
- Download and install the appropriate Omni-Bot installation from the Omni-Bot website.
- Download and install the No Quarter 1.1.1 Omni-Bot Patch (see below).
- Set the following CVARs to enable Omni-Bot in No Quarter:
- set omnibot_enable "1"
- set omnibot_path "absolute-path-to-directory-where-omnibot_et.so-is-installed"
- 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)
- The previous scripts are what allows the Omni-Bots to use No Quarter weapons.
- Set write permission for et-instance on Omni-Bot waypoint-folder omni-bot/et/nav.
- Start server.
- To test your installation, use "/rcon <pass> bot minbots <x>" or "set minbots <x>" in $omnibot_path/et/scripts/et_autoexec.gm before starting server. <x> is count of bots. Have a look at omni-bot/et/nav if there is at least one *.vis-file (your first map) for maximum omni-bot performance created.
Note: Omni-Bot creates an own 'omnibot.log'-file in your et-installation path f.e. /usr/local/games/enemy-territory/. Make sure write permission is also set. Use this file to debug bots.
Note/Warning: Do not use unsupported filesystem characters in bot-names. Upper NQ 1.1.1 color informations are stripped and unacceptable characters are substituted with a '-' for filenames. So the names ^1red^0\^1bot and ^2red^0/^2bot will both be translated to "red-bot" for the guids. XP save works on guid name.
Omni-Bot Patch for 1.1.1
- Use only if you downloaded and installed No Quarter 1.1.1 before April 5th, 2007. This patch has been merged with the 1.1.1 upgrade download, see above.
- Download the patch here : No Quarter 1.1.1 Omni-Bot Patch - 1.94 MB
- Download and install the : Omni-Bot 0.61 Patch(Win & Linux) (-hotfix for Omni-bot version 0.60-)
- This patch is a must if you have installed No Quarter 1.1.1 and plan to use Omni-Bots!!!
- This patch offers no changes for 1.1.1 servers that have Omni-Bots disabled.
- This patch fixes the following bugs with Omni-Bots in No Quarter:
- Bots grouping together, getting stuck at waypoints, and not being able to move.
- Not being able to specify a different Omni-Bot folder with omnibot_path.
- Replace the appropriate qagame on your server from the 1.1.1 installation, with the one provided in this patch.
- Bots should now work like expected!
Keep in mind: Bots use more CPU power than humans do. Watch CPU usage in case of instability and reduce count of players.
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.
Update Installation to 1.0.4 (from 1.0.2)
- No Quarter b1.1.0 requires a valid 2.60b/d Enemy Territory installation
- This requires a previous No Quarter b1.0.2 installation on your server.
- Shutdown your server
- Extract the noquarter_b1.0.4_update.rar file
- In the 'noquarter' folder, REMOVE this file: nq_bin_b1.0.2.pk3
- Do NOT, I repeat, do NOT remove noquarter_b1.0.2.pk3. This is still required.
- Add the following new files in the 'noquarter' directory:
- noquarter_b1.0.3.pk3
- noquarter_b1.0.4.pk3
- nq_bin_b1.0.4.pk3
- Now, you will need to replace the server binary, depending on the type of server you are running. You already figured this out since this is just an update.
- For Windows servers, replace qagame_mp_x86.dll in the directory.
- For Linux servers, replace qagame.mp.i386.so in the directory.
- For Mac servers (we found one that exists!), 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 4 pk3 files and a server binary file in your 'noquarter' directory.
- Update your config with any new CVARs or changes in from Changelog.
- Start your server!!!
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
Install - Step by Step - Omni-Bot 0.7
Step 1
Double click the Omni-Bot Installer ET (Full) 0.7 Stable :
Step 2
The Wizard gives you a nice welcome.
Click on : Next.
Step 3
Choose Components - Select components to install; leave Mod support ON, as is by default.
Click on : Next.
Step 4
Choose Install Location.
Click on : Next.
Step 5
Please wait while Omni-Bot 0.7 STABLE is being installed ..
Step 6
Completing the Omni-Bot 0.7 STABLE Setup Wizard.
Click on : Finish.
Step 7
Now check on your desktop ... there's a new shortcut : Omni-Bot ET !
DOUBLE CLICK IT !!!
Step 8
After Wolfenstein:Enemy Territory starts UP.
Click on : HOST GAME.
Step 9
When the next screen opens.
In right corner below.
Click on : START SERVER.
Step 10
IMPORTANT : Wait untill the warmup finishes, and the map starts.
Step 11
Open the console with the tilde : ~ key
When you see like in the above picture : "Bot Initialized" you have succesfully installed Omni-Bot.
Step 12
When you open the tab : SERVER INFO, you will see the now running mod listed under Game name : Omni-Bot:etmain.
Server.cfg
Whatever mod you are running, the server.cfg needs to be configured before players can connect. If you are renting a server then your game server provider will probably do the initial configuration for you.
The list is not to be said : complete. You as a server admin have to tweak it !
Here below are the most common ones.
- set dedicated "2" : change to 1 if you use the server on a LAN
- set net_ip "" : set to override the default IP ET uses. No need to change
- set net_port "27970" : set to override the default port ET uses. Default port is 27960 but some server providers use other ports. Should already be set correctly if you rent a server
- set sv_maxclients "22" : number of maximum players that can be connected on the server including private slots. If you are renting then this is controlled by your provider and changing it will have no effect
- set g_password "" : set a password to lock the server. Players will be prompted for password when they connect. You can lock server e.g. during scrims
- set sv_privateclients "2" : if set > 0, then this number of client slots will be reserved only for people who have the privatepassword (see below)
- set sv_privatepassword "your password" : if you have defined private slots then you should define a password for them as well.
- set rconpassword "your_rcon_ password" : this is the most important password. Access to it should be strictly restricted to people who change the configuration and manage the server at this level. People who have this password can have full server control
- set refereePassword "your_ref_password" : this will set the password for a referee. If you are running any of the mods this will be useful because you can assign people referee status to administer the server. Referees can shuffle teams, put players in teams or spectator, kick players etc. Again, be careful about who you give ref access.
- set sv_wwwDownload "1" : if you have custom maps on your server then make sure you have this set at 1. Otherwise players won't be able to download them
- set sv_wwwBaseURL "http://myhostinwebsite.com" : if you are re-directing your downloads then here is where you set the url. Read this post for the details
- set g_friendlyFire "1" : set this to 0 if you don't want Friendly Fire on i.e. if set to 1, you can team-kill your team mates
- set g_teamforcebalance "1" : if you have this set to 1 then the server won't allow a player to join a team which has already one player more than the other team. If set to 0 then it will be easier to end up with unequal teams in terms of numbers
- set g_voiceChatsAllowed "4" : this is the maximum number of chats someone can spam chat with. Make this too big and you risk a lot of spamming
- set g_warmup "60" : warm-up time i.e. the number of seconds prior to starting the game. Make sure this is long enough to allow players to connect after the end of the previous map. You can increase it e.g. during scrims to allow people more time to organise
- set vote_allow_kick "1" : if you set this as 1 then players will be allowed to vote-kick someone out of the server
- exec maprotation.cfg : set this as your map rotation config file.