| |
|
Please follow these instructions carefully, executing
commands as a wizard except where indicated. You may want to read
through the instructions once before actually doing anything.
First off, you'll need to create a MudNet
player. Use a password that's not easily guessable.
| @pcreate
MudNet=<password> |
If your MU* has a system of character
setup that new players have
to go through before they can do anything else, get MudNet through it.
Give MudNet the idle power, or a
really long timeout to avoid
random disconnects.
| @power *mudnet=idle | for TinyMUX, TinyMUSH 3, or PennMUSH |
| @timeout *mudnet=1000000000 | for TinyMUSH 2 |
| @timeout *mudnet=-1 | for RhostMUSH |
Give it infinite money to avoid
running out and being unable to queue commands (even if you have a daily
paycheck, it may not reconnect often enough to stay afloat, and the penn
softcode usually requires more money to install than the player starts
with)
| @power *mudnet=free_money | for TinyMUX or TinyMUSH 3 |
| @power *mudnet=no_pay | for PennMUSH |
| give *mudnet=1000000000 | for TinyMUSH 2 |
Give it the builder power or some
quota if your MU* requires it; the softcode installation
creates a handful of objects.
If you're using TinyMUSH 3 or MUX (older than
2.0.21.308p6), you'll need to give MudNet the long_fingers
power to allow it to @pemit/list to non-player objects. This bug
does not affect TinyMUSH 2, PennMUSH, RhostMUSH, or newer MUX servers.
| @power *mudnet=long_fingers |
Dig it a quiet floating home to
avoid spamming the bot with people going in and out, etc.
| @fo *mudnet={@dig/teleport MudNet's Home;
@set here=floating; @link me=here} |
Now, you need to download one of
the following, log in as the MudNet character, and upload
the file to install the softcode:
After a bunch of Set. messages, they'll finally
stop and you can safely log out of the MudNet character after
you see a "Done Uploading MudNet Softcode" message. Don't
worry if you see a couple "Huh?" or "No such flag" messages from the
Tiny install code, since it's meant to work on multiple server types.
You'll probably also see some delays due to the number of comments in
the code.
Continuing as a wizard, place the Mudnet Globals
in the master room. This object can be found in
Mudnet's inventory or location.
On a PennMUSH, you will need to add the
mnelock() function so that MudNet has permission to
evaluate mnlocks on wizards. Normally the SAFER_UFUN option prevents
MudNet from doing so. You may need to do this as #1, and add the @function
line to #1's @startup. This code is approved as "safe" by Javelin and
Talek.
| &fun_mnelock #1=[switch(%@,num(*MudNet),u(%0/mnlock,%1,%2,%3,%4,%5,%6,%7,%8,%9),#-1 PERMISSION DENIED)] |
| @function mnelock=#1, fun_mnelock |
Fill in the mninfo with a
description of your MU*.
| &mninfo *mudnet=Blah blah we're a MUSH
etc. |
If your MU* uses other names for
+who (softcoded WHO list with better style or different
info), +staff (list of wizards and staff showing who's
connected), or +finger (IC or OOC profile on a specific
player), or other commands used by MudNet, please add
custom handlers for these commands so that MudNet can
use them. For example,
&TRH_FINGER *mudnet=@pemit me=%vkRSTARTrequest|%0;+id %6;@wait 2=@pemit me=%vkRENDrequest|%0 |
if your MU* uses +id instead of
+finger. |
&TRH_STAFF *mudnet=@pemit me=%vkRSTARTrequest|%0;+admin;@wait 2=@pemit me=%vkRENDrequest|%0 |
if your MU* uses +admin instead of
+staff. |
Note you'll need to use @pemit/silent
in these examples if you have a PennMUSH, otherwise the @pemit feedback
might expose your hostkey (%vk) to a remote user.
If you need help with customization, try asking on the
mudnet-users list. I'll
eventually add more information on the website (see also the
mnlock documentation and the comments
that appear in the install
scripts). Here's another example,
Brandy mailer support on a PennMUSH:
&TRH_MAIL *mudnet=@pemit/silent me=%vkRSTARTrequest|%0;+mail %6=MudNet Mail: %7;-From %4%(%3%)@%5%r%r%8%r%r** reply using `mnmail'. See `mnhelp' for help. **;+send;@wait 2=@pemit/silent me=%vkRENDrequest|%0 |
Now, go back and recheck that you've
done everything correctly, please, just in case. After that, assuming
you've read and agreed to the policy,
continue on to the form to send us
your information.
|