[Encore] My Multi-Room works in Xpress now!

[Kevin Jepson]

Good Evening Folks
 
I hope you didn't overdose on all the chocolate. :-)
 
I have finally succeeded in integrating the Multi-Room object I use at my
MOO into enCore V4, it will probably work in V3 also but will NOT work in
V5.
 
An @dump of this object is available at the Barn.
HYPERLINK
"http://www.encore-consortium.org/Barn/news.html"http://www.encore-consortiu
m.org/Barn/news.html
 
This object mimics the normal room/exit system with an in-object database.
This means that within a single object there can be several rooms with their
own exits and descriptions.
 
It has many interesting capabilities, such as details, which are described
in the help file which I've copied below.
 
I use this object for vehicles, specifically ships, airships and submarines.
Being a single object they are easily moved inside the object hierarchy when
the ship sails or the airship flys.
 
By creating a custom _html verb I was able to integrate it into the WEB
display of the Xpress client.
 
I hope you find it useful.
 
There are a couple of changes to the detail display that should be done to
make it more useful but I leave that as an exercise for other builders. :-)

 
Ciao
KJ
 
=======================================================
Kevin Jepson R.E.T.
President
4K Consulting Inc.                    
An't nanum hearm deth, doth hwaet ye willath.

PHONE: (403) 875-8372
Email: kevijeps at telusplanet.net
=======================================================
 
====================================
Help File for Generic_Multiroom :
----
The mandate of #37796, a previous generic multiroom, was to expand on the
concept of details, this roomtype is what is called a metaroom, one object
that has been programmed to simulate the $room and $exit system.
 
There are other multirooms, this one features interactivity between
simulated rooms and a convenient environment for building.  If you wanted to
give this room one of those loaded generic names it might go something like
"Generic Secure Seated Detailed Exterior Integrating Metaroom with
Megafeatures". 8+)
 
Features:
 
    * Notion of being able to see what is ahead of you in another location
in straight lines and 'hear' what is going on in the locations around you.
This is accomplished by a concept of transparent and sound permeable exits.
There is a maximum range of 5 rooms in a straight line for sight and a
radius of 3 rooms around your present location for sound.
 
 * Exits that can be doors and that have locking. You can set special flags
on each exit to tell the multiroom that it is a door and you have the
spectrum of $exit messages to set as well. Exits are integrating via
look_msg. 
 
 * Support for linking with other room types using exits from any location
within the multiroom.  With the addition of properties like look_msg and
transparency you can make a seamless transition from the multiroom to other
roomtypes.
 
 * Details: Every sub-room in the multiroom can have it's own details. These
details are shown when you look at something in the room that matches the
detail name.
 
 * Seats: Details can be seats, allowing you to sit down or lie on top of a
detail, with the appropriate room description and announced messages.
Looking at a detail that is a seat will also display who is sitting/lying on
that seat. In addition, the format of the original command line is preserved
for message display; You type lie on bed and it will say you are lying on
the bed, say lie in bed it will say you are lying in the bed. "a", "an",
"the" are checked for and supplied for you.
 
 * Surfaces: Any detail that you can sit/lie apon is considered a surface
and you may place objects on that surface. Any object associated with a
surface will be hidden from view unless the object is "on" the surface as
opposed to behind it or under it. For example if you 'put a key under a
welcome mat' then the key will be invisible unless you 'look under the
welcome mat', 'look at welcome mat' will just show the mat's description.
 
 * Virtual containers: a detail may also be a container. If the detail is
specified as not being sittable or something you can lie on and there is
only one of them then you will be asked if you can open and close it, this
means the detail will be a container. You can get/put things from detail
containers, open and close them. If a container is open then it's contents
are integrated into the room description. And more...
 
 * Security: A simple global security is available for those who wish it.
 
 * Integration: any object within the multirom with a look_msg property will
be integrated into the room description of its location.
 
 * Exterior Room: You can enter and exit this room. You can have an exterior
description and title as well as custom messages for entering and exiting.
The concept of transparency has been used here as well.
 
 I feel that my version of a metaroom is fairly robust and stable and that
just about all of the bugs have been worked out. It is still subject to
fine-tuning and enhancements however as the suggestions from users come in.
There are several outstanding incompatibities in the design of metarooms in
general with regard to non-room verbs, hopefully someone will come up with a
good solution to them. 
 
 Enjoy!
 
 Tarod (1993)
 
Technical info on the internal DB structure etc is avialable through the
command @about this. 


  
 

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.446 / Virus Database: 269.0.0/752 - Release Date: 08/04/2007
8:34 PM
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: /pipermail/encore_encore-consortium.org/attachments/20070409/5b0e6ff0/attachment.html