Search results

Jump to: navigation, search
  • [[Ctcp_(event)|CTCP]] *:FINGER:*: { [[ctcpreply]] [[$nick]] FINGER Hey Don't finger me. ( [[Dol
    308 bytes (33 words) - 09:30, 2 July 2007
  • Access levels are assigned both to a user and to an event and serve to limit a user's access to only certain events. ...ll levels equal to or less than 3. All the other levels are levels that an event must specifically have to allow a user to access it.
    6 KB (1,038 words) - 02:36, 26 February 2007
  • ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; LOAD EVENT ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; JOIN EVENT ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
    34 KB (4,097 words) - 14:54, 28 June 2008
  • Returns the associated file name including path to the target of the event. * [[Ctcp_events|CTCP Prefix]] - dcc send only.
    1 KB (144 words) - 16:56, 29 January 2009
  • This identifier allows you to check if CTCP or Event parsing is turned on, or if the entire remote is disabled
    519 bytes (65 words) - 00:05, 31 October 2008
  • These [[:Category:Events|events]] respond to [[ctcp|CTCP (Client to Client Protocol)]] requests. ctcp <level>:<matchtext>:<*|#|?>:<commands>
    522 bytes (74 words) - 00:25, 31 October 2008
  • ...vent triggers when a user sends a standard [[ctcp|CTCP]] reply to a [[ctcp|CTCP]] that you initiated. This is triggered when a client replies to a [[ctcp|CTCP]] VERSION request that you sent.
    539 bytes (85 words) - 01:46, 23 June 2013
  • ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; LOAD EVENT ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; JOIN EVENT ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
    48 KB (5,079 words) - 01:21, 3 March 2011
  • @ prefix can be used to only trigger the event if you are opped on the channel. so it is the same as using if ($me isop $c An example/guideline for an event:
    122 KB (20,281 words) - 19:27, 2 March 2011