Difference between revisions of "Build Guide"

From From The Ashes Wiki
Jump to: navigation, search
(Created page with "= Putting in a Build Request = So you want to build something? Oh, fun times. Here are a few things you should put in your '''+req/build''' request: Image:Edmonton_Blocky_t...")
 
(→‎STEP 4: The Next Room)
 
(21 intermediate revisions by 3 users not shown)
Line 1: Line 1:
−
= Putting in a Build Request =  
+
= Submitting a Build Request =  
−
So you want to build something? Oh, fun times. Here are a few things you should put in your '''+req/build''' request:
+
The purpose of this guide is to familiarize you, the player, with building information that you will need to set up a home or business on From the Ashes: Detroit by Night. Here are a few things you should put in your '''+request/build''':
−
[[Image:Edmonton_Blocky_the_Build_Guide_Builder.gif|left]]
 
−
 
 
−
* The name of your build, like 'Log Cabin' or 'Secluded Home'.
 
−
* How many rooms you'll be needing. Remember, the number of rooms you can have is determined by your [[Mush news:Build mundane|resource level]].
 
−
* How the rooms link to each other.
 
−
* What area on the [[Maps|+map]] you want to be linked. Not sure where you should go? Check [[Residences|residences]] for a list of possible apartments/areas that might suit organized by Resource level.
 
−
** Please note: If you are in a sphere where territories matter, make sure you're not building in anyone's claimed territory without their permission to live/own a shop/whatever there.
 
−
** Please also note: If you want a room in family build because you are part of that family, please get permission and make sure we know you have permission by including whoever owns the build on the +job and having them comment that they are OK with you having that room made and linked there.
 
  
 +
* The name of your build.
 +
* How many rooms you will be needing. The number of rooms you can have is determined by your [[Mush news:Build mundane|resource level]].
 +
* What area on the [[Maps|+map]] you want to be linked. Take a look at the grid for ideas and to get a feel for the style of the district you wish to build your project in. Check [[Residences|residences]] for a list of possible apartments that might suit your needs and Resource level. Some of these are already furnished with descs that can be customized, while others will require you to build a room in its entirety.
 +
**Please be advised that if your build does not suit the location or your Resources, you may be asked to modify your project.
  
 
Example:  
 
Example:  
−
:''+req/build Secluded Cottage=I would like to make a three room Secluded Cottage linked to ES02. I'd like a garden, a living room, and a workshop. The first room would be the garden; it would link to the living room and the workshop.''
+
:''+request/build Bazooka Lounge=I would like to make a two roomed club linked to #11.
−
 
 
−
 
 
−
Please also take a look in the Old Builds section of the nexus for anything you can adapt that might suit your needs instead of of a new build.
 
−
 
 
−
= Standards =
 
−
Because we like the grid to look uniform, buildstaff insists on the following:
 
−
* Room desc format. Room descs must begin with %r%t, have %r%r%t between paragraphs, and end with %r.
 
−
* Exit descs. No special format, but every exit needs to have an @desc, even if it's hidden or transparent. Every single one!
 
−
* @osuccs. Only two kinds of exits need these; an exit leaving the grid and going into a build and an exit leaving a build and going back to the grid. Just those exits.
 
−
 
 
−
== Take Pity On Us ==
 
−
* SPELLCHECK. We will know if you don't bother. You can find lots of spell check whatsits online - for example, [http://www.spellcheck.net/ spellcheck.net].
 
−
** Seriously, we will know if you don't bother with this. Nothing makes build staff burn out faster than having to correct a bunch of spelling and sentence structure.
 
−
* Proofreading: also good.
 
−
* ''If you have difficulty writing, please, please, ''please'' ask a friend to proofread your @descs before submitting for inspection.'' It is okay to not be a perfect writer. We will help you as best we can! Help us help you.
 
−
 
 
−
 
 
−
= Rooms =
 
−
Your basic building blocks of build projects. Rooms can represent a tiny space like a closet or something huge like an entire +map coordinate, spanning multiple properties and swaths of land. You're more dealing with the closets, apartments, and back yards of the world with your +build requests.
 
  
−
== @descs ==
 
