egghelp/eggheads community

Error with Unreal3.2 extended bans

2004-07-26T03:56:18-04:00

I'll have a look. Unreal changes things constantly, so Eggdrop is naturally going to have some problems on it. This shouldn't be too hard to fix.

BTW guys, the best place to report bugs is to the Eggheads Development Team, not here. Bugs will be addressed quicker if they are sent in to bugs@eggheads.org, or better yet, added directly to BugZilla at [url]bugzilla.eggheads.org[url].

Wcc

Statistics: Posted by Wcc — Mon Jul 26, 2004 3:56 am

Error with Unreal3.2 extended bans

2004-07-25T07:03:13-04:00

i too have noticed this since moving my eggdrop to a network running unreal 3.2
very annoying problem :/

Statistics: Posted by Guest — Sun Jul 25, 2004 7:03 am

Error with Unreal3.2 extended bans

2004-07-02T10:35:06-04:00

I have currently been testing unreal 3.2 and while checking the extended bans, i have come aware that the eggdrops (as well as services unban command) don't remove the extended bans.

For those who aren't familiar with Unreal, the extended bans are in the form ~q:nick!ident@host ~r:*realname* or ~c:#channel.

Logically, i would have thought eggdrops would have been able to cope with these bans, as they can be set on any server type, just unreal does something with this format.

Currently, the eggdrops will list the ban in its internal banlist and will say its removing the ban if you use .-ban blah blah, but it won't actually remove the ban. It will also overlook the ban when the alloted ban-time is over and only remove the normal bans.

Statistics: Posted by Guest — Fri Jul 02, 2004 10:35 am