Mostly this is just to check this is OK, and to
question if it's actually useful. It uses not the user
but the owner of the sex property being checked as "me"
so this script:
@set me=sex:{tell:{name:me},this}
will only ever tell the owner of that sex prop his or
her own name.
When is this useful, especially since all the ws
programs I know will display that MPI? (The ws program
on my muck will trigger the MPI, though, since it uses
pronouns to pick a color for ANSI-enabled users.)
Logged In: YES
user_id=6331
This is actually mostly due to an odd side effect of parsing
MPI for locks, as the gender code uses the same routine to
find the user's gender. Umm, yeah, the 'me' should be the
checking user, but I'm not sure if that's always possible to
provide. I'll have to look later.
Logged In: YES
user_id=57367
Also you can spam yourself nicely with these few lines of
code:
@set me=sex:{pronouns:%s}{tell:Hello}
@mpi {pronouns:%s}
However this fortunately doesn't crash, although it's not
particularly nice :>
Parsing MPI in sex sounds something of a security issue
too... Might be time to add a "RESTRICTED" flag to the mpi
parser which only allows props reads and logic to be called,
everything else silently aborts...