View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0000557unrealircdpublic2002-12-17 19:082003-11-20 19:46
Reporterparanomix Assigned Tocodemastr 
PrioritynormalSeverityfeatureReproducibilityN/A
Status closedResolutionfixed 
Product Version3.2-beta13 
Summary0000557: Badword Feature
DescriptionAt this time, Unreal will replace all badword in clients message. Why we dont display this message ? I think its usefull for anti ads messages. Example, If clientA say a message include badword (like http://, *porn*) to ClientB, ircd dont relay this message to ClientB.
3rd party modules

Activities

PoisonDart316

2002-12-18 00:23

reporter   ~0000895

Im sorry, but that was pretty bad sentence structure because I couldn't completely understand what you are trying to say, however if im correct, unreal has a badwords block, and you ARE able to have unreal block spam words. It sounded like you were making a statement about the badword feature rather then a bug report

paranomix

2002-12-18 15:43

reporter   ~0000900

Last edited: 2002-12-18 16:15

 CLIENTA send
:ClientA PRIVMSG ClientB :line1 begin
:ClientA PRIVMSG ClientB :line2 oh shit
:ClientA PRIVMSG ClientB :line3 end
* Unreal replace "shit" by "shoot",
CLIENTB receive
:ClientA PRIVMSG ClientB :line1 begin
:ClientA PRIVMSG ClientB :line2 oh shoot
:ClientA PRIVMSG ClientB :line3 end
* If Unreal have dont display feature:
CLIENTB receive
:ClientA PRIVMSG ClientB :line1 begin
:ClientA PRIVMSG ClientB :line3 end
(only lines without badword)

Example in here badword is "shit", replace by "shoot", when message CLIENTA send to CLIENTB "oh shit" become "oh shoot". Do any way that ABC can recognize the badword will not be send or receive ?

edited on: 12-18 16:15

codemastr

2003-04-13 16:52

reporter   ~0002298

Added in .1731, works like:

badword channel {
word "*fuck*";
action block;
};

then any text that matches *fuck* will not be sent to the channel.

Issue History

Date Modified Username Field Change
2003-04-13 16:52 codemastr Status new => resolved
2003-04-13 16:52 codemastr Resolution open => fixed
2003-04-13 16:52 codemastr Assigned To => codemastr
2003-04-13 16:52 codemastr Note Added: 0002298
2003-11-20 19:46 syzop Status resolved => closed