−
Room descs need to be formatted in a particular way. We like things to look uniform and be easy to read. To that end, room descriptions need to begin with '''%r%t''', have '''%r%r%t''' between paragraphs, and have '''%r''' at the end. In practice:
 
  
−
<blockquote>@desc here=%r%t277 Bay Street is a two-story white house complete with a columned porch, pedimented gable, and bold, simple mouldings. It's not gigantic but it would be out of place in the depths of suburbia. The property around the house is circled by an iron fence and contains a multitude of trees, providing the home with a fair amount of privacy. %r%r%tThe interior decor is very coordinated, as though the owner just picked up a catalogue and bought everything in the pictures. The result is weird. At least it was a upper-end catalogue. There are no personal photos. Other rooms include a master bedroom with en suite bathroom, one and a half other bathrooms, a couple of spare rooms, a kitchen-slash-dining area, and a study with seriously high-performance computers, some of which are in various states of assembly. The study looks like the most lived-in room in the house, as though a person actually spends a lot of time there, while the rest of the house could be a model home. %r </blockquote>
+
There are some existing businesses available on the grid for PC ownership. If your concept fits one of these, do an 'ex' on the exit. If it's owned by "The D" that means it's open for new management and could be yours if you wanted it to be! Residences, shops, and other building ideas are welcome here and there are existing buildings where shops, cafes and other boutiques can be linked, such as the Guardian Building, and the Fisher Building. Check [[Businesses|businesses]] for currently available enterprises.
  
−
== +views ==
+
= Formatting =
−
So much detail to give, so few lines of text to give it. Well, not really - the lines of text are actually unlimited, but if you want people to actually read a desc, three solid paragraphs is about the maximum. If it scrolls off a screen, forget it. +Views are great for including details without spamming someone every time they walk into a room or type 'l'. They're like opt-in bits of descing; you've told them the basics, so they can choose to read more. While you ''can'' devote a paragraph in a room desc to a lovely painting of a gentleman standing with a dog, chances are people aren't going to want to know all that much about it unless it's important to them. Mention there are paintings on the wall, slap on a +view called 'Painting' and describe that man's outfit and the dog's stance to your heart's content. In practice:
+
Because we like the grid to have a certain amount of uniformity, BuildStaff insists on the following:
 +
* Room desc format. Room descs must begin with %r[space(7)], have %r%r[space(7)] between paragraphs, and end with %r.
 +
* Exit descs. The above applies to Exits, too. Every exit needs to have an @desc, even if it's hidden or transparent.
 +
* @osuccs. All exits in a building project will require exit emits. This will be detailed later on.
 +
* @parent. Here at From the Ashes: Detroit by Night, we use only one parent for all rooms. @parent here=#6 This parent automatically formats the headers and footers for your room, as well as the exit format, which will automatically use the first letter of the first word as the Exit name, unless you specify otherwise (which you should). You do not need to add <> to anything.  
 +
* Spellchecking can be overlooked. You don't need to be a perfect writer to play here, but we have provided a resource to use should you desire it. You can find lots of spell checkers online - for example, [http://www.spellcheck.net/ spellcheck.net].
  
−
<blockquote>+view here/Painting=Gentleman With Dog is a 17th century painting by artist Pierre Doucette rendered in oils. It depicts Bartholomew Cunningham with his Scottish terrier Stuart. Bart, dressed in his finest blue attire, stands gallantly with one knee braced on the rail of a mighty ship, Stu tucked under his arm like a furry football. The ship is The Paragon, Bartholomew's third ship and the one he owned for the least amount of time; it, and Stuart, are at the bottom of the Atlantic, having been sank by an ill-advised shot fired in anger during a dice game three weeks into The Paragon's maiden voyage. </blockquote>
+
= STEP 1: Renaming your exit =
 +
Once your building request has been approved, you will be granted a starting room in the Building Nexus. The starting room is the very first room of your building project. Your Exit will be named something like: 'Will's Starterroom <WIL>'. The first thing you will need to do is consider what you are building. An Apartment? A House? A business? A business will need to be given the name of the business. An apartment, an apartment number. A house will require a house number and street name.  
  
 +
*For a business:
 +
**@name WIL = Bazooka Lounge;bl;bazooka
 +
*Or for an apartment:
 +
**@name WIL = 104;104
 +
*Or for a house:
 +
**@name WIL = 1313 Mocking Bird Lane;1313
  
