mirror of
https://github.com/opsxcq/mirror-textfiles.com.git
synced 2025-08-31 03:29:53 +02:00
266 lines
9.0 KiB
Plaintext
266 lines
9.0 KiB
Plaintext
From sk4p+@andrew.cmu.edu Wed Aug 10 20:17:23 1994
|
|
Received: from nova.unix.portal.com (nova.unix.portal.com [156.151.1.101]) by jobe.shell.portal.com (8.6.4/8.6.4) with ESMTP id UAA16465 for <Tyagi@houseofkaos.abyss.com>; Wed, 10 Aug 1994 20:17:22 -0700
|
|
Received: from po3.andrew.cmu.edu (PO3.ANDREW.CMU.EDU [128.2.10.103]) by nova.unix.portal.com (8.6.7/8.6.4) with ESMTP id UAA03600 for <Tyagi@houseofkaos.abyss.com>; Wed, 10 Aug 1994 20:17:21 -0700
|
|
Received: (from postman@localhost) by po3.andrew.cmu.edu (8.6.7/8.6.6) id XAA09772 for Tyagi@houseofkaos.abyss.com; Wed, 10 Aug 1994 23:17:19 -0400
|
|
Received: via switchmail; Wed, 10 Aug 1994 23:17:18 -0400 (EDT)
|
|
Received: from ccon-weh.weh.andrew.cmu.edu via qmail
|
|
ID </afs/andrew.cmu.edu/service/mailqs/q002/QF.ciGNUqa00bkU40OEFk>;
|
|
Wed, 10 Aug 1994 23:17:11 -0400 (EDT)
|
|
Received: from ccon-weh.weh.andrew.cmu.edu via qmail
|
|
ID </afs/andrew.cmu.edu/usr23/sk4p/.Outgoing/QF.4iGNUpi00bkU45mMw4>;
|
|
Wed, 10 Aug 1994 23:17:09 -0400 (EDT)
|
|
Received: from BatMail.robin.v2.14.CUILIB.3.45.SNAP.NOT.LINKED.ccon.weh.weh.andrew.cmu.edu.sun4m.412
|
|
via MS.5.6.ccon-weh.weh.andrew.cmu.edu.sun4c_411;
|
|
Wed, 10 Aug 1994 23:17:09 -0400 (EDT)
|
|
Message-ID: <EiGNUpe00bkU45mMoq@andrew.cmu.edu>
|
|
Date: Wed, 10 Aug 1994 23:17:09 -0400 (EDT)
|
|
From: Shawn Clayton Knight <knightster+@CMU.EDU>
|
|
To: Tyagi <Tyagi@houseofkaos.abyss.com>
|
|
Subject: news file
|
|
Status: OR
|
|
|
|
Divination Web News
|
|
================================================================
|
|
Updated 9 August 1994
|
|
|
|
We are now running Foxen's MUFPage 2.40 with page #mail and
|
|
lots of other features! Type 'page #help' for info.
|
|
----------------------------------------------------------------
|
|
News Subtopics
|
|
|
|
BldgPolicy Building Management
|
|
================================================================
|
|
~~~
|
|
index
|
|
The following news topics are available. Type 'news <topic>' where
|
|
<topic> is one of the list below to view the news.
|
|
|
|
BldgPolicy
|
|
Building
|
|
Management
|
|
~~~
|
|
Building
|
|
Building Guide
|
|
|
|
All of the following can be referenced by 'help <topic>'.
|
|
|
|
|
|
Reference
|
|
|
|
ex (examine) - used to peruse construction in detail
|
|
l (look) - to see desc fields on objects
|
|
@owned - used to view a list of owned objects
|
|
@quota - obtain a breakdown of current project quota status
|
|
|
|
Construction
|
|
|
|
@dig - make a room
|
|
@open - make an exit
|
|
@link - connect one object to another
|
|
(thing/player + room => set home; exit + room => destination)
|
|
|
|
For more, see 'news Building2'.
|
|
|
|
~~~
|
|
Building2
|
|
Textfields
|
|
|
|
edit <obj> = <field>;/<oldtxt>/<newtxt>
|
|
changes the text of a field
|
|
|
|
detail <obj>:<tag> [;tag2;tag3;...] = <textstring>
|
|
adds tags to an object which may be seen with look
|
|
|
|
@desc (@describe) - what is seen by look
|
|
@succ (@success) - what occurs to a character when obj is used
|
|
@osucc (@osuccess) - what is seen by others when an obj is used
|
|
@fail - what happens to a character when failing to use an obj
|
|
@ofail - what is seen by others when a character fails to use an obj
|
|
@drop - what a player sees when an obj is drop'd
|
|
@odrop - what is seen by others when an obj is drop'd
|
|
@name - sets the name of an obj
|
|
|
|
For more, see 'news Building3'.
|
|
|
|
~~~
|
|
Building3
|
|
Miscellaneous Commands
|
|
|
|
@lock - keeps access to obj limited to a designated key
|
|
|
|
@project - designate or identify the current construction project
|
|
|
|
<bogus> - an exit @lock'd with fail and ofail fields designed to
|
|
simulate an activity/action
|
|
|
|
For more, see 'news Building4'.
|
|
|
|
~~~
|
|
Building4
|
|
Objects of Import
|
|
|
|
me - the builder
|
|
here - the room in which the builder stands
|
|
number (#) - the identifying number (PID) of any obj
|
|
|
|
|
|
Other Topics
|
|
|
|
Communication - various commands for talking
|
|
Transportation - various commands for moving about
|
|
Purpose - description of why DWII is here
|
|
Networking - ideas for how to make connections
|
|
|
|
~~~
|
|
bpolicy|bldgpolicy
|
|
Divination Web Building Policy
|
|
|
|
0.0 Introduction
|
|
|
|
In order to maintain the quality and focus of Divination Web, a policy
|
|
for Builder-bit (B-bit) dispensation and project construction has been
|
|
instituted. This includes specific quotas and processes of proposal
|
|
and review.
|
|
|
|
|
|
1.0 Quotas
|
|
So as to minimize impact upon the DWII database and preserve prompt
|
|
response-time, a quota system has been installed with the following
|
|
limitations:
|
|
|
|
General Players: 0 objects
|
|
Muckers and Builders without a project: 5 objects
|
|
Default builders with projects: 150 objects
|
|
|
|
'Coins', the currency whereby building may proceed, are effectively
|
|
useless and we may find some way of allowing people to increase their
|
|
own cache.
|
|
|
|
Type 'news bpolicy2' for more.
|
|
~~~
|
|
bpolicy2
|
|
1.1 Quota Increase Request
|
|
If a Builder desires a greater quota, they can contact a B-manager
|
|
familiar with their project. At that time they should provide an
|
|
explanation for their request. Generally the 150 object maximum
|
|
will remain firm except under unusual circumstances.
|
|
|
|
|
|
2.0 Proposal Process (Getting B-bits)
|
|
In order to be able to build on DivWeb one must first procure a B-bit,
|
|
and these are dispensed by the B-managers:
|
|
|
|
Hsi.Wang.Mu (tyagi@houseofkaos.abyss.com)
|
|
Shawn (knightster+@cmu.edu)
|
|
|
|
Email a proposal to one of the B-managers and await a response.
|
|
|
|
Type 'news bpolicy3' for more.
|
|
~~~
|
|
bpolicy3
|
|
2.1 Proposal Contents
|
|
This Muck has very specific goals and purposes which include
|
|
networking and experimentation within the subject fields of occultism
|
|
and spirituality. In order to serve these, a loose restraint has been
|
|
placed upon building projects.
|
|
|
|
In general, a proposal should contain thematic orientation and at
|
|
least a vague concept of structure. Estimates on the number of
|
|
objects to be used and a building schedule are also valuable.
|
|
Ultimately it is up to the B-managers whether or not they wish to
|
|
sponsor a proposed project, for to do so indicates their assumed
|
|
responsibility for the review and expedition.
|
|
|
|
2.3 Proposal Review
|
|
Each proposal will be reviewed by B-managers and should any of them
|
|
desire to sponsor the project, they will coordinate with the new
|
|
Builder on a quota and review schedule.
|
|
|
|
Should such sponsorship not be forthcoming, then suggestions for
|
|
revision or a request for additional information will be returned.
|
|
|
|
Type 'news bpolicy4' for more.
|
|
~~~
|
|
bpolicy4
|
|
3.0 Review Process
|
|
In order to facilitate efficient use of database resources and to
|
|
preserve the enjoyment of players, periodic reviews will be scheduled
|
|
on all building projects currently underway.
|
|
|
|
3.1 General Review Guideline
|
|
The following is intended as a guideline rather than a strict
|
|
standard, and a review schedule may be conducted differently by a
|
|
B-manager based on specific project complexity and/or character.
|
|
|
|
3.2 Suggested Timing
|
|
Suggested Initial Review: 2 weeks
|
|
Periodic Update Reviews: every 2 months
|
|
|
|
3.3 Review Criteria
|
|
B-managers will be looking at internal consistency (where
|
|
appropriate), in comparison with the projected construction schedule.
|
|
|
|
Type 'news bpolicy5' for more.
|
|
~~~~
|
|
bpolicy5
|
|
It is suggested that projects be broken into sectors, with regular
|
|
completion of a specified sector prior to each review. The size of
|
|
each sector is left to the discretion of the Builder to be based upon
|
|
available time and expertise.
|
|
|
|
3.4 Review Results
|
|
A B-manager sponsor or another B-manager who is familiar with the
|
|
proposal, quota and schedule for the project will review the whole
|
|
with careful scrutiny of any sector designated as 'completed'.
|
|
Results from this review will be sent to the Builder and to other
|
|
interested B-managers.
|
|
|
|
Exits to reviewed and completed sectors will be made visible to the
|
|
public. In this way the projects will emerge gradually and the
|
|
review process will be kept to a minimum of effort.
|
|
|
|
Type 'news bpolicy6' for more.
|
|
~~~
|
|
bpolicy6
|
|
3.5 Corrections
|
|
If there are problems within a sector which was planned to have been
|
|
'completed', then the Builder and their sponsor B-manager can work
|
|
together to resolve these problems and get the sector open to the
|
|
public. An acceptable means of dealing with these problems would
|
|
be to revise the time-schedule and set a new review date.
|
|
|
|
3.6 Warnings
|
|
Given severe delays and the lack of logging in (e.g. 180+ days),
|
|
Builders may receive a warning that their project and properties
|
|
are to be recycled unless management is contacted within one
|
|
week. If no such communication is received within that week,
|
|
then their unfinished project is subject to recycling by the
|
|
management.
|
|
~~~
|
|
management
|
|
Divination Web is operated and managed by:
|
|
|
|
Caledhaearn (hoffman@curly.red-cross.org)
|
|
- Responsible for managing Mucker bits and projects.
|
|
|
|
Hsi.Wang.Mu (tyagi@houseofkaos.abyss.com)
|
|
- Responsible for managing Builder bits and projects.
|
|
|
|
Shawn (knightster+@cmu.edu)
|
|
- Responsible for maintaining the MUCK server.
|
|
|
|
All managers are able to assist the others with their work, so if you
|
|
can't find the manager you're looking for, contact the others.
|
|
~~~
|
|
|
|
|
|
|
|
|
|
|
|
Shawn C. Knight/knightster+@cmu.edu |"Magus Perde, take your hand from off the
|
|
Box 4498, 5115 Margaret Morrison St.|chain; loose a wish to still the rain,
|
|
Pittsburgh, PA 15213 (412) 862-2232 |the storm about to be ..." - Jethro Tull
|
|
|
|
|
|
|