Difference between revisions of "+Build Help"

From City of Hope MUSH
Jump to navigation Jump to search
imported>Eloise
(Updating)
 
(8 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 +
=New Builds How To=
 +
<big>The information here applies to NEW BUILDS that are not on the grid.  If you are taking over an existing build, most of this will not apply.</big>
 +
<br>
 +
<br>
 +
<b>
 
:::Building with +build, an A to Z ........
 
:::Building with +build, an A to Z ........
  
Line 28: Line 33:
  
 
The game will then show us this message: <br>
 
The game will then show us this message: <br>
:::<span style="color: Blue">Requested location for Cabin set to Deep Forest. +map should now work within the project. </span>
+
:::<span style="color:Red">Requested location for Cabin set to Deep Forest. +map should now work within the project. </span>
  
 
Next you want to tell the code what rooms you want and what rooms have exits
 
Next you want to tell the code what rooms you want and what rooms have exits
Line 72: Line 77:
 
After you see the big long Blueprint readout above, all you do is
 
After you see the big long Blueprint readout above, all you do is
  
Type:  
+
:::Type:  
<span style="color: Blue">+build/magic </span>
+
:::<span style="color: Blue">+build/magic </span>
  
 
The game will show you:
 
The game will show you:
Line 85: Line 90:
 
Now, if you want to rename rooms within your project, it does not work like a lot of the games that you're used to. So don't just @name g=Grounds <G>;g as this will mess your exits all up!
 
Now, if you want to rename rooms within your project, it does not work like a lot of the games that you're used to. So don't just @name g=Grounds <G>;g as this will mess your exits all up!
  
 +
==Exits==
 
To rename exits properly for the +build code use: @name g=G:Grounds;g  
 
To rename exits properly for the +build code use: @name g=G:Grounds;g  
 
Rather than going Grounds <G> by going G:Grounds you achieve the same effect. The code will name your exit Ground <G> -for- you. Here are a few different examples:
 
Rather than going Grounds <G> by going G:Grounds you achieve the same effect. The code will name your exit Ground <G> -for- you. Here are a few different examples:
  
 
<span style="color:red">Exit Names:
 
<span style="color:red">Exit Names:
Frontdoor <Fr>  Backroom <Br>  Dark bRoom Kloset <DbK>  OuT <O> </span>
+
Frontdoor <Fr>  Backroom <Bro>  Dark bRoom Kloset <DbK>  OuT <O> </span>
  
 
Okay, so as you can see above, we've got some booboos in our exit names. To rename each of those -here- we would do the following:
 
Okay, so as you can see above, we've got some booboos in our exit names. To rename each of those -here- we would do the following:
Line 102: Line 108:
  
 
<span style="color:blue">@name o=O:Out;o;ou;out;b;ba;bac;back</SPAN>
 
<span style="color:blue">@name o=O:Out;o;ou;out;b;ba;bac;back</SPAN>
Results in: <span style="color:red">Out <O>
+
Results in: <span style="color:red">Out <O></span>
 
-- For this using 'o', or 'ou' or 'b' or 'back' will allow you to go through that particular exit. Be careful not to double up on things. Out <O> with Office <O> would be bad.
 
-- For this using 'o', or 'ou' or 'b' or 'back' will allow you to go through that particular exit. Be careful not to double up on things. Out <O> with Office <O> would be bad.
  
And there you have it! Just @desc as usual and you're set! Hope this helps
+
==Authorizing Others==
some people! When you're done @descing, simply +myjob/add #jobnumber=Done!
+
You can have help with your build without having to worry about who owns it. They can assist using the commands below.
To get your project linked to the grid. Also, include any of the doors that
+
 
you would like to have +locks set up on in your comment to the job at this
+
+bhelp +build - The help file
point
+
 
 +
+build/auth <project>=<player>  - Authorize a player for the specific project<br>
 +
+build/auth <player>            - Authorize a player on the selected project<br>
 +
+build/unauth <project>=<player> - Remove an authorized player from the specific project<br>
 +
+build/unauth <player>          - Remove an authorized player from the selected project<br>
 +
+build/ex here|<room>|<exit>    - As an authorized player, examine settable attributes on the room or exit<br>
 +
+build/set here|<room>|<exit>/<attribute>=<value> - As an authorized player, set attributes on a room or exit.<br>
 +
+build/edit here|<room>|<exit>/<attribute>=<from>,<to> - As an authorized player, edit an attributes on a room or exit.<br>
 +
 
 +
 
 +
==Night/Day Zones==
 +
&zone here=night<br>
 +
&zone here=day
 +
 
 +
==Custom Exit Messages==
 +
You can also set custom messages for those coming and going to rooms, but it is not required.<br>
 +
Examples:<br>
 +
@succ exit=You leave the den and enter the store room.<br>
 +
@osucc exit=leaves the den heading into the store room.<br>
 +
@odrop exit=enters from the den.<br>
 +
@fail exit=That door is locked.<br>
 +
@ofail exit=tried to open the door to the store room but couldn't.<br>
 +
 
 +
And there you have it! Just @desc as usual and you're set! Hope this helps some people! When you're done @descing, simply +myjob/add #jobnumber=Done!  
 +
 
 +
To get your project linked to the grid. Also, include any of the doors that you would like to have +locks set up on in your comment to the job at this point.

Latest revision as of 13:47, 17 January 2024

New Builds How To

The information here applies to NEW BUILDS that are not on the grid. If you are taking over an existing build, most of this will not apply.

Building with +build, an A to Z ........
SO! Your new build request has been approved. Great! Now what? It's really easier than it looks! Follow these simple steps & you won't have a problem.


Step 1:
Type: +build/list


You'll see something like:


<---======##=============[ Build Projects for Fakie ]=============##======--->
DBREF Name Rooms Authorized
<---======##=-------------------[ Unfinished ]-------------------=##======--->
#12345 Cabin 0/4 Fakie
<---======##=---------------------[ Linked ]---------------------=##======--->
<-------------=============++++++++++++++++++++++++=============------------->


Once you know what the DBREF of your project is (For this example its #12345)

Type:
+build/select #12345
The game then shows me this message (this is how we know it worked)

You have selected Cabin

Once that has been accomplished, you need to go to the IC grid location where you want your project to be linked from. If you're IC sometime type +MAP and, you'll see that each grid location has a specific number. For this project we are going to say it should be in the forest, so we will go to the forest and we'll choose a room, any room-- 786 will do. (When you go to the forest map, you'll notice that 786 is the very center 'entrance' to the forest area.)


Type:
+build/setloc #12345
..... because #12345 is our project's DB number or DBREF.
Note: You MUST be standing in the IC grid wher you want to link to. Think of your character as the 'You are here' marker like at a map at the mall.

The game will then show us this message:

Requested location for Cabin set to Deep Forest. +map should now work within the project.

Next you want to tell the code what rooms you want and what rooms have exits to what other rooms and so forth. This LOOKS complicated, but really its not!

Type:

+build/setbp 1:Grounds|2:Living Room|3:Master Bedroom|4:Upstairs/0--1|1--2|2--3|2--4

Once you've done that, the game will burp out a thing like this at you:

<---======##=================[ Blueprint: Cabin ]=================##======--->
Room 1: Cabin - Grounds
Room 2: Cabin - Living Room
Room 3: Cabin - Master Bedroom
Room 4: Cabin - Upstairs
Exit: (Outside) <--> Grounds
Exit: Grounds <--> Living Room
Exit: Living Room <--> Master Bedroom
Exit: Living Room <--> Upstairs
<-------------=============++++++++++++++++++++++++=============------------->

If this isn't self-explanatory enough, I'll break it down for you.

1:Grounds|2:living room|3:Master Bedroom|4:Upstairs

This is pretty simple. The very first room is the Grounds, Second is the living room, so on and so forth. These also serve as the exit names that lead into each room. They can be changed later. I'll explain that further down. (Yes! I KNOW this is already spammy as it is! I'm sorry!)

