-
Notifications
You must be signed in to change notification settings - Fork 0
/
regnames.html
138 lines (123 loc) · 4.88 KB
/
regnames.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
<html>
<head>
<title>The MUCK Manual: Registered Names</title>
</head>
<body bgcolor="#FFFFFF">
<center>
<a href="triggers.html">prev</a>|
<a href="toc.html">toc</a>|
<a href="patmatch.html">next</a>
</center>
<table>
<tr>
<td width="20%"> </tc>
<td>
<!-- BODY CONTENT HERE -->
<p><b>2.1.5 Registered Names</b></p>
<p>Objects can be specified by `registered names' as well as by names
and dbrefs. A registered name is an alias that can (like a dbref) be
used regardless of the object's location, but (like a name) consisting
of a memorable string. The primary use is to provide a convenient,
memorable way of specifying an item, regardless of its location and
ownership. For example, a player on a large <code>MUCK</code> might have
a puppet with a long, difficult to remember dbref, such as
<code>#128629.</code> If the player frequently wanted to teleport the
puppet to her from somewhere else, she would need to either memorize the
dbref or repeatedly retrieve it with the <code>@find</code> command. As
an alternative, she could give the puppet an easy-to-remember registered
name such as `pup'. From that point on, the puppet could be specified
with the name `pup' preceeded by a <code>$</code> dollar sign, rather
than by dbref.</p>
<p>Players can create registered names — usuable only by the player
— with the <code>@register</code> command, syntax <code>@reg #me
<object> = <registered name></code>. (The information is
stored in the player's <code>_reg/</code> directory.)</p>
<p><code>
====================================<br>
> @find Squiggy<br>
Squiggy(#128629XZ)<br>
***End of List***<br>
1 objects found.<br>
> @reg #me #128629 = pup<br>
Now registered as _reg/pup: Squiggy(#128629XZ) on Jessy(#2PWQX)<br>
> @tel $pup = me<br>
Teleported.<br>
> i<br>
You are carrying:<br>
Squiggy(#128629XZ)<br>
You have 5086 pennies.<br>
===================================<br>
</code></p>
<p>Individual registered names may also be set when an object is
created. The standard creation commands — <code>@create, @dig,
@action</code>, and <code>@open</code> — each take two optional
argument fields, separated by = equals signs. The first of these fields
is specific to each command; the second field for all four may be used
to specify a registered name. </p>
<p><pre>
@create <name> = <cost in pennies> = <reg name>
@dig <name> = <parent room> = <reg name>
@action <name> = <source> = <reg name>
@open <name> = <link> = <reg name>
</pre></p>
<p><code>
====================================<br>
> @create Mary Poppins Umbrella == umbi<br>
Mary Poppins Umbrella created with number 226.<br>
Registered as $umbi<br>
> ex $umbi<br>
Mary Poppins Umbrella(#226) Owner: Mistral<br>
Type: THING<br>
Created: Fri May 09 14:33:47 1997<br>
Modified: Fri May 09 14:33:47 1997<br>
Last used: Fri May 09 14:33:47 1997<br>
Usecount: 0<br>
> ex me=_reg/<br>
ref /_reg/umbi:Mary Poppins Umbrella(#226)<br>
<br>
> @dig OOCafe = #143 = cafe<br>
OOCafe created with room number 225.<br>
Trying to set parent...<br>
Parent set to OOC Environment(#143RL).<br>
Room registered as $cafe<br>
<br>
> @open Enter Garden = $garden = gogard<br>
Exit opened with number 224.<br>
Trying to link...<br>
Linked to Secret Garden(#455R).<br>
Registered as $gogard<br>
====================================<br>
</code></p>
<p>Wizards can set global registered names — usuable by all players —
syntax <code>@reg <object> = <registered name></code>. A
frequent and convenient use of global registered names is to provide an
alias for publicly available programs such as `do-nothing' and
`obvious-exits'. Without global registered names, players would need to
find the dbrefs of these programs each time they needed them for
building purposes. Since the players do not control these programs,
finding the dbrefs can be difficult. (To create a personal registered
name as a wizard, use the <code>#me></code> option: <code>@reg #me
<object> = <registered name>)</p>
<p><code>
====================================<br>
> @find obv<br>
gen-Obvexits(#2002FLM3)<br>
***End of List***<br>
1 objects found.<br>
> @reg #2002 = exits<br>
Now registered as _reg/exits: gen-Obvexits(#2002) on The Void(#0R)<br>
> @succ here = @$exits<br>
Message set.<br>
====================================<br>
</code></p>
<center>
<a href="triggers.html">prev</a>|
<a href="toc.html">toc</a>|
<a href="#top">top</a>|
<a href="patmatch.html">next</a>
</center>
</td>
<td width="20%"> </tc>
</table>
</body>
</html>