- BNBT.CFG
BNBT stores its configuration data in a simple text document
called bnbt.cfg. It is composed of configuration keys
and their values and can be edited using any simple text editor
such as Notepad.exe, Emacs, Pico, etc. The standard syntax is as
follows:
configuration_key = value
PLEASE NOTE: There will never be any spaces in the configuration
key names; only underscores. There should be a space before and
after the equals sign. Values should NEVER be surrounded by
quotation marks. This will cause parse errors.
BNBT's configuration file can be modified while the tracker is
running, but the changes will not take effect until after the
tracker has been shutdown and restarted.
A list of configuration keys and their functions can be found
at
http://bnbt.go-dedicated.com/doc/. I will also be
publishing my own configuration key guide in the future, as I
have done in the past.
The following configuration keys are specific to The Trinity
Edition of BNBT and BNBT EasyTracker:
- bnbt_alt_signup_url — 7.7r3.2004.07.15
When enabled, allows you to specify an alternate URL to
which your users will automatically be redirected when they click the
register button
- bnbt_custom_labels — 7.7r3.2004.07.15
When enabled, allows you to specify custom text to be used for numerous
objects on the index page of your tracker; these values are specified
using var expressions in your header document (JavaScript)
NOTE: This key is enabled (1) by default in EasyTracker configuration,
but has no effect if variables are not set in header.html.
Some values are already assigned in the default header.html document
that comes with EasyTracker. Others are commented out along with documentation.
- bnbt_navigation_bar — 7.7r3.2004.07.15
When enabled, displays an intuitive navigation bar at the top of all tracker
pages; clickable buttons are based on user's access level... i.e.
admin buttons appear dimmed and are not clickable when the user does
not have administrative access
This feature is enabled (1) by default in EasyTracker configuration;
if enabled, you should use the stylesheet that comes packaged with
EasyTracker for optimal display.
- bnbt_tracker_title — 7.7r3.2004.07.15
This key allows you to specify the name of your tracker which will
be used on your tracker's webpages and in the title bar of the user's
web browser.
- bnbt_static_upload_header — 7.7r3.2004.07.15
bnbt_static_upload_footer — 7.7r3.2004.07.15
— allows you to specify html documents that will be displayed
above and below the upload page; works just like the
standard header and footer keys for the index page.
- bnbt_static_signup_header — 7.7r3.2004.07.15
bnbt_static_signup_footer — 7.7r3.2004.07.15
— allows you to specify html documents that will be displayed
above and below the signup page; works just like the
standard header and footer keys for the index page.
- trinity_nt_service_name — 7.5r2.2004.04.30
— allows you to specify a custom name to be used when installing
the tracker as a Windows System Service, thus allowing you to run
more than one instance of the tracker as a service.
— Please read the System Service Tutorial before using this
feature.
- trinity_use_mouseovers
— when enabled, assigns onMouseOver and onMouseOut functions
to the tag filter images on your tracker's index; actions can then
be attributed to those functions using JavaScript in your header
document.
— Please read the onMouseOver Feature Tutorial before using this
feature.
- BNBT Configuration Frontend — The tabs in the image below
are clickable.
In addition to modifying your configration file with a simple
text editor, a configuration frontend is also available for
Windows users, and comes prepackaged with BNBT EasyTracker. The
configuration frontend was created by Deadhead for BNBT EasyTracker,
but can be used with any version of BNBT.
PLEASE NOTE: Certain dynamic linking libraries (DLLs) are
required to use the frontend. These are automatically installed
by BNBT EasyTracker if they are not already on your system.
The frontend has not been updated since the release of BNBT 7.4
Beta Release 2, and will therefore not contain the fields for
any new configuration keys created since then. The Raw
tab, however, will display all the new configuration keys found
in the tracker's configuration file.
The Nat check field (found on the Allow Options tab) is
not used, as it has not yet been implemented into BNBT.
The Display All field (found on the Display Options tab)
is no longer being used. This value should be left blank. The
new key keep_dead can be found on the Raw tab.
- BNBT Configuration Frontend Errors
If you receive errors when launching the configuration frontend,
it usually means that you do not have the required DLLs installed
and registered. To rid yourself of these errors, you should
download and install the new BNBT EasyTracker.
- Applying Changes
Changes to your tracker's configuration can be made while the
tracker is running, but those changes will not take effect
until after your tracker has been shutdown/restarted.
