dragonmtn-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Dragonmtn-commits] Changes to snowwhiteHelp/chanserv/set-akickreasons.x


From: Mark Loeser
Subject: [Dragonmtn-commits] Changes to snowwhiteHelp/chanserv/set-akickreasons.xml
Date: Sun, 28 Aug 2005 21:36:57 -0400

Index: snowwhiteHelp/chanserv/set-akickreasons.xml
diff -u snowwhiteHelp/chanserv/set-akickreasons.xml:1.2 
snowwhiteHelp/chanserv/set-akickreasons.xml:1.3
--- snowwhiteHelp/chanserv/set-akickreasons.xml:1.2     Sat Aug 20 06:34:42 2005
+++ snowwhiteHelp/chanserv/set-akickreasons.xml Mon Aug 29 01:36:38 2005
@@ -1,27 +1,57 @@
-<help service="chanserv">
-       <topic name="AKICKREASONS">
-               <command name="AKICKREASONS">
-                       <syntax>
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE help SYSTEM "../help.dtd">
+<help>
+       <service>
+               ChanServ
+       </service>
+       <command>
+               <name>
+                       SET AKICKREASONS
+               </name>
+               <syntax>
+                       <li>
                                /ChanServ SET #&lt;channel&gt; AKICKREASONS 
&lt;on | off&gt;
-                       </syntax>
-                       <desc>
-                               Normally akick reasons are visible to channel 
operators only.
-                               However, if you enable this op reason, then 
every time ChanServ
-                               kicks a user due to an akick, it will display 
the full reason.
-                       </desc>
-                       <section name="NOTE">
+                       </li>
+               </syntax>
+               <desc>
+                       Normally akick reasons are visible to channel operators 
only.
+                       However, if you enable this op reason, then every time 
ChanServ
+                       kicks a user due to an akick, it will display the full 
reason.
+               </desc>
+               <section>
+                       <heading>
+                               NOTE
+                       </heading>
+                       <body>
                                A current side effect of this is that the 
nickname of the channel
                                operator who set the akick will appear in the 
kick reason.
-                       </section>
-                       <examples>
-                               <ex pre="To set akick reasons on for the 
channel #10thKingdom">
+                       </body>
+               </section>
+               <section>
+                       <heading>
+                               ACCESS
+                       </heading>
+                       <body>
+                               Minimum of Founder access required.
+                       </body>
+               </section>
+               <examples>
+                       <example>
+                               <context>
+                                       To set akick reasons on for the channel 
#10thKingdom
+                               </context>
+                               <sample>
                                        /ChanServ set #10thKingdom akickreasons 
on
-                               </ex>
-                               <ex pre="To turn akick reasons off for the 
channel #10thKingdom">
+                               </sample>
+                       </example>
+                       <example>
+                               <context>
+                                       To turn akick reasons off for the 
channel #10thKingdom
+                               </context>
+                               <sample>
                                        /ChanServ set #10thKingdom akickreasons 
off
-                               </ex>
-                       </examples>
-                       <limit access="Founder" />
-               </command>
-       </topic>
+                               </sample>
+                       </example>
+               </examples>
+       </command>
 </help>




reply via email to

[Prev in Thread] Current Thread [Next in Thread]