That crazy 0--1|1--2|2--3|2--4 stuff isn't as confusing as it looks either. I've already explained that the first room is the Grounds, the second is the living room, so on right? So if the first room is the Grounds, then 0 is just whatever leads -onto- the grounds. First that'll be the building nexus, then it'll be that IC grid room that you wanted your project linked off of.

So really all this madness does is simply tells the code what room has doors to what other rooms. So the grid (0) links to the Grounds (1), and then, for our example place here, the Grounds (1) links to the living room (2), and the living room links to the master bedroom (3) as well as the upstairs (4). Now, this all works the same whether you have 2 rooms, 4 rooms, or 50 rooms.

After you see the big long Blueprint readout above, all you do is

Type:
+build/magic

The game will show you: Build Launched Cabin Parent has left. Done.

From that point, all you do is go +ooc, then BN and your project should be the very first exit listed in the Build Nexus.

Now, if you want to rename rooms within your project, it does not work like a lot of the games that you're used to. So don't just @name g=Grounds <G>;g as this will mess your exits all up!

Exits

To rename exits properly for the +build code use: @name g=G:Grounds;g Rather than going Grounds <G> by going G:Grounds you achieve the same effect. The code will name your exit Ground <G> -for- you. Here are a few different examples:

Exit Names: Frontdoor <Fr> Backroom <Bro> Dark bRoom Kloset <DbK> OuT <O>

Okay, so as you can see above, we've got some booboos in our exit names. To rename each of those -here- we would do the following:

@name fr=FD:Front Door;fd
It will end up looking like: Front Door <FD>

@name br=BR:Back Room;br Results in: Back Room

@name DbK=DBC:Dark Broom Closet;dbc Results in: Dark Broom Closet <DBC>

@name o=O:Out;o;ou;out;b;ba;bac;back Results in: Out <O> -- For this using 'o', or 'ou' or 'b' or 'back' will allow you to go through that particular exit. Be careful not to double up on things. Out <O> with Office <O> would be bad.

Authorizing Others

You can have help with your build without having to worry about who owns it. They can assist using the commands below.

+bhelp +build - The help file

+build/auth <project>=<player> - Authorize a player for the specific project
+build/auth <player> - Authorize a player on the selected project
+build/unauth <project>=<player> - Remove an authorized player from the specific project
+build/unauth <player> - Remove an authorized player from the selected project
+build/ex here|<room>|<exit> - As an authorized player, examine settable attributes on the room or exit
+build/set here|<room>|<exit>/<attribute>=<value> - As an authorized player, set attributes on a room or exit.
+build/edit here|<room>|<exit>/<attribute>=<from>,<to> - As an authorized player, edit an attributes on a room or exit.


Night/Day Zones

&zone here=night
&zone here=day

Custom Exit Messages

You can also set custom messages for those coming and going to rooms, but it is not required.
Examples:
@succ exit=You leave the den and enter the store room.
@osucc exit=leaves the den heading into the store room.
@odrop exit=enters from the den.
@fail exit=That door is locked.
@ofail exit=tried to open the door to the store room but couldn't.

And there you have it! Just @desc as usual and you're set! Hope this helps some people! When you're done @descing, simply +myjob/add #jobnumber=Done!

To get your project linked to the grid. Also, include any of the doors that you would like to have +locks set up on in your comment to the job at this point.