```
4.4.2 Notice
Command: NOTICE
Parameters: <nickname> <text>
The NOTICE message is used similarly to PRIVMSG. The difference
between NOTICE and PRIVMSG is that automatic replies must never be
sent in response to a NOTICE message. This rule applies to servers
too - they must not send any error reply back to the client on
receipt of a notice. The object of this rule is to avoid loops
between a client automatically sending something in response to
something it received. This is typically used by automatons (clients
with either an AI or other interactive program controlling their
actions) which are always seen to be replying lest they end up in a
loop with another automaton.
See PRIVMSG for more details on replies and examples.
```
private: False
* If #653 gets done, notices are much more easier to lose.
tellOnJoin: False
* Many people are using bouncers or running their IRC clients on 24/7 up server, so in many cases joins don't tell anything on are people really present, so it's better to just wait for them to say something.
Enable colours: most of people want them and they are supported by
all IRC clients used nowadays.
Show hostmask: that is standard behaviour of relaybots which I am seeing.
Punish other relaybots: Does this even need explaining? "Let 2009-11-24 <http://echelog.com/logs/browse/supybot/1259017200> be a lesson to you: turn *on* supybot.plugins.Relay.punishOtherRelayBots."
Don't join on all networks: I think that people mostly want to relay
specific networks, not all of them. This is also a method to evade
limitation of LinkRelay ( ProgVal/Supybot-plugins#11 ).
Use notices with nonprivmsgs: This is also standard behaviour and makes
it easier to see the difference between PRIVMSGs and everything else.
It was just said at #Limnoria that someone couldn't install Debian packages
of Limnoria, because haven't been configured to replace supybot.
NOTE: I am not Debian packager, so I have no idea if this works, so please
test it first!
