Menu
▾
▴
#31 INDIRECT flag
INDIRECT flag.
----------------------
Players set INDIRECT will never receive any
normal 'game' text from the server directly, unless sent
by a program in one of the LISTEN propqueues.
*Idea behind this:
Server side proprocessing of output; automatic detection
and highlight of player names in text, etc, for players
individually. Really just something for version 2.0, until
then, there's more urgent things than this.
´
Keep up the excellent work, Protocoders.
Logged In: YES
user_id=42132
That's an unusual idea, but I can see the merits of it. I'll keep
it in mind for the future. The only hang up that I can see is
that there's a lot of text that gets notifed to players that is
considered 'non-listenable'. Things like MUF Editor output,
examine output, among other things, are not notified to
listening/ props as a way to save CPU time, since handling
listeners is actually a very time-consuming part of the
notification routines.
This wouldn't be hard to implement at all, but there's just a
lot of ramifications to keep in mind.
-Akari
Logged In: YES
user_id=42132
I've been trying to think of a different way of going about this
and two ideas present themselves. I might implement one or
the other or both, depending on what the demand is:
Approach #1)
Add a '@filter/' propqueue that would only be on the object
being notified. When a player has a '@filter/' propqueue
program, that program is called any time that player would
have been notified by any means. The only way to actually
notify the player would be a new NOTIFY_NOFILTER prim
(which one would presumably use in whatever program was
called by the @filter/ propqueue).
Approach #2)
Make a @tune 'filter_prog' command that would get called
ANY time a player was being notified something. Only 'notify*'
prims used by the filter_prog would actually get notifed, every
other notify on the MUCK (in-server and in MUF) would get
sent to the filter_prog @tune instead for pre-processing.
I like the first idea a little bit better than the second, because
then it's player-specific and I think it would do what you
wanted. Just a thought. Might be easier in implementation
and actual use than an INDIRECT flag.
-Akari