−
== @names ==
+
= STEP 2: Rename Your Room, @parent and Descing =
−
This @name is bad and you should feel bad! Sometimes you decide you want a garden more than you wanted a basement. That's okay, it happens. It also happens that buildstaff typos or gets something wrong. But, happy day, You can change the @name of your room if necessary.
 
  
−
Take your basement/garden issue. Say the basement room is named ''Basement - Hudson House''. You want it to be a garden. To change it, you'd type (while standing in the room):
+
You need to rename your starter room. Go inside the room.
  
 +
*@name here = The Bazooka Lounge - Vestibule
  
−
:@name here=Garden - Hudson House
+
Rooms should begin with the name of the apartment, business or house name, then the name of the specific room. Foyer. Lounge. Living Room. And so on and so forth.
  
 +
Next, you need to @parent your room as described in the Formatting section above. @parent here=#6
  
−
Ta-da. A garden instead of a basement. It's important to keep that 'Hudson House' part in there because it helps differentiate builds; imagine how many Living Rooms are out there.
+
Now you are ready to begin descing your room and exits. Writing @descs is a creative process. It allows you to visually imagine a location, and fill in the details of the location with your words. @descs should be detailed and as descriptive as you like, though any exit that links to a street or outdoor location should receive a bit of extra attention. This exit tells people what the exterior facade of your store front or house looks like to anyone passing by and gives flavor to the location. All descs require a certain format be maintained as outlined above in the Formatting section.
  
 +
*@desc here=%r[space(7)]This is my desc. Isn't it nice?%r
  
−
= Exits =
+
Or to desc an exit:
−
Your exit can be a tricky customer. It helps if you think of an exit on a game as one side of a door. They usually come in pairs. Every IN has an OUT, and while they're two different exits on the game, they're paired together as a single entity, be it a door or a hole in the wall or a thin curtain. Exits have a few options to set on them; the only one (other than the @desc) we make you set on The Reach is the '''@osucc''', and that's only on exactly two exits in your build, as covered earlier.
 
  
 +
*@desc o=%r[space(7)]This is what the door looks like.%r
  
−
== @osuccs ==
+
= STEP 3: Exits =
−
The osucc message is the message people in the same room as you see when you successfully go through an exit. They see it ''on'' your ''success'' - ''osucc''. We have you set this on the first entrance/exit on your build so people will know where you went when you, say, go into a house from the street. When you set an exit's osucc message, you're setting the message ''people in the same room as you'' who ''don't go through the exit'' see when you go through it. For example:
+
Now that you have @desc'd your room, your exits, what's next? Exit @succ's. These are the messages you receive when you move between exits. There are 5 of them that you need. They are:
 +
*@succ
 +
*@osucc
 +
*@odrop
 +
*@fail
 +
*@ofail
  
 +
The specific information on each can be accessed by typing help @succ, replacing @succ with whichever you're curious about. Specifically, this is what each does.
  
−
:@osucc OH=goes into a moldy old house.
+
@succ - Sets the message that is shown to someone who successfully passes through the exit.
  
 +
@osucc - Sets the message that is shown to others whenever someone successfully passes through the exit (in the room where the exit is).
  
−
Mary, Tim, and Greg are standing out on the street. Mary goes through the Old House <OH> exit. Tim and Greg see 'Mary goes into a moldy old house' because they're still out on the street.
+
@odrop - Sets the message that will be shown to others on the OTHER side of the exit you pass through (in the room where the exit goes).
  
 +
@fail - Sets the message that is shown to someone who fails to pass through the exit.
  
−
== @descs ==
+
@ofail - Sets the message that is shown to others whenever someone fails to pass through the exit (in the room where the exit is).
−
Fortunately, exits are easy to put descriptions on. Just @desc the exit name. For example:
 
  
 +
These are the basic requirements of an exit. Examples are as follows:
 +
*@succ o=You walk out the door.
 +
*@osucc o=walks out the door.
 +
*@odrop o=walks out of Apartment 202.
 +
*@fail o=The door appears to be locked.
 +
*@ofail o=tries to walk out the door, but it appears to be locked.
  
−
:@desc out=A wooden door leading to the shop's abattoir.
+
= STEP 4: The Next Room =
−
:@desc bedroom=A curtain of purple beads separates the bedroom from the living room.
+
Now that you have finished with your starter room, it is time to make the next one (if there is a next one).
−
:@desc qf=Quality Foods is an unassuming two-story brick building. The grocery store is open twenty-four hours a day and does brisk business.
 
  
 +
