Chapter 12. Omni-bot

Table of Contents

Native Library Search Path
See Also

Jaymod natively supports the Omni-bot product. This product enables servers to set up computer controlled bots with relative ease. There is nothing that you have to set up within Jaymod’s configuration to use them. There is, however, some setup that needs to be done with the Omni-bot installation.

To get Omni-bot for your server, visit http://www.omni-bot.com. There, you will find downloads for the files needed to get running, and installation and configuration documentation.

It is imperative that you match the Omni-bot version exactly that which Jaymod supports. Jaymod 2.1.7 supports Omni-bot 0.66, and for all other versions please consult the appropriate documentation.

Native Library Search Path

Omni-bot can be installed in a variety of ways on your server. Because different people have different needs, a list of directories is searched and the first one which has a native library for your platform is used. Note that any duplicate directories are searched only once. The following is the standard search path, in order of preference, for Omni-bot native libraries:

  1. optional directory specified via CVAR omnibot_path.
  2. optional omni-bot sub-directory of fs_homepath, if specified.
  3. optional omni-bot sub-directory of fs_basepath, if specified.
  4. omni-bot subdir relative to { $HOME (for Linux) or %Program Files% (for Windows) } environment variables of the server process.
  5. default mechanism for server platform's native library loader.

[Note]Note
On Linux systems, if the directory by which the Omni-bot library was found is relative (not absolute) then you must add '.' to the PATH environment variable before launching the process. If this is not done then the library will load but internal Omni-bot initialization routines will fail. It is strongly suggested that absolute paths be used to work around this issue.

Example search path for a typical Linux server with omnibot_path=/somewhere/omni-bot:

  1. /somewhere/omni-bot/
  2. /home/etserver/omni-bot/
  3. /usr/local/games/enemy-territory/omni-bot/
  4. $HOME/omni-bot/
  5. <SYSTEM-LOADER>

Example search path for a typical Windows server with omnibot_path=Z:\Somewhere\Omni-bot:

  1. Z:\Somewhere\Omni-bot\
  2. G:\ETserver\Omni-bot\
  3. C:\Program Files\Wolfenstein - Enemy Territory\Omni-Bot\
  4. C:\Program Files\Omni-bot\
  5. <SYSTEM-LOADER>

See Also

omnibot_enable(cvar)