Hi there, 

pleaase find in chandev xml the section <p><emphasis>Spamming</emphasis>. 


AFTER that section please add: 

<subsection>
<title>Channel Desynch</title>
<p>There are a few different things that may get your channel desynched.  The most common reason is that the channel does not resynch properly after a netsplit and the settings are different between servers.</p>
<p>There are many means which you can know that your channel is desynched.  The first common thing that happen with most DALnet channels is to see ChanServ's behaviour, for example like setting the mode locks for several time and/or keeps changing the channel topic or changing modes repeatedly.  You may not see what the other person is saying. Basically you can say that things are not in proper order.</p>
<p>If your channel is not synched properly, you only have one way to fix this problem, by making your channel empty from all the users.  You can simply talk with your channel users (if they are few enough) to part the channel for few minutes, or if its hard to do so with all the channel users (if it is a big channel), you can do the masskick command by typing <command>/chanserv MKICK <param>[#channelname]</param></command>, in which this command will kick all users that in your channel, and by this way your channel will be synchronized and organized once again. For more help on masskick command, see <url>http://docs.dal.net/docs/chanserv.html#9</url>.</p>

</subsection>



Then go to section <title>Channel Takeovers</title>

rename this to <title>Channel Takeovers and Miscellaneous</title>
Browse through the text and find the sentence: 

. Setting MAILBLOCK is a good idea if you do not have secured email account but if you set MAILBLOCK on, you will not be able to retrieve the channel password if you lose it.</p> 

This is normally the last sentence of the section. Please continue to write right after this
sentence:


<p>Identification to services impersonators means identifying to non services eg. ChanServ and NickServ. The 2 common ways of telling if it is real services is that services nicknames have ONLY 8 characters with the first 4 characters represent the service and the last 4 is <emphasis>Serv</emphasis>. Also remember that services ONLY connect to <server>services.dal.net</server>. For more information on services impersonation, please read <url>http://docs.dal.net/docs/ircimps.html</url>.</p>
<p>Using of auto-identification scripts is not safe especially when you share your scripts with others. Some scripts contain backdoors that may not send the password to the actual services. It is best to use the <command>/nickserv identify</command> or <command>/chanserv identify</command> rather than losing your nickname or channel.</p>
<p>Sometimes, channel operators may attempt to takeover the channel by simply kicking and banning other channel operators or even the channel founder and lock them out. Fortunately, services have built-in commands that you can use without the need of being in the channel. If you are kick banned from the channel, you can use the UNBAN command included in ChanServ to remove the ban and enable you to return to the channel. Type <command>/chanserv UNBAN <param>#channel</param></command> If you're banned again or find that the operator in question is using a script that kick bans you automatically, use <command>/chanserv deop <param>#channelname</param> [<param>nickname</param>]</command>. This will deop the operator in question. <emphasis type='strong'>Note:</emphasis> You cannot deop someone who has higher access than you have. Example, AOps cannot deop SOps and SOps cannot deop the founder. If you are an SOp or the founder and find that this user is abusive, you can always delete his/ her access without being in the channel. Once you have removed the user and unbanned yourself, you may rejoin the channel. Remember not to op anyone your don't know no matter what the condition is and be careful of how you select your channel staff. It is better to be safe than sorry :-)</p>
<p>Sometimes, you find someone else who is not in the access list is opped and wonder how he/ she got the access. A user may have identified to the Op nick and is using another. To find out how that user got the access, you will use <command>/chanserv WHY <param>#channelname</param> <param>[nickname]</param></command>. Let's take a look at an example. The nick dungunban is not registered and yet he has Op access in #Fleetstreet. When I typed <command>/chanserv WHY <param>#fleetstreet</param> <param>dungunban</param></command>, the following will be displayed:</p>
<commandblock>
<line>-ChanServ- dungunban has SOp access to #fleetstreet.  Reason: Identification to the nickname Road_Runner.</line>
</commandblock>
<p>So, now we know that dungunban has SOp access because he has identified to the nickname Road_Runner.</p>
<p>Another similiar command is the ACC command that tells us the user's access level for that channel. The command is <command>/chanserv ACC <param>#channelname</param> <param>[nickname]</param></command>. Example, I want to know what access does Road_Runner have in #fleetstreet, I would use <command>/chanserv ACC <param>#fleetstreet</param> <param>Road_Runner</param></command>. The following will be displayed:</p>
<commandblock>
<line>-ChanServ- Road_Runner ACC #fleetstreet 2 (SOP)</line>
</commandblock>
<p>For more information on channel access and their levels, please refer to <url>http://docs.dal.net/docs/csaccess.html</url>.</p>




Please save it as usual and rename the file to chandevXX-1.0.1.xml

Have a nice day :)

Fredfred