Evie Addon Details

Watch - Add Favorite

Description

Manage all your ES plugins, all from one easy popup!
(note: if you are using xa, you can get an xa version here)

Addon Manager offers one easy popup to manage all of your Eventscripts addons!

Note: The blue popups are a client-mod, and have nothing to do with Addon Manager

New with 2.3:

  • Optional: ExceptHook Integration. The addons page in the menu will display a message if ExceptHook has dumped an error file. [enable/diable via am_excepthook in settings.cfg]
  • Improved addon_manager/manager syntax (see below)


New with 2.0:

  • Improved Parser
  • File parsing now optional (Improves speed)
  • Configuration file


To access the menu, simply say !addons
That will open a list of all addons installed on your server, and upon selecting one you can view its details and load/unload it.

You will need to be set as an admin to use the admin menu.
You can use an auth service to achieve this (admins will need access to "manage_addons") or you can add admins in the settings file
Note: Mani-auth is no longer built in. If you require mani use, try using mani_basic_auth or ini_tree_auth


If one of the scripts you have doesn't have addon info, you can load it using Addon Manager to give it info! Simply replace the es_load scriptname in your autoexec with
am_load scriptname "Real name" "Author" "version"
// for example..
am_load gungame4 "GunGame 4" "cagemonkey" "4.0.96 RC1"


Addon Manager also comes with a built in script controller! Now you can automate the unloading and loading of scripts under certain conditions! using the command am_control
 
// a few examples...
 
// This will make the script only loaded on de_dust2 and cs_office
am_control manage <myscriptname> map de_dust2
am_control manage <myscriptname> map cs_office
 
// This will do the opposite - <myscriptname> will be loaded on everymap except de_dust2 and cs_office
am_control manage <myscriptname> notmap de_dust2
am_control manage <myscriptname> notmap cs_office
 
// This will only load the script if there is more than 4 players on the server (5 or more)
am_control manage <myscriptname> players >4
 
// This will only load the script if there is less than 4 players on the server (3 or less)
am_control manage <myscriptname> players <4
 
// This script will only be loaded if there are more then 4 players and the map is de_dust2
am_control manage <myscriptname> players >4
am_control manage <myscriptname> map de_dust2
 
// Remove controls from an addon (used to remove whilst ingame)
am_control exclude <myscriptname>
 
// Note: In older versions of manager, you had to include addons like so:
am_control include <myscriptname>
// This is no longer required, but is still supported.

These setting can be put into your autoexeccfg or settings.cfg that will appear in addons/eventscripts/addon_manager/manager/ after its first load.

To enable the controller, add
es_load addon_manager
es_load addon_manager/manager
to autoexec


Note for scriptors:
Python files details are set via es.AddonInfo()
ESS scriptors can use the addon_manager command to give their addons a description

 
es_set myvar 0
es_exists myvar addon_manager_ver // if addon_manager is installed
if (server_var(myvar) == 1) do
{
addon_manager "basename" "addon name" "author" "version"
// Tell addon_manager this addons details
}

also, am_load cannot write over your variables

*should* work for all source games

and most importantly, +w00t if you like o.~

Installation

extract to cstrike (or your main folder, depending on game)
add es_load addon_manager to autoexec
(if you want to install the controller too, add es_load addon_manager/manager to autoexec also)
restart server

alternatively, you can just use the following command in your server console:
es_install addon_manager autoload
(es_install will not enable the controller, you will still need to add es_load addon_manager/manager to your autoexec if you wish to use it)

Version Notes For 2.3.1 (Announce this update)

Updated on: 2010-01-17 22:27:45 EST by DanielB
Cleaned up addon_manager.py

Changed Syntax for addon_manager/manager (am_control)
Old syntax is still supported, though updating is recommended [it will just attempt fix your syntax]

Syntax changes:
[list]
  • am_control include statements are no longer required
  • To add a rule to an addon, you must use the manage subcommand. eg
  •  
    am_control manage gungame map de_dust2
    am_control manage gungame players >3
    // so, where you would have done
    am_control gungame players >3 // OK - but only supported for legacy (may not be supported in future)
    // you'd now do
    am_control manage gungame players >3 // Great! This syntax will always be supported
    // Though the old style is still supported

    ( Previous Versions )

    Request a new feature