" $bDELTRACK$b Deletes an active track.",
" $bLISTTRACK$b Lists all active tracks.",
);
+
+"PRIVILEGE" (
+ " The Privilege list system: ",
+ " $b$b",
+ " $bPRIVSET$b Set and unset privileges on the fly."
+ );
+
"ROUTING" (
" The Auto Routing System: ",
" $b$b",
" $bROUTING MAP$b Show what the active routing plan says the network should look like.",
" $bREROUTE$b Connect servers to the network, optionally squiting them first to change the routing.",
" $b$b ",
- " Start by creating a routing plan, and then adding servers to it, with their listning port, uplink, and a backup uplink. You can view it in $bSTATS ROUTING$b. Take care not to create loops, and that you make everything connected. Then set your new plan ACTIVE using $bROUTING SET$b. $O does the rest! See help topic $bROUTING EXAMPLE$b for a working example."
+ " Start by creating a routing plan, and then adding servers to it, with their listning port, uplink, and a backup uplink. You can view it in $bSTATS ROUTING planname$b. Take care not to create loops, and that you make everything connected. Then set your new plan ACTIVE using $bROUTING SET$b. $O does the rest! See help topic $bROUTING EXAMPLE$b for a working example."
);
"CHANNEL" (
" $bJUPE$b Create dummy server.",
" $bUNJUPE$b Remove a dummy server.",
" $b$b",
+ " $bDEFCON$b Manipulate the DefCon system.",
" $bREFRESHG$b Refresh the Glines.",
" $bREFRESHS$b Refresh the Shuns.",
" $bSETTIME$b Synchronize time across the network.",
"$bGLINE$b: Gline the user that tripped the alert",
"$bTRACK$b: Send a notice to the $b$O$b alert channel and track the user (if the tracking module is loaded)",
"$bSHUN$b : Shun the user that tripped the alert",
+ "$bVERSION$b : Check the version on the user that tripped the alert",
+ "$bSVSJOIN$b : Force the user that tripped the alert to join the target channel",
+ "$bSVSPART$b : Force the user that tripped the alert to part the target channel",
"$uSee Also:$u addalert, delalert"
);
"TRACE" ("/msg $O TRACE <action> <criteria> <value> [<criteria> <value>]...",
"Searches through the current users for those matching the specified criteria, and applies the specified action to them. A detailed list of actions can be found in $bhelp trace action$b and a list of criteria in $bhelp trace criteria$b.",
- "Quick Ref ACTIONS: PRINT, COUNT, KILL, GLINE, SHUN, GAG, DOMAINS",
- "Quick Ref CRITERIA: MASK, NICK, IDENT, HOST, INFO, SERVER, IP, ACCOUNT, AUTHED, CHANNEL, NUMCHANNELS, LIMIT, NICKAGE, ACCESS, REASON, DEPTH, DURATION, CLONES, INFO_SPACE, ABUSE OPERS, LOG, REGEX",
+ "Quick Ref ACTIONS: PRINT, COUNT, KILL, GLINE, SHUN, GAG, DOMAINS, SVSJOIN, SVSPART, VERSION",
+ "Quick Ref CRITERIA: MASK, NICK, IDENT, HOST, INFO, SERVER, IP, ACCOUNT, AUTHED, CHANNEL, NUMCHANNELS, LIMIT, NICKAGE, ACCESS, REASON, DEPTH, DURATION, CLONES, INFO_SPACE, ABUSE OPERS, LOG, REGEX, CHANTARGET, SILENT, VERSION",
"Access level: $b${level/trace}$b",
"$uSee Also:$u trace action, trace criteria"
);
"$bSHUN$b: Issue a shun for the client's host (by default, 1 hour long).",
"$bGAG$b: Gag all matching users (by default, does not expire).",
"$bDOMAINS$b: Display counts of users in each domain (length specified by DEPTH criteria.",
+ "$bSVSJOIN$b: Force users to join channel givin in chantarget criteria.",
+ "$bSVSPART$b: Force part the matching clients out of the specified target channel.",
+ "$bVERSION$b: Query for the users CTCP VERSION reply.",
+ "$bMARK$b: Set a nefarius 'mark' named via the mark criteria as if the user were in that dnsbl.",
"Note: By default, IRC operators are not affected by the KILL, GLINE, SHUN or GAG actions. You can override this by specifying the $bABUSE OPERS$b criteria for a trace. Even if you do specify $bABUSE OPERS$b, it will not affect opers at your access level or above.",
"$uSee Also:$u trace criteria, trace"
);
"$bLOG$b Record matching users in $O's log file (in addition to acting).",
"$bREGEX$b yes/no Specifies if NICK/IDENT/HOST/INFO should be treated as a regular expression.",
"$bSILENT$b yes/no If yes, AUTO is prepended to the gline message, making the gline silent in nefarious ircd.",
+ "$bVERSION$b version If they have been queried using the VERSION action and responded, they are matched if the reply they give matches.",
+ "$bCHANTARGET$b #channel For use with SVSJOIN action, this specifies the channel they are svsjoined to.",
+ "$bMARK$b mark For use with the MARK action, this is what thety are marked with.",
"Additionally, the $bCHANNEL$b target may be prefixed with @ to select channel operators, + to select voiced users (will not select chanops unless @ is also used), or - to select non-voiced non-chanop users. For example, CHANNEL #foo will select all users in #foo; CHANNEL +#foo will select only users voiced in #foo; CHANNEL @+#foo will select ops and voiced users in #foo; etc.",
"When searching on the criteria of nick, ident, or info, the search string can be another of the three, prefixed with a & character, to indicate that the match should compare each user's individual data. For example, $binfo &nick$b would search for all users whose info matches their nick. To search for that phrase explicitly, prefix the & with a backslash; e.g.: $binfo \&ident$b.",
"$uSee Also:$u trace action, trace"
"$uSee Also:$u ban, kick, kickban"
);
+"MARK" ("/msg $O MARK <mark>",
+ "Sets a nefarious 'mark' on the user as if they are in <mark> dnsbl. ",
+ "(shows in /whois and prefixes their host, for easy banning)",
+ "Mark must be a-z0-9 or dash (-) 20 chars or less.",
+ "$uSee Also:$u trace action"
+ );
+
+"SVSJOIN" ("/msg $O SVSJOIN <nick> <#channel>",
+ "Forces nick to join #channel",
+ "$uSee Also:$u svspart, join, trace action"
+ );
+
+"SVSPART" ("/msg $O SVSPART <nick> <#channel>",
+ "Forces nick to part #channel",
+ "$uSee Also:$u svsjoin, part, trace action"
+ );
+
"MODE" ("/msg $O MODE <#channel> <+/- mode>",
"Sets the specified modes (but cannot include voice, ban or op changes) on a channel.",
"If the channel is omitted, then $bmode$b will be done in the channel where the command was given.",
"$uSee Also:$u refreshg, gline, ungline"
);
+"DEFCON" ("/msg $O DEFCON [1|2|3|4|5]",
+ "The defcon system can be used to implement a pre-defined set of restrictions to services useful during an attempted attack on the network. Not specifying a level will cause $O to display the currently set defcon level and options if the level is below 5",
+ "Access level: $b${level/defcon}$b",
+ );
+
"REFRESHG" ("/msg $O REFRESHG [server]",
"Re-issues all GLINES in $b$O's$b database. Usually used for newly joining or desynched servers. If a server mask is specified, the GLINES are only sent to server(s) with matching names.",
"Access level: $b${level/refreshg}$b",
"ROUTING ADDPLAN" ("/msg $O ROUTING ADDPLAN <name>",
"Creates a new blank routing plan named name.",
"You can then use $bROUTING ADDSERVER$b to build it.",
- "Use $bSTATS ROUTING$b to view it, and $bROUTING SET ACTIVE$b to activate it.",
+ "Use $bSTATS ROUTING [name]$b to view it, and $bROUTING SET ACTIVE$b to activate it.",
"$uSee Also:$u routing, stats routing, routing delplan, routing set, routing addserver"
);
"ROUTING DELPLAN" ("/msg $O ROUTING DELPLAN <name>",
" |-laptop.net.org - laptop's uplink is test",
" | `-foobar.net.org - foobar's uplink is laptop",
" `-test2.net.org - test2's uplink is test",
- " `-test3.net.org - test3's uplink is test3",
+ " `-test3.net.org - test3's uplink is test2",
" $b$b ",
" Its important that every entry in your routing plan be specified relitive to the same location. Usually this is the location of X3 itself, but doesn't have to be. In the above example you could do:",
+ " ROUTING ADDPLAN mylpan ",
" ROUTING ADDSERVER myplan test.net.org:4400 x3.net.services ",
" ROUTING ADDSERVER myplan test2.net.org:4400 test.net.org ",
" ROUTING ADDSERVER myplan test3.net.org:4400 test2.net.org ",
" ROUTING ADDSERVER myplan laptop.net.org:4400 test.net.org ",
" ROUTING ADDSERVER myplan foobar.net.org:4400 laptop.net.org ",
+ " ROUTING SET ACTIVE myplan ",
" $b$b ",
" If there are loops, or two servers who point to eachother, $O will not be able to use the plan. If there are sections which do not link back to the rest, they will be lost and the plan will not work properly.",
);
"$uSee also:$u routing, routing map, stats routing",
);
-"STATS ROUTING" ("/msg $O STATS ROUTING",
+"STATS ROUTING" ("/msg $O STATS ROUTING [planmask]",
"Provides information about The Auto Routing System's configuration. You can see the routing plans, and the current routing options.",
+ " If planmask is provided, you will see the full details for any plans matching the mask (* and ? wildcards)",
"$uSee also:$u routing, routing set",
);
+"PRIVSET" ("/msg $O PRIVSET <nick> <+/-flag>",
+ "Allows $O to set flags on users.",
+ "Access level: $b${level/privset}$b",
+ "$uSee also: privflags"
+ );
+
"UNRESERVE" ("/msg $O UNRESERVE <nick>",
"Removes a nick from $b$O's$b reserve list.",
"Access level: $b${level/unreserve}$b",
"$bMODULES$b: Shows loaded modules that implement commands.",
"$bSERVICES$b: Shows active service bots.",
"Access level: $b${level/stats}$b",
+ "$b$b",
+ "$uSee Also:$u stats alerts"
+ );
+
+"STATS ALERTS" ("/msg $O STATS ALERTS [Owner|Filter]",
+ "Show alerts. If a parameter is given, only alerts who match it are shown.",
+ "$b$b",
+ " Owner - the account name of whoever created the alert",
+ " Filter - A wildcard (* and ?) match string compared against the criteria string",
+ "$b$b",
+ "Example: STATS ALERTS *nick phil*",
+ "$uSee Also:$u addalert, delalert, stats"
);
"TRACK" ("/msg $O TRACK <+/-type|all|none>",