Emote() [REF: Job 186]

[brazilofmux]

Original issue 38 created by brazilofmux on 2006-09-09T01:33:37.000Z:

On Fri Feb 25 17:32:57 2005, Anomaly suggested:

emote(<player>,<pose>,[<prefix>])

This command will evaluate <pose> (",:,;) and prefix it with <prefix>.

Ex:
>think emote(Bob,:waves.,<OOC>%b)

<OOC> Bob waves.
>think emote(Bob,Hi,<OOC>%b)
<OOC> Bob says, "Hi."

This would take into account any @saystring. Players who can access it
would be the calling player, or a wiz-inherit object.

On Fri Feb 25 17:57:20 2005, Ian added:

This kind of behavior is trivial and cheap to emulate. oemit() would be a
far more useful thing to impliment.

On Fri Feb 25 18:23:57 2005, Ian added:

As Ash as pointed out.. oemit() already exists in MUX. Doh. Anyways, this
is still the type of thing that deserves to be softcoded. :)

On Fri Feb 25 19:39:33 2005, Ronan added:

Additional comments from Anomaly since he can't access +jobs here: With
oemit you have to write switches or cases or other filters to filter 'is
this a say?' 'is this a pose?' 'is this a pose-without space'? emote makes
it easier to process that information. It is useful for OOC commands,
language code, table code, anything that has to process a pose into a
broadcast.

[REF: Job 186]

[brazilofmux]

Comment #1 originally posted by brazilofmux on 2006-11-28T05:52:01.000Z:

Take all speech stuff for the same milestone.

[brazilofmux]

Comment #2 originally posted by brazilofmux on 2007-01-10T03:55:43.000Z:

Schedule further out. 2.7A02 is already full.

[brazilofmux]

Comment #3 originally posted by brazilofmux on 2007-08-25T21:01:07.000Z:

Just a note - if such a function was added, would it not make sense to call it pose
(), in keeping with the precedent of functions and commands with similar
usage/purpose having the same base name?

[brazilofmux]

Comment #4 originally posted by brazilofmux on 2007-09-20T23:50:49.000Z:

<empty>