CUSTOMIZING CLUSTERS AND PLACES
There is an option to allow you to specify the color that tabletalk (tt) appears as, allowing specification for personal preferences and terminal restrictions.
&TTCOLOR1 me=<ansi code>
&TTCOLOR2 me=<ansi code>
TTCOLOR1 controls the color of the tabletalk at your table.
TTCOLOR2 controls the color of a tabletalk that you are spying on.
For example, setting '&TTCOLOR1 me=hr' will set it to highlighted red. Setting '&TTCOLOR1 me=n' will set it normal. If you do not set these, TTCOLOR1's default is 'h' (i.e. highlight) and TTCOLOR2's default is highlight black (i.e. grey).
See 'help ansi codes' for a list of ansi codes.
INSTALLING CLUSTERS AND PLACES
The code for configuring clusters and places is not yet completed. However, you can configure clusters and places manually for a room you own. As an instructive example, if you want to create a place 1 which would be a couch, then input the following:
&CFG.PLACE.1 here=name~A couch|desc~A nice leather couch.|max~4|num~4|fixed~That's just silly|join~sits down at the couch.|depart~stands up from the couch.|cjoin~moves to stand near the couch.|cdepart~You move away from the couch.|prefix~At the couch|cprefix~Near the couch
You can add additional places and customize them by changing the data after each ~ as appropriate. And a second would be created with '&CFG.PLACE.2 here=<customized data>' and so on.
If you are installing places in a room, remember to @set here=!halt. Otherwise people who use your spaces will leave 'ghosts'.
If a room has a lot of IC background noise, please do: @set here=TERSE.
OLD
Places code can be used to distinguish sub-areas or tables within a larger space. Examples might be different exhibit areas inside a museum gallery, or different tables inside a restaurant. Some people may use this to delineate space in their private rooms as well, such as distinguishing a bathroom from a living room from a kitchen.
The existence of places (and +views) will be displayed just after the description of the room.
This document will not go into what you can do with a place. It assumes that you know. If you don’t have a look at: +help ic/places, +help ic/places options, +help ic/mutter.
This document will go into how you make and set your places so that they have all the several values, descriptions and emits that they need to use all the commands related to the places-code.
14.1 Creating Places
First you need to decide how many places you would like to have in your room. Then you make sure that you are in the room that you want to create the places in and type:
Configure <number or places that you want> places
When you made a mistake and you want to have more places you can repeat this command and insert the total number of places that you want.
When you want to erase all your places you can type:
Unconfigure places
For the Exotic Garden in my ‘Little Shop of Horrors’ I want to have a ‘Veranda’ an ‘Iron Bench’ which is a total of 2 places, so I make sure that I am in my exotic garden and I type:
Configure 2 places
14.2 Place Settings
For more information see: +help ic/places, +help ic/places config, +help ic/mutter.
When you created your places, your places will have default settings as noted in the table below. You can adjust these settings to make these places into what you want them to be. The command that you use for this is the following:
Update <Place #>/<Option>=<Configuration Text>
The several ‘options’ that you have and an indication of what the configuration text could be are indicated in the table below. You should set all of these options for all of your places separately.
Option Description <Option> Default Configuration Text
Place Name NAME Table x
Place description DESC <NULL>
Maximum # of places MAXPLACES Random
Current # of places CURPLACES Random (1 >= # >= MAXPLACES)
Fixed fail message FIXED <NULL>
Full fail message FULL That table has no more room.
Join message JOIN You sit down at <place>.
Ojoin message OJOIN sits down at <place>.
Depart message DEPART You stand and leave <place>.
Odepart message ODEPART stands and leaves <place>.
Say prefix PREFIX At your table
Let’s to through the different options one by one:
14.2.1 Place Name
This is how your place is called.
Update <Place #>/place name=<Name of the Place>
Dummy_BLDR wants her place 1 to be the Iron Bench. So she types:
Update 1/name=Iron Bench
14.2.2 Place Description
This is the description of your place. Make sure the description adheres the format as described in section 10.1.
Update <Place #>/desc=<Description of the Place>
Dummy_BLDR wants her Iron Bench to be rusty and in the centre of the garden.
Update 1/desc=%r %t A rusty bench of foundry iron stands in the midst of the exotic garden, in front of a small pond. A strange giant flower lunges over the bench, hovering over any that would sit there, like a falcon watching its prey. %r
14.2.3 Maximum number of Spaces in a Place
This defines the maximum number of people that your place can hold.
Update <Place #>/maxplaces=<maximum number of people that the place can hold>
Dummy_BLDR determines that her place is barely large enough to harbour 3 people.
Update 1/maxplaces=3
14.2.4 Current number of Spaces in a Place
This defines the number of places that is currently available. I mostly make this the same as maxplaces.
Update <Place #>/curplaces=<maximum number of people that the place can hold>
Dummy_BLDR types: .
Update 1/curplaces=3
14.2.5 Failure messages when trying to move a fixed place
This is the message that a player gets when he tries to move a place that is fixed. It’s not really done so much, so you can leave it on <NULL> most of the time.
Update <Place #>/fixed=NULL
Dummy_BLDR types either nothing (because she need not change the default setting, or:)
Update 1/fixed=NULL
14.2.6 Failure messages when trying to join a full place
This is the message that a player gets when he tries to join a place that is already full.
Update <Place #>/full=<failure message>
Dummy_BLDR types:
Update 1/full=There are no more seats available on the Iron Bench.
14.2.7 Joining message for the player
This is the message that you get when you join the place.
Update <Place #>/join=<joining message for the player that joins>
Note: this will message will automatically be followed up by the place-name, so the place name need not be inserted here.
Dummy_BLDR types:
Update 1/join=You take a seat on the
14.2.8 Joining message for the other players
This is the message that is omitted to other players when you join a place.
Update <Place #>/ojoin=<joining message for the other players>
Note: this will message will automatically be (1) preceded by the name of the character that joins the place, and (2) followed up by the place-name, so both need not be inserted here.
Dummy_BLDR types:
Update 1/ojoin=takes a seat on the
14.2.9 Departing message for the player
This is the message that you get when you depart the place.
Update <Place #>/depart=<departing message for the player that departs>
Note: this will message will automatically be followed up by the place-name, so the place name need not be inserted here.
Dummy_BLDR types:
Update 1/depart=You raise and leave the
14.2.10 Departing message the other players
This is the message that is omitted to other players when you leave a place.
Update <Place #>/odepart=<departing message for the other players>
Note: this will message will automatically be (1) preceded by the name of the character that departs the place, and (2) followed up by the place-name, so both need not be inserted here.
Dummy_BLDR types:
Update 1/odepart=raises and leaves the
14.2.11 Prefix when using table-talk (tt)
This is the prefix that is used when a player used the table-talk-command (tt).
Update <Place #>/prefix=<Prefix that is inserted when using table-talk>
Dummy_BLDR types:
Update 1/prefix=On the Iron Bench
Advise: In order to check if you set everything right (especially the ojoin and the odepart) you might want to invite another player (or your own pc) into the room in order to test them.
14.3 Noisy rooms vs. Auspexers
Rooms with too much background noise for Auspex to be used effectively should be @set here=TERSE. Unless this flag is set, it is possible for use of Auspex to eavesdrop on places.
14.4 Troubleshooting Ghosts
Sometimes weird things happen to get people 'stuck' at a place, even though they are disconnected or out of the room. This may even cause them to get messages they shouldn't when they reconnect.
If you are in a room with places and notice these 'ghosts' please type the following command:
+placescleanup
This should hopefully fix things. If that fails, +feedback/bug (see '+help ooc/feedback').
