Welcome to the website for evilnet development. We develop: Nefarious IRCu, X3, Exile, and GNUWorld modules mod.auth and mod.chanfix.


Documentation- Opping Logic

Automatic Fix

If a channel becomes opless, and there are scores in chanfix's database for this channel, chanfix will try to fix this channel. In other words, it will give ops to the clients it thinks deserve it the most.

For each automatic opless channel fix (autofix), a time window of 60 minutes is reserved. During this window chanfix will op eligible clients. Atleast one client each time.

There are, of course, requirements to the minimum score that you need to have before chanfix will op you. This minimum score is determined both from the absolute maximum score that can be obtained, and from the maximum score available in the channel that is being fixed.

The first time that chanfix ops clients, it will only op clients with:
- at least 90% of channel_max_score (variable)
- and at least 40% of max_score (default: 0.4 * 4032 = 1613)

The last time that chanfix can possibly op (which is after the autofix_time_maximum has passed), it will only op clients with:
- at least 30% of channel_max_score (variable)
- and at least min_score (default: 0.04 * 4032 = 162)

In between, chanfix will use a linear formula to determine the decrease of these values over time.

Numbers are bad, pictures are good, so let's look at two pictures, the first for a channel with channel highscore 2600 points, and the second for a channel with a maximum score of only 1200 points.

 

In the first picture you see what happens if you have a channel with a high score. Clients in the area marked green have a high enough score to be opped. So from time 0 until time 60, chanfix could op clients that have a high enough score. The more time passes, the lower score chanfix will accept for giving ops.

The second image shows a situation where the maximum channel score is relatively low (only 1200). This means that there are no clients yet who are above the 40% of the maximum (4032) limit, and therefore chanfix will not pass out ops immediately. Up to time t1, chanfix will not give any ops in the channel.

Opping logic example

Channel #a has a maximum score of 2400. The last opped client leaves.

When chanfix first ops clients, only clients with at least 0.9 * 2400 = 2160 and at least 0.4 * 4032 = 1613 will be opped, so only clients with more than 2159 points will be opped.

If chanfix would op a last time at the end of the 60 minutes, it would op clients with at least 0.33 * 2400 = 800 points. Lower scores will never be opped.

When chanfix ops clients after 20 minutes (which is 1/3rd of the total window for fixing), it will only op clients with
at least 2160 - 0.33 * (0.9-0.3) * 2160 = 1728
and at least 1613 - 0.33 * (1613-100) = 1109
points, i.e. at least 1728 points.

Determining the end of a fix

As soon as autofix_num_opped clients are opped in the channel, either by chanfix or by the clients which were opped earlier, the fix is considered complete.

If the channel has fewer than autofix_num_opped clients, then the fix is considered complete as soon as all clients are opped.

As soon as chanfix can see that there is at least 1 opped client and no more clients have a score that is high enough to get opped, the fix is considered complete.

Under no circumstances will chanfix give ops if that would result in having more than autofix_num_opped opped clients (chanfix itself excluded).

Under no circumstances will chanfix give ops to any client with a score lower than min_score.

Under no circumstances will chanfix give ops to any client with a score lower than 0.3 * channel_max_score.

Manual Fix
Now, for a manual chanfix the procedure is as follows:
- First, C removes all restrictive modes and bans.
- Then, C waits chanfix_initial_interval minutes.
- After that, autofixing starts with exactly the same algorithms as described above.

Webmasters

Syndicate

Link Images

X2 IRC Services
X3 IRC Services
GPL Licensed
Evilnet Development
Nefarious IRCu
mod.Chanfix

Sourceforge

SourceForge.net Logo

Search

Latest News

X3 1.5 Released
For those of you who have been using X3 off SVN this will be old news. But for the people who have never used and/or heard of X3 before this is relevent. X3 is a set of irc services based off srvx. De...
Read More ...
Nefarious IRCu 1.0.1 Released
Thats right a new release of Nefarious IRCu. We highly reccommend that you upgrade from 0.4.0 especially if you are running the tarball version of 0.4.0. This version is still based on 2.10.11. This w...
Read More ...
New features in X3
Check it out! X3 has had some nice new features added in the last few months! ...
Read More ...
nefarious host-in-topic security flaw
Nefarious 1.0 (0.5) with svn versions prior to 1699 are vulnerable to anexploit in the host-in-topic code. If you are using either the 0.5 development branch, or an early 1.0 stable release prior to t...
Read More ...
GNUWorld HOWTO
Lately ive been working on the Undernet GNUWorld howto document, bringing it up to date and adding various bits. This howto does include instructions for our mod.chanfix and mod.auth so use this howto...
Read More ...

Who's Online

We have 3 guests online

OpenSource