#6 Multiple MOTDs

[Keith Gable]

There needs to be several sets of MOTDs.
1) A short MOTD that is displayed when users connect.
To get the "real" MOTD, they would type /motd. Most
IRCDs support this. Filename: ircx.smotd
2) A operator MOTD that is displayed when any user
becomes any level of oper. This would be displayed
with /OMOTD. No IRCDs I know of support this, but it
might be useful to let your opers know of news or
whatever. Filename: ircx.omotd
3) A locoper MOTD that is displayed when any user
becomes a locoper. This would be displayed instead of
the generic operator MOTD (as described in 2), but only
to locopers. Again, no IRCDs I know of support it, but
it's a useful idea. Filename: ircx.lomotd
4) A globoper MOTD that is displayed when any user
becomes a globoper. This would be displayed instead of
the generic operator MOTD (as described in 2), but only
to globopers. No IRCDs I know of support it.. yada
yada.. Filename: ircx.gomotd
5) All oper MOTDs (globoper/locoper/general) would be
recalled with /OMOTD. Basically, the globoper/locoper
MOTD overrides the generic operator MOTD, if they exist.
6) Operator MOTDs will not be used if ircx.omotd,
ircx.lomotd, and ircx.gomotd are missing or blank.
Additionally, if a generic OMOTD doesn't exist, and the
user's level of MOTD doesn't exist, no OMOTD will be
displayed.
7) SMOTDs will only be shown if ircx.smotd exists and is
not blank.

This would also require a MOTD manager, because who
the hell is going to know what to do in this situation:

ircx.motd
ircx.smotd
ircx.omotd
ircx.lomotd
ircx.gomotd

It'd be a lot easier to add tabs or something and let the
user type it there ^^,. Maybe a checkbox for "don't use
<type> MOTDs".

[M2Ys4U]

Logged In: YES
user_id=953136

"A operator MOTD that is displayed when any user
becomes any level of oper. This would be displayed
with /OMOTD. No IRCDs I know of support this, but it
might be useful to let your opers know of news or
whatever. Filename: ircx.omotd"

AFAIK, dancer ircd uses this :)

[Keith Gable]

Logged In: YES
user_id=919946

Ah, well, didn't know.

This is being integrated into the snap-in. BTW -- it's a
PITA, but very cool nonetheless.

Next step: XML config file.