@lock/dropto Who can trigger this container's drop-to.
@lock/destroy Who can destroy this object if it's DESTROY_OK
@lock/interact Who can send sound (say/pose/emit/etc) to this object
+ @lock/take Who can get things contained in this object
See also: @lock, @lset, @clock, FAILURE
& @lset
The /list switch to this command allows you to @pemit a message to
a list: @pemit/list <object 1> [<object 2> <object N>] = <message>
- There can be any number of objects in the list. The objects must be
- specified by dbref number. You will not get back a "confirmation"
- message for the /list form of this command.
+ There can be any number of objects in the list. You will not get back a
+ "confirmation" message for the /list form of this command.
(continued in help @pemit2)
& @pemit2
get <object>
take <object>
- You pick up object, if you pass the object's @lock. You can also do
- get <thing>'s <object>, which will fail if either thing is not ENTER_OK
- or the object is locked against you. Some MUSHes choose to disable the
+ You pick up object, if you pass the object's @lock and the container's
+ @lock/take (if set). You can also do get <thing>'s <object>, which will
+ fail if thing is not ENTER_OK, thing has a take-lock that blocks you,
+ or object is locked against you. Some MUSHes choose to disable the
ability to take an object in someone else's inventory.
See also: @lock, ENTER_OK, give, drop, @success, inventory
See also: match(), matchall(), grab(), regmatch()
& GREP()
& REGREP()
+& WILDGREP()
+& GREPI()
+& REGREPI()
+& WILDGREPI()
grep(<object>,<attrs>,<substring>)
wildgrep(<object>,<attrs>,<pattern>)
regrep(<object>,<attrs>,<regexp>)
preferred one.
X - Never return #-2. Use the last dbref found if the match is
ambiguous.
- If you specify more than one type, the last one will be preferred. Unless
+ If you specify more than one type, any will be preferred. Unless
you specify an F option, if an object of a different type is found and
none of the preferred type are, the found object will be returned.
Returns the dbref number of the object, which must be in the same
room as the object executing num.
+& NMWHO()
& NWHO()
nwho()
+ nmwho()
This returns a count of all currently-connected players. When
- mortals use this function, DARK privileged players are NOT counted.
+ mortals use this function, hidden players are NOT counted.
-See also: lwho(), nmwho(), xwho()
+ nmwho() returns a count of all currently connected, non-hidden players.
+ It's exactly the same as nwho() used by a mortal, and is suitable for use
+ on privileged global objects that always need an unprivileged count of
+ who is online.
+ These functions are equivilent to words(lwho()) and words(mwho()),
+ but are more efficient, and don't suffer from buffer constraints.
+
+See also: lwho(), mwho(), xwho(), xmwho()
& OBJ()
obj(<object>)
or ROOM. See "help types of objects" for more.
& U()
& UFUN()
+& ULAMBDA()
u([<object>/]<user function name>, <arg 0>, <arg 1>, ...)
ufun([<object>/]<user function name>, <arg 0>, <arg1>, ...)
+ ulambda([<object>/]<user function name>, <arg 0>, <arg1>, ...)
This allows you to create your own functions and evaluate them.
<user function name> is the attribute that contains the desired
<arg 0>, <arg 1>, ... are the arguments that get passed to the
user function as v(0), v(1), etc. (as in @trigger). You can pass
- up to 10 arguments (v(0) through v(9)); extra arguments will be
- evaluated but not accessible (since v(10) refers to an attribute,
- not another argument).
+ up to 10 arguments (v(0) through v(9)).
This function is also known as U() (alias for TinyMUSH compatibility).
+ ulambda() also accepts anonymous attributes.
+
See "help UFUN2" for more.
& U2