forked from TinyMUSH/Historical-TinyMUSH
-
Notifications
You must be signed in to change notification settings - Fork 0
/
CONVERT.MUX
331 lines (217 loc) · 11 KB
/
CONVERT.MUX
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
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
If you are converting your game from TinyMUX 1.x, upgrading to TinyMUSH
3.1 is just like doing a MUX version upgrade, with some additional
steps. You will need to do the following:
- Flatfile your database using the dbconvert utility from TinyMUX
(the db_unload script will work -- this is just like doing a normal
backup of your database).
- Copy that flatfile to some safe place, and save it.
- Edit mush.config and make sure it's correct (it should basically be
like your old mux.config file).
- If the GAMENAME parameter in your mush.config file is not 'netmush',
edit your GAMENAME.conf file (substitute whatever you set GAMENAME to
for GAMENAME).
- Compare your GAMENAME.conf file to the default netmush.conf file.
You'll note that there are some new parameters and some changes to
old defaults. Update your conf file to reflect these changes. Two
things that you'll definitely want to add are:
helpfile news text/news
raw_helpfile man text/mushman
- If you have the following parameters set, simply remove them:
cache_depth
cache_width
input_database
output_database
mail_database
comsys_database
have_comsys
have_mailer
format_exits
format_contents
- If you were using the built-in comsys, add this line:
module comsys
- If you were using the built-in mailer, add this line:
module mail
- If you had your database files in the data directory, add this line:
database_home data
(If you have your database files in another directory, substitute that
in instead. Pathnames are relative to the ~/3.1/game directory.)
- If you have the gdbm_database parameter in your conf file, edit it
to take away any prepending path. For instance, if your conf file reads:
gdbm_database data/netmush.gdbm
change it to read:
gdbm_database netmush.gdbm
- If you have the crash_database parameter in your conf file, edit it
to take away any prepending path. For instance, if your conf file reads:
crash_database data/netmush.db.CRASH
change it to read:
crash_database netmush.db.CRASH
You should also look at the "Compatibility Notes" section below, for
any other configuration parameters you'll need to add or change.
- Assuming that your flatfile is in the 'game' directory, go into the
'game' directory ('cd game').
If you have perl installed on your system, type:
./cvtmux.pl < mygame.flat > NEW.flatfile
If you do not have perl installed on your system, type:
sed -f cvtmux.sed mygame.flat > NEW.flatfile
(Substitute the name of your flatfile for 'mygame.flat'.)
This will take care of converting function calls to backwards-compatible
versions, and the '%c' substitution to the '%x' substitution.
- From the game directory, type: ./Restore NEW.flatfile
This will unflatfile (load) your database into TinyMUSH 3.1 format.
- From the game directory, type: ./Backup
This will back up your datbase in TinyMUSH 3.1 format.
(This step is not necessary and can be skipped, but it's worthwhile
doing anyway.)
- Convert your comsys database. You must have perl installed on your
system. From the game directory, type:
cp comsys.db comsys.db.save
./convert_comsys.pl < comsys.db.save > mod_comsys.db
Make sure to keep comsys.db.save someplace safe, in case something goes
wrong in the conversion process.
If you do not have perl installed on your system, you will not be able
to import your comsys database. (You could give a copy of the database,
and the script, to a friend with perl on his system, and have him do
it for you, though.) If you can't find a way to convert your comsys
database, type: mv comsys.db comsys.db.save
- Rename your mail database to the new 3.1 name:
mv mail.db mod_mail.db
- From the game directory, type: ./Startmush
This will start the game.
-----------------------------------------------------------------------------
Compatibility Notes
You will want the following parameters in your conf file, for maximum
TinyMUX compatibility:
global_aconn_uselocks no
lattr_default_oldstyle no
addcommands_match_blindly yes
addcommands_obey_stop no
helpfile +help text/plushelp
helpfile wiznews text/wiznews
access wiznews wizard
Also, the default netmush.conf file has 'raw_helpfile news text/news' in
it. If you want the old MUX behavior of 'news', where percent-substitutions
and ANSI are evaluated in the news file, you will need to change that
line to 'helpfile news text/news' instead.
Note that unless you explicitly need the legacy behavior of @addcommand'd
commands (you want no Huh? message generated if an @addcommand is missed,
and you match multiple @addcommands at once), you should probably set
the last parameters to the opposite of their MUX-compatibility defaults.
-----------------------------------------------------------------------------
Altered Behavior
The following are important changes in behavior between MUX and 3.0:
- MUX used '%c' for ANSI color. 3.0 uses '%x' for ANSI color ('%c' is
the last-command substitution, as it is in PennMUSH and TinyMUSH 2.2.)
- MUX ifelse() conditioned on a non-zero result. 3.0 ifelse() conditions
on a boolean-true result. To get the old behavior, use nonzero().
- pmatch() now works as documented (i.e., identical to its PennMUSH
predecessor). To get the old behavior, use pfind().
- Objects are now checked for commands if they are set COMMANDS (instead
of not being checked for commands if they are set NO_COMMAND).
- ZMOs are now controlled by their ControlLock, not their EnterLock.
Only objects that are set CONTROL_OK may be controlled according to
their zone's ControlLock.
- The COMPRESS flag has been eliminated. It was unused in MUX, though
you could manually set it on objects.
- The WATCHER flag is now used to watch logins, rather than MONITOR.
The power to do this is now called Watch_Logsin, and it allows
you to set WATCHER on objects that you own (rather than on objects
that you control).
- There is no longer a /dbref switch for @decompile; just use
'@decompile <object>=<dbref of object>' to get the same effect.
Your existing database was converted automatically to take the above
differences into account.
The comsystem has been re-implemented. Some significant differences
include:
- If you are starting a game from scratch, and thus have no comsys.db,
on startup, the Public and Guests channels are created by default.
- The channel administration commands have been consolidated to a
single command, @channel, which takes a variety of switches. Channel
objects are no longer necessary; data from them is automatically
imported when you load a comsys database of the format generated
by the convert_comsys.pl script.
- Multiple aliases for a single channel work in a much saner manner.
Each alias can be associated with a different comtitle.
Other changes to be aware of:
- Two additional categories have been added to the stats() function. If
you have softcode that extracts the number of garbage objects in the
database from stats(), it will be fine if you used last(stats()) to
get the data; if you used extract() or another function that depended
upon list position, you will need to modify your code.
- Though MUX's help files documented the behavior of teleport locks, the
implementation didn't reflect the help. The implementation now works
the way help says it does.
-----------------------------------------------------------------------------
The following is a list of features/functions that were in TinyMUSH 2.2.5,
but were not in TinyMUX 1.6, and which have become part of 3.0.
For a more general look at TinyMUSH 3.0 changes, see the CHANGES file.
- Quotas by object type supported.
- Added building_limit conf parameter.
- Added player_parent, room_parent, exit_parent, thing_parent conf
parameters for default parent objects.
- Added log options keyboard_commands and suspect_commands.
- Decent password choices are enforced via safer_passwords.
- Guest can be locked out from sites via the guest_site parameter.
- SIGUSR1 is logged, and the game restarts as GOD, not #1.
- Note is written to log after @startup queue is run.
- Disconnect log includes command count, bytes input, and bytes output.
- New COMMANDS flag, the reverse of the NO_COMMAND flag, which has been
eliminated.
- New STOP flag, halts matching if a command is matched on a STOP object.
(Wizard-only.)
- NOSPOOF is only wiz-visible.
- The color substitution is now '%x' rather than '%c'.
- The '%c' substitution returns the last command.
- Added "lag checking".
- Added timechecking.
- @daily is now implemented using the @cron facility.
- @dump/optimize no longer exists, since the database is optimized after
every dump.
- @doing truncates the minimum possible (i.e., don't truncate for the ANSI
character unless necessary).
- Added @dolist/notify.
- @enable/@disable now appear in the logfile, like config updates do.
- Added @eval command.
- examine/brief now shows everything but the attributes on the object.
- INFO command implemented.
- Added '@list cache'.
- Hash statistics listing shows stats for @function hash table.
- @mvattr no longer clears the original attribute unless it was able
to copy it at least once.
- @pemit/noeval permits unparsed output.
- @pemit/list now obeys the /contents switch.
- There is a space after the @program prompt (2.2 behavior).
- Added object count to @search.
- @stats shows the next dbref to be created.
- The #$ @switch/switch() token has been added.
- Added @conformat and @exitformat contents and exits formatting.
- Command matches can be done unparsed through no_eval attribute flag.
- New BOUNCE flag acts like equivalent of @listen of '*' without @ahear.
- Added bor(), band(), bnand() functions.
- die() checks its arguments 2.2-style (so 0-100 is valid).
- Added filterbool() function.
- ifelse() now conditions on a boolean, rather than on a non-zero number.
- Added nonzero() function, which behaves like ifelse() used to.
- lastcreate() and the NewObjs attribute keep track of last-created
objects for a given thing.
- Added lpos() function.
- matchall() returns a null string, not 0, on no match.
- mix() can take up to ten arguments total.
- objeval() now preserves the cause (enactor) in the evaluation, and
allows the calling object to succeed if its owner is the same as
the evaluator's owner, instead of needing to _be_ the evaluator's
owner (2.2 behavior).
- Added programmer() function.
- Added remit() function, like pemit() but does contents.
- restarts() and restarttime() added.
- Added sees() function.
- shl(), shr(), inc(), dec() no longer require inputs to be numbers
(2.2 behavior).
- Added t() function.
- Added toss() function.
- Vector functions replaced by 2.2 ones, including addition of vdot().
This means that vector multiplication now works, but it breaks the
old MUX behavior of vmul().
- Added wipe() function.
- Added xcon() function.
- elements(), filter(), map(), munge(), setunion(), setinter(), setdiff(),
shuffle(), sort(), sortby(), splice() take output delimiters.