Skip to main content

Fresh Bans

Installing Fresh Bans

MySQL Server

To connect Fresh Bans with GameCMS, a MySQL database is required. Ensure the same database is connected to the GameCMS Dashboard.
How to connect MySQL Server with GameCMS

Installing Fresh Bans with GameCMS.ORG is straightforward and involves only a few steps:

  1. Connect Your Database
    If not already done, connect your database with GameCMS.
    How to connect MySQL Server with GameCMS
  2. Select Main Database for Counter-Strike 1.6
    Go to Integrations -> CS16 and select the main database for CS 1.6 integration.
  3. Add the Fresh Bans Plugin
    1. Navigate to Integrations -> CS16 -> Plugins
    2. Click Add Plugin and select Fresh Bans
    3. Set the table prefix (default is amx_). You can find this prefix in /cstrike/addons/amxmodx/configs/fb/main.cfg
    4. Click Add
  4. Configure Fresh Bans in main.cfg
    Edit /cstrike/addons/amxmodx/configs/fb/main.cfg:
    • Set your database details.
    • Change fb_use_sql to 1
    • Restart your server.

Setting Up Multiple Servers

To separate bans for each server, you have two options:

Using fb_serveronly Option

Using fb_serveronly with the Same Table Prefix and Database

  • Set fb_serveronly to 1 in /fb/main.cfg.
  • This will keep bans separate by server while using the same database and table prefix across all servers.

Using Different Table Prefix

Using Different Table Prefixes without fb_serveronly

  • If you don’t want to use fb_serveronly, you can set unique table prefixes for each server in /fb/main.cfg.
  • Add a new Fresh Bans plugin in the GameCMS dashboard, specifying the table prefix for each server.
  • You can use the same database for all servers; the unique table prefix will ensure each server’s bans are kept separate.

For each server’s configuration, update the following settings in main.cfg:

  1. fb_sql_table (Default: amx_bans)
  2. fb_servers_table (Default: amx_serverinfo)
  3. fb_sql_log_table (Default: amx_logs)

Simply replace amx_ with your chosen prefix, like server1_ or server2_, to separate data per server.