A logic 'flaw' in the auto-op feature

[AngelofDeath]

I use eggdroop 1.6.12 on a RedHat Linux system fyi

some beginning details
The eggdrop is configured to auto-voice anyone matching the 'allvoice' handle with a *!*@* hostmask within 5-15 seconds
this handle is given the +v #channel tag, and it works fine (+autoop is specified for this channel)

However I noticed that certain people simply were not getting voiced by the bot.

In order to check and see if possibly it wasnt matching the handle, i devoiced the person. (allowed on my particular network) This faked the eggdrop into thinking 'that's a devoiced nick' and it promptly voices it.

The random nicks that are not voiced all have one thing in common, they changed their nickname before the random timer activated the voice.

As a result i believe the nature of this problem to be related to nick change following. I know that you can enable nick tracing to be enabled for kicks (and it is) but I believe that the eggdrop does not impliment/use this function with respect to autoops correctly

I would like to request adding this feature in the next release. possibly as a config option 'trace nick changes globally (note, this can be extremely cpu intensive during a flood)' 0/1 or something

AngelofDeath
irc.infatech.net
#animunkie

[ppslim]

Are you stating the issue is with the auto-op system, or auto-voice system.

Is this only affecting user that have been oped by +autoop, or all users?

If it is all users, then this feature would be usless on most networks.

On the big networks (I havn't clarified this), +o status is the equivilant of +v, plus more powers. Thus, simply having +o, would release the requirment to set +v.

Allthough this is true, being set +v along side +o, can bring benefits to Tcl scripts. This is true up until a certain point.

This system is flawed. When a user joins a channel, each nickname in the channel is listed, along with there mode status. It will either report no modes, @ for +o, or + for +v. However, it does not post a combination.

Thus a person that has been set +v and +o, will look only to be +o. There is no way of checking the +v status.

However, if you feel there is more of an issue here, post back.

[AngelofDeath]

Since the Auto-voice system is dependant on the autoop system, i'd say the autoop
and all the users have a +v flag only

I understand what you mean by if the user has an o already, he may not neccessarily get a +v due to when the ircd passes the user list, the @ infront of the name doesnt include a @+

but this is definately no mistake, ive monitored it for weeks and am not including any of these case scenario's

The user joining simply does not recieve the +v at all if he/she changes their nickname before the timer triggers the +v

Currently this bot functions only to make sure that all users in the channel are voiced (with the exception of any that i -v, and only those)
It does not give +o to anyone.

[ppslim]

Right.

As you stated, this would be a rather CPU expensive idea.

However, a simple script, triggered on a timer at 5 min levels, calling the resetchan command, should in theory solve the problem.

It is doubtful your idea, while sound, would be added, as it would simply add bloat for a function caused by the user.

Auto-voice could simply be ported to a script, to provide this functionalaty.

[AngelofDeath]

Its pretty hard to find good autovoice scripts that work like this one, especially since most of them stoped development due to coded in eggdrop support

[ppslim]

See the bseen archive, it has literaly every scrip there is.