@oemit/list - oemit()

[brazilofmux]

Original issue 92 created by brazilofmux on 2006-09-12T07:03:10.000Z:

@pemit allows for the /list command for sending to a list of dbref#s, and this behavior is also
replicated by the handy-dandy side-effect function pemit(). However, @oemit has no such
switch, which while not quite essential, would be nice if you're sending specific messages to
different players.

IE: Suppose you have a softcoded command that allows a player to perform a specific action on
another player, let's call it 'badoof'. It generates three messages: 'You badoofed player!' is sent
to the enactor. '%n badoofed you!' is sent to victim. '%n badoofed player!' is sent to everyone else
in the room. For bonus points we throw in color highlighting to the enactor and victim to get
their attention, but not to everyone else.

Current hardcode allows this, but requires filtering of your pemit() targets by setdiff()ing out the
enactor and victim. Not terrible, but likely to break if used in high population rooms. (IE,
Shangrila's # 0, # 69, OBG, perhaps).

I would suggest @oemit/list, that would behave in the following manner: An @oemit would be
sent to the room of the first dbref# on the list, except to players on the list. As the default
@oemit behavior sends messages to the locations of the targets, this would ensure that only one
location is spammed with the oemit.

[brazilofmux]

Comment #1 originally posted by brazilofmux on 2006-09-12T13:58:06.000Z:

Classified as an Enhancment not a defect.

[brazilofmux]

Comment #2 originally posted by brazilofmux on 2006-11-15T20:21:55.000Z:

The would be divergent behavior from PennMUSH. PennMUSH does not require /list in
order to provide a list, and PennMUSH will @oemit to the location of each <object>
in the list -- not just the location of the first one.

@oemit[/<switch>] [<room>/]<object> [<object>...] = <message>

This command shows <message> to everyone in the location of <object>
EXCEPT <object>. The object can be specified by name if in your current
location, or by DBREF number. A list of objects can be given, in
which case the message is shown in all locations to all except those
objects.

If a room is specified (usually via dbref), this command shows
<message> to everyone in <room> except for <object> (which may be
a list, as above). In this case, object(s) are matched with reference to
<room>. Therefore, if you want to send a message to everything but an
object called "spy" in # 100, you can simply use "@oemit # 100/spy=Test";
you don't need to know the dbref of "spy".

The /noeval switch prevents the MUSH from evaluating the message.
The /spoof switch causes nospoof notifications to show the enactor's
dbref instead of the executor's dbref, and requires control over
the enactor or the Can_nspemit power.

See also: @emit, @pemit, NOSPOOF and SPOOFING.

[brazilofmux]

Comment #3 originally posted by brazilofmux on 2006-11-28T05:55:24.000Z:

Take all speech stuff for the same milestone.

[brazilofmux]

Comment #4 originally posted by brazilofmux on 2007-01-10T03:53:19.000Z:

Schedule for later. There are too many items in 7.2A02.

[brazilofmux]

Comment #5 originally posted by brazilofmux on 2007-09-21T00:43:20.000Z:

<empty>