Start in your existing room. There you will need to use the @dig command.
  
−
== @names ==
+
* @dig Kitchen = Kitchen;k;kitchen,Out;o;out
−
Slightly more complicated than room @names or character @names, exit names also contain all the words you type that get you into a room. For example, the very common Out <O> @name is often:
 
  
 +
This command creates the new room, an exit into that room, and an exit back out of that room to your starter room.
  
−
:@name out=Out;o;back;exit;leave
+
Make sure you follow all preceding steps on each new room. And that's it! You are done!
−
 
 
−
 
 
−
We want to be able to let people wander around intuitively if possible, which is why there are so many words that mean 'go outside' on that out exit. The semi-colons are important in the exit @names. Here are some other examples of exit @names:
 
−
 
 
−
 
 
−
:@name st=Study;st
 
−
:@name st=Stairs;st;up;upstairs
 
−
:@name st=Stairs;up;upstairs;stairs;study;st
 
−
:@name ws=Workshop;ws;work;work shop;shop;down
 
−
:@name wdw=Winding Driveway;wdw;winding;driveway;drive;winding drive
 
−
 
 
−
 
 
−
The code will put the first set of characters after the semi-colon in brackets next to the exit name, so @name st=Study;st will get set as Study <ST>.
 
−
 
 
−
= Where Is My Stuff? =
 
−
We all lose track of things.
 
−
 
 
−
== @search ==
 
−
Sometimes you forget where you put things, like a closet or your horse ranch. That's okay, you can find things you own easily by typing ''@search''. That's it, ''@search''. That pulls up a whole list of things you own - rooms and exits, for example, and in the case of exits, how they relate to rooms. For example:
 
−
 
 
−
 
 
−
:@search
 
−
 
 
−
 
 
−
:ROOMS:
 
−
:Apartment N202 - Aleswich Arms(#7326RA)
 
−
 
 
−
:EXITS:
 
−
:Apartment;202;apt 202;apartment 202(#7655E) [from Aleswich Arms - North Wing - Second Floor to Apartment N202 - Aleswich Arms(#7326RA)]
 
−
:Out;o;back;exit;leave;hall;hallway;corridor;corr(#7809E) [from Apartment N202 - Aleswich Arms(#7326RA) to Aleswich Arms - North Wing - Second Floor]
 
−
 
 
−
 
 
−
== #dbrefs ==
 
−
What is an #dbref? It's short for 'database reference'. Everything, everything, everything on the game has a #dbref - the channels you talk on, the rooms you use. A #dbref number can stand in for an @name. While there are many apartments in the game, yours is the only apartment with the dbref #7326. If you're the person in the above example, anyway.
 
−
 
 
−
 
 
−
Who cares? It's useful to know if, say, you misname an exit in a manner that makes it difficult to rename using words - like having two exits using 'BR' in the same room. Which can and does happen. You can sub in #dbrefs when necessary, like so:
 
−
 
 
−
 
 
−
:@name #7984=Out;o;back;exit;leave
 
−
 
 
−
 
 
−
It comes in handy sometimes.
 
  
 +
Before you resubmit your project for inspection and approval to be linked via '''+request/build''', please make sure you have not overlooked anything. The following are often missed:
  
 +
* Ensure all descs start with %r[space(7)] and end with a %r
 +
* Ensure your exits have descs. Every exit needs an @desc
 +
* Don't forget to rename the exit INTO your starterroom. See Step 1 for how to do that.
 +
* Don't forget to @parent your room.
 +
* @odrop on every exit. It is often overlooked.
 +
* +inspect here can be used to view all the existing parts of a room in order to ensure they've all be set.
  
 
= Places =
 
= Places =
−
Place code is immensely useful for large scenes. It provides a way to filter messages that helps you concentrate on just the people near your character while still being able to watch everyone else. Any public builds, ones where PCs are encouraged to loiter about and RP, are ''strongly encouraged'' to have place code set up. (''Strongly encouraged'' in this case means ''please for the love of whatever entity or non-entity you find most dear, please, please put in place code, we are begging you''.)
+
Places code is immensely useful for large scenes. It provides a way to filter messages that helps you concentrate on just the people near your character while still being able to watch everyone else. Any public builds, ones where PCs are encouraged to loiter about and RP, are encouraged to have places code set up.  
−
 
 
−
 
 
−
Place code is great when you have a great big house, too. Instead of building a kitchen, a sitting room, and a dining room off your living room, why not make those areas places in the living room? Why shouldn't the people in the living room be able to see people going into and coming out of the kitchen or maybe overhear them if they're talking loudly enough? Why bother descing entire rooms that are rarely used? Put in places. Please put in places.
 
−
 
 
−
 
 
−
The best thing about places, though? You don't have to wait on build staff. And while we obviously are volunteers out trying to help everyone, sometimes it's a lot faster to set up some quick and dirty place code rather than wait for us to get our reading glasses on and oh let me open my spell check and you're missing a %r there, I'll get back to you after I link these five apartments.
 
−
 
 
−
 
 
−
The +help files on the game and [[Mush_help:Places_2|on the wiki]] are useful, but we'll just walk through the basics here.
 
−
 
 
−
 
 
−
== Configuring Places ==
 
−
 
 
−
=== How many places do you want? ===
 
−
 
 
−
Is it a business establishment like a bar or a cafe? You'll want various booths, tables, stools, or other seats. The more the merrier. You can make some of them small, with maybe three or four people, maximum, but the rest should be considerably bigger.
 
−
 
 
−
 
 
−
Are you describing rooms on the main floor of a large house? Just as many as you think you'll use is good. You can have a kitchen, a parlour, and a dining room off your living room. You could have a few room places and a few regular seat places like couches.
 
−
 
 
−
 
 
−
The maximum number of places you can have in any location is 10.
 
−
 
 
−
 
 
−
Let's say I'm adding places to a cafe. I'd like to have a large counter for people to sit at, a couple of small, intimate places, some booths, and a big squishy couch. I'll configure 6 places.
 
−
 
 
−
 
 
−
:places/configure <location>/<number of places> 
 
−
:places/configure here/6
 
−
 
 
−
 
 
−
So, after typing places/configure here/6 and confirming that was in fact what we meant to do to, we now have places:
 
−
 
 
−
 
 
−
:A table (#1) has 5 empty places.
 
−
:A table (#2) has 5 empty places.
 
−
:A table (#3) has 5 empty places.
 
−
:A table (#4) has 5 empty places.
 
−
:A table (#5) has 5 empty places.
 
−
:A table (#6) has 5 empty places.
 
−
 
 
−
 
 
−
Tables are automatic. Tables are the default. We can still have our counter, booths, and big squishy couch. We'll just have to set some of those attributes.
 
−
 
 
−
=== How do you change a place's name or spaces? ===
 
−
 
 
−
All the other attributes will be set using '''places/set <location> <num>/<item>=<value>'''. There are a number of things we can set, but the main ones we're gonna use are:
 
−
 
 
−
 
 
−
:'''Name''': The name of the place, better if lower-case except for proper nouns. (Default: a table)
 
−
:'''Spaces''': The number of spaces at a place. If set to '0', there is no limit. (Default: 4)
 
−
:'''Description''': The description of the place. (Default: A table with a couple of chairs)   
 
−
:'''Say_Prefix''': What's added to the use of 'tt' or 'tto' at that place. A comma is automatically added. (Default: At your table)
 
−
 
 
−
 
 
−
:places/set 1/name=Counter
 
−
:places/set 2/name=Small Booth
 
−
:places/set 3/name=Small Table
 
−
:places/set 4/name=Booth
 
−
:places/set 5/name=Booth
 
−
:places/set 6/name=Big Squishy Couch
 
−
 
 
−
 
 
−
And now when we type 'places', we get this list:
 
−
 
 
−
 
 
−
:Counter (#1) has 5 empty places.
 
−
:Small Booth (#2) has 5 empty places.
 
−
:Small Table (#3) has 5 empty places.
 
−
:Booth (#4) has 5 empty places.
 
−
:Booth (#5) has 5 empty places.
 
−
:Big Squishy Couch (#6) has 5 empty places.
 
−
 
 
−
 
 
−
Let's work on the counter place, which is #1.
 
  
 +
Places code is also useful when you have a large house, too. Instead of building a kitchen, a sitting room, and a dining room off your living room, why not make those areas places in the living room? Why shouldn't the people in the living room be able to see people going into and coming out of the kitchen or maybe overhear them if they're talking loudly enough? Why bother descing entire rooms that are rarely used? Put them into places.
  
−
:places/set 1/spaces=12
+
For installation of places, please see the +help files on From the Ashes: Detroit by Night by typing '''+help places-config'''.
−
:places/set 1/description=A long brick counter with a smooth concrete top.
+
*  For additional configuration options, type '''+help places-options'''.
−
:places/set 1/say_prefix=At the counter
 
−
 
 
−
 
 
−
Now when we type 'places', 'Counter' looks like this:
 
−
 
 
−
 
 
−
:Counter (#1) has 12 empty places.
 
−
 
 
−
 
 
−
And if we type 'plook 1' to look at place 1, we see:
 
−
 
 
−
 
 
−
:A long brick counter with a smooth concrete top.
 
−
:This place has 12 empty places out of 12.
 
−
 
 
−
 
 
−
And if we sit at the counter and use the table talk command 'tt', everything we say will be prefixed by 'At the counter,' which is great.
 
−
 
 
−
 
 
−
Once you have the basics down, you can configure places pretty fast. Like:
 
−
 
 
−
 
 
−
:places/set 6/spaces=4
 
−
:places/set 6/description=A big, squishy orange couch.
 
−
:places/set 6/say_prefix=On the couch
 
−
 
 
−
 
 
−
...gives us a place called 'Big, Squishy Couch' with four spots to sit where everything we say to our place with tt will be prefaced with 'On the couch,'. That's cool. Maybe I want more space on the couch. Maybe I want infinite space on the couch. Then I'd type:
 
−
 
 
−
 
 
−
:places/set 6/spaces=0
 
−
 
 
−
 
 
−
and have
 
−
 
 
−
 
 
−
:Big Squishy Couch (#6) has no limit.
 
−
 
 
−
 
 
−
...which is more useful for, say, outdoor golf ranges than couches.
 
−
 
 
−
 
 
−
=== Adding another place ===
 
−
 
 
−
Mistakes happen. Sometimes you realize after the fact that you want your cafe to have a secret petting zoo. You don't have to start over. You can sneak that petting zoo on in as your seventh space.
 
−
 
 
−
 
 
−
:places/newplace <location>
 
−
:places/newsplace here
 
−
 
 
−
 
 
−
Boom, now there's another table in here. But it's so easy to make it a petting zoo. It's just so easy:
 
−
 
 
−
 
 
−
:places/set 7/name=Secret Petting Zoo
 
−
:places/set 7/spaces=0
 
−
:places/set 7/description=A cleverly hidden petting zoo.
 
−
:places/set 7/say_prefix=At the petting zoo
 
−
 
 
−
 
 
−
And there you go. Type 'places' and now you have a secret petting zoo with no limit.
 
−
 
 
−
 
 
−
WITH NO LIMIT.
 
−
 
 
−
 
 
−
 
 
−
== Unconfiguring Places ==
 
−
Yes, you can undo it.
 
−
 
 
−
 
 
−
:places/breakdown <location>
 
−
:places/breakdown here
 
−
 
 
−
 
 
−
...will wipe out all the places, while:
 
−
 
 
−
 
 
−
:places/delplace <location>=<placenum>   
 
−
:places/delplace here=7
 
−
 
 
−
 
 
−
...would just remove the seventh place, which in our example was the petting zoo. Health code violations, probably. If there is only one place set, you'll have to use the first command.
 
  
 
= Miscellaneous Commands =  
 
= Miscellaneous Commands =  
 
== Dark ==
 
== Dark ==
−
You can set exits DARK, which means only you will be able to see the exit. Anyone will be able to use the exit so long as they know what to type. This is hella useful for hidden doors to secret rooms. @set <exit>=DARK will do it.
+
Setting an exit DARK makes that exit invisible to the room. Anyone will be able to use the exit so long as they know what to type. Very useful for hidden doors to secret rooms. @set <exit>=dark
  
 
== Unfindable ==
 
== Unfindable ==
−
Maybe you have a Brony room in your build and you want to keep it a secret. You probably don't want people looking at +where and seeing Brony Room - Expensive Mansion on the list. No worries, you can set it unfindable! This is good for things like secret sphere hangouts, hidden clubs, and other things not involving magical friendship. Please remember that as the room's owner, you will always, always see your room in your +where list, even if it's unfindable. The command is @set <here>=UNFINDABLE.  
+
One room in your build may be set UNFINDABLE, if you have more than one. A safe room, for instance, or sanctum. Setting the room unfindable removes it from the +where list. @set <here>=undfindable.
 +
 
 +
== Transparent ==
 +
Setting an exit TRANSPARENT allows you to see the next room beyond the exit. Helpful if the door is made of glass, for instance, or is simply an open archway. @set <exit>=transparent
  
 
== Abode ==
 
== Abode ==
−
Sometimes people crash at your place, or you want to give someone a temporary way to get to a room quickly, or whatever. The ABODE flag lets people @link themselves to a room, which sets the room as their home. Use @set here=ABODE.
+
The ABODE flag lets people @link themselves to a room, which sets the room as their home. Use @set here=abode
−
 
 
  
−
= Hangouts and the Directory =
+
= Hotspots =
 
Approved and linked to the grid?  
 
Approved and linked to the grid?  
−
* Do you want your build to be a [[Mush_help:Hangouts|+hangout]]? Send a +req/build with ATTN Dresden in the title to be added.
+
* Do you have a public building and want it to be shown on '''+hotspots'''? Send a +request/build and ask for it to be added.
−
* Do you want your build added to the [[Mush help:Directory|+directory]]? Same! Send a +req/build with ATTN Dresden in the title to be added.
 
  
−
= And Then... =  
+
= Security =  
 
Have you considered [[Equipment/Security_Systems|security]]?
 
Have you considered [[Equipment/Security_Systems|security]]?

Latest revision as of 09:34, 1 April 2018

Submitting a Build Request

The purpose of this guide is to familiarize you, the player, with building information that you will need to set up a home or business on From the Ashes: Detroit by Night. Here are a few things you should put in your +request/build:

  • The name of your build.
  • How many rooms you will be needing. The number of rooms you can have is determined by your resource level.
  • What area on the +map you want to be linked. Take a look at the grid for ideas and to get a feel for the style of the district you wish to build your project in. Check residences for a list of possible apartments that might suit your needs and Resource level. Some of these are already furnished with descs that can be customized, while others will require you to build a room in its entirety.
    • Please be advised that if your build does not suit the location or your Resources, you may be asked to modify your project.

Example:

+request/build Bazooka Lounge=I would like to make a two roomed club linked to #11.


There are some existing businesses available on the grid for PC ownership. If your concept fits one of these, do an 'ex' on the exit. If it's owned by "The D" that means it's open for new management and could be yours if you wanted it to be! Residences, shops, and other building ideas are welcome here and there are existing buildings where shops, cafes and other boutiques can be linked, such as the Guardian Building, and the Fisher Building. Check businesses for currently available enterprises.

Formatting

Because we like the grid to have a certain amount of uniformity, BuildStaff insists on the following:

  • Room desc format. Room descs must begin with %r[space(7)], have %r%r[space(7)] between paragraphs, and end with %r.
  • Exit descs. The above applies to Exits, too. Every exit needs to have an @desc, even if it's hidden or transparent.
  • @osuccs. All exits in a building project will require exit emits. This will be detailed later on.
  • @parent. Here at From the Ashes: Detroit by Night, we use only one parent for all rooms. @parent here=#6 This parent automatically formats the headers and footers for your room, as well as the exit format, which will automatically use the first letter of the first word as the Exit name, unless you specify otherwise (which you should). You do not need to add <> to anything.
  • Spellchecking can be overlooked. You don't need to be a perfect writer to play here, but we have provided a resource to use should you desire it. You can find lots of spell checkers online - for example, spellcheck.net.

STEP 1: Renaming your exit

Once your building request has been approved, you will be granted a starting room in the Building Nexus. The starting room is the very first room of your building project. Your Exit will be named something like: 'Will's Starterroom <WIL>'. The first thing you will need to do is consider what you are building. An Apartment? A House? A business? A business will need to be given the name of the business. An apartment, an apartment number. A house will require a house number and street name.

  • For a business:
    • @name WIL = Bazooka Lounge;bl;bazooka
  • Or for an apartment:
    • @name WIL = 104;104
  • Or for a house:
    • @name WIL = 1313 Mocking Bird Lane;1313

STEP 2: Rename Your Room, @parent and Descing

You need to rename your starter room. Go inside the room.

  • @name here = The Bazooka Lounge - Vestibule

Rooms should begin with the name of the apartment, business or house name, then the name of the specific room. Foyer. Lounge. Living Room. And so on and so forth.

Next, you need to @parent your room as described in the Formatting section above. @parent here=#6

Now you are ready to begin descing your room and exits. Writing @descs is a creative process. It allows you to visually imagine a location, and fill in the details of the location with your words. @descs should be detailed and as descriptive as you like, though any exit that links to a street or outdoor location should receive a bit of extra attention. This exit tells people what the exterior facade of your store front or house looks like to anyone passing by and gives flavor to the location. All descs require a certain format be maintained as outlined above in the Formatting section.

  • @desc here=%r[space(7)]This is my desc. Isn't it nice?%r

Or to desc an exit:

  • @desc o=%r[space(7)]This is what the door looks like.%r

STEP 3: Exits

Now that you have @desc'd your room, your exits, what's next? Exit @succ's. These are the messages you receive when you move between exits. There are 5 of them that you need. They are:

  • @succ
  • @osucc
  • @odrop
  • @fail
  • @ofail

The specific information on each can be accessed by typing help @succ, replacing @succ with whichever you're curious about. Specifically, this is what each does.

@succ - Sets the message that is shown to someone who successfully passes through the exit.

@osucc - Sets the message that is shown to others whenever someone successfully passes through the exit (in the room where the exit is).

@odrop - Sets the message that will be shown to others on the OTHER side of the exit you pass through (in the room where the exit goes).

@fail - Sets the message that is shown to someone who fails to pass through the exit.

@ofail - Sets the message that is shown to others whenever someone fails to pass through the exit (in the room where the exit is).

These are the basic requirements of an exit. Examples are as follows:

  • @succ o=You walk out the door.
  • @osucc o=walks out the door.
  • @odrop o=walks out of Apartment 202.
  • @fail o=The door appears to be locked.
  • @ofail o=tries to walk out the door, but it appears to be locked.

STEP 4: The Next Room

Now that you have finished with your starter room, it is time to make the next one (if there is a next one).

Start in your existing room. There you will need to use the @dig command.

  • @dig Kitchen = Kitchen;k;kitchen,Out;o;out

This command creates the new room, an exit into that room, and an exit back out of that room to your starter room.

Make sure you follow all preceding steps on each new room. And that's it! You are done!

Before you resubmit your project for inspection and approval to be linked via +request/build, please make sure you have not overlooked anything. The following are often missed:

  • Ensure all descs start with %r[space(7)] and end with a %r
  • Ensure your exits have descs. Every exit needs an @desc
  • Don't forget to rename the exit INTO your starterroom. See Step 1 for how to do that.
  • Don't forget to @parent your room.
  • @odrop on every exit. It is often overlooked.
  • +inspect here can be used to view all the existing parts of a room in order to ensure they've all be set.

Places

Places code is immensely useful for large scenes. It provides a way to filter messages that helps you concentrate on just the people near your character while still being able to watch everyone else. Any public builds, ones where PCs are encouraged to loiter about and RP, are encouraged to have places code set up.

Places code is also useful when you have a large house, too. Instead of building a kitchen, a sitting room, and a dining room off your living room, why not make those areas places in the living room? Why shouldn't the people in the living room be able to see people going into and coming out of the kitchen or maybe overhear them if they're talking loudly enough? Why bother descing entire rooms that are rarely used? Put them into places.

For installation of places, please see the +help files on From the Ashes: Detroit by Night by typing +help places-config.

  • For additional configuration options, type +help places-options.

Miscellaneous Commands

Dark

Setting an exit DARK makes that exit invisible to the room. Anyone will be able to use the exit so long as they know what to type. Very useful for hidden doors to secret rooms. @set <exit>=dark

Unfindable

One room in your build may be set UNFINDABLE, if you have more than one. A safe room, for instance, or sanctum. Setting the room unfindable removes it from the +where list. @set <here>=undfindable.

Transparent

Setting an exit TRANSPARENT allows you to see the next room beyond the exit. Helpful if the door is made of glass, for instance, or is simply an open archway. @set <exit>=transparent

Abode

The ABODE flag lets people @link themselves to a room, which sets the room as their home. Use @set here=abode

Hotspots

Approved and linked to the grid?

  • Do you have a public building and want it to be shown on +hotspots? Send a +request/build and ask for it to be added.

Security

Have you considered security?

Retrieved from "http://fta.procacious.com/wiki/index.php?title=Build_Guide&oldid=6028"