Post by Rarity on Jan 26, 2012 18:30:38 GMT -5
Good Evening, darlings, and welcome to another edition of The Fine Art of Role Play, with your furiously flirtatious, faithfully fantastic, fabulously fabulous filly of fantasies, Rarity!!
So tonight we have an extra special class for you: descriptions on a technical level! I shall do regular descriptions another time and date, but this, tonight, is to help any pony having an issue with descriptions! Not the easiest thing to master, ( am utterly hopeless with the things) so thats why we have an special guest tonight- Our prodigious programmer pony, Programmerpony! (He programs)
So, as such, darlings, tonight's class IS such that of the hard working wizards of our little corner of the muck! Something told to me by the wizards themselves! without further ado, lets diving into the world of descriptions!!
ProgrammerPony:
Just a quick basic review:
pub is our public-chat command.
ansi #on is how characters see color.
Where/find, look, ws (whospecies) and WHO are the most used basic commands. > is OOC.
For builders out there: @dig creates a room and links it to a parent.
@recycle destroys unused objects (use carefully, if you use).
@action creates exits for rooms (that's one function).
@link links up your exits to other rooms.
@attach allows you to move exits around.
Oooo darling! Very technical! Very...erm...Technical! Yes! Not all of us are builders, of course, but just in case you are granted such permissions, this is a handy little guide to use! What else is there? (Also, be sure to thank our wall-eyed wonder, Derpy Hooves, for she writes most of the descriptions for the rooms we RP in! )
@name allows renaming of rooms. IF you ever need to rename a mistyped exit : say you named exit #123 incorrectly, @name #123=newname will correct it.
For exits, you can add aliases to exits with the ; symbol. For example: Rarity's Sewing Room;RSW. This allows players to use RSW as well as the full name to use the exit. When looking at an exit, it'll show the main name, as well as the alises. Be careful, when adding aliases to exits, not to conflict with existing globals or the names of characters. Local exits that conflict with globals or player names will take precedence. Remember, using a player's name for an exit is bad! So if you try to make an exit called look, players won't be able to use look in that room. A player's name for an exit can interfere with certain examine programs. It used to interfere with @po, but that got fixed.
In Short, - If that player happens to be in the room, and someone else tries to look at them, they might end up looking at the exit instead
in addition, @open. It creates an exit on a room, then links it to the appropriate next room. It can be used in place of @action and @link for exits.
Remember, too, that one-letter aliases generally are good to avoid. Better to be reserved for existing (or future) muckwide commands.
Oooo thank you, Programmer! This...this is all entirely over Miss Rarity's head. All of it. I seriously have no idea what you are talking about. At all. So, um...carry on. Yes. MPI commands are next? That's utterly charming. ._.
@desc object=description will create a simple description, that's usually limited to about 256 characters (that's the muck-limit for output to a client on a single line of text). For more lengthy descriptions, someone can use lsedit. That stands for LiSt Editor. You can create lists of, say, descriptions, allowing for more then one solid description line."
Let's say you have 5 paragraphs of description you want to create. @desc me=description just won't do it. You create the description with a list name (say, desc). lsedit me=desc creates a list called 'desc' on me. lsedit here=desc creates one for the room.
You attach the list to the player or room by typing @desc me={list:desc} or @desc here={list:desc}.
Lists are item-specific. You have to attach the list to something when you create it, be it an object, room, or person. So to use a list for your description, you'd want to use 'me' as the item to attach the list to."
On you (me) means the list applies to you. If you make a description on you, it means it'll be your description for your character
For anyone that doesn't know, the {} in the @desc me={list:desc} is MPI. It can be placed on any description or property on an object. The list here means that it's going to produce a single description from the specified list, which is desc, which is what you create in lsedit.
WELL! That...that is all the time we have for tonight on The Fine Art of Role Play, with your teacher, Rarity. No, Darling, I have no idea what was going on. I've hardly got my desc working properly. So be SURE to ask Programmer Pony, Econnomistbrony or Derpy Hooves what the hey they're talking about.
Do. Not. Ask. Rarity. She can only give you fashion advice.
So tonight we have an extra special class for you: descriptions on a technical level! I shall do regular descriptions another time and date, but this, tonight, is to help any pony having an issue with descriptions! Not the easiest thing to master, ( am utterly hopeless with the things) so thats why we have an special guest tonight- Our prodigious programmer pony, Programmerpony! (He programs)
So, as such, darlings, tonight's class IS such that of the hard working wizards of our little corner of the muck! Something told to me by the wizards themselves! without further ado, lets diving into the world of descriptions!!
ProgrammerPony:
Just a quick basic review:
pub is our public-chat command.
ansi #on is how characters see color.
Where/find, look, ws (whospecies) and WHO are the most used basic commands. > is OOC.
For builders out there: @dig creates a room and links it to a parent.
@recycle destroys unused objects (use carefully, if you use).
@action creates exits for rooms (that's one function).
@link links up your exits to other rooms.
@attach allows you to move exits around.
Oooo darling! Very technical! Very...erm...Technical! Yes! Not all of us are builders, of course, but just in case you are granted such permissions, this is a handy little guide to use! What else is there? (Also, be sure to thank our wall-eyed wonder, Derpy Hooves, for she writes most of the descriptions for the rooms we RP in! )
@name allows renaming of rooms. IF you ever need to rename a mistyped exit : say you named exit #123 incorrectly, @name #123=newname will correct it.
For exits, you can add aliases to exits with the ; symbol. For example: Rarity's Sewing Room;RSW. This allows players to use RSW as well as the full name to use the exit. When looking at an exit, it'll show the main name, as well as the alises. Be careful, when adding aliases to exits, not to conflict with existing globals or the names of characters. Local exits that conflict with globals or player names will take precedence. Remember, using a player's name for an exit is bad! So if you try to make an exit called look, players won't be able to use look in that room. A player's name for an exit can interfere with certain examine programs. It used to interfere with @po, but that got fixed.
In Short, - If that player happens to be in the room, and someone else tries to look at them, they might end up looking at the exit instead
in addition, @open. It creates an exit on a room, then links it to the appropriate next room. It can be used in place of @action and @link for exits.
Remember, too, that one-letter aliases generally are good to avoid. Better to be reserved for existing (or future) muckwide commands.
Oooo thank you, Programmer! This...this is all entirely over Miss Rarity's head. All of it. I seriously have no idea what you are talking about. At all. So, um...carry on. Yes. MPI commands are next? That's utterly charming. ._.
@desc object=description will create a simple description, that's usually limited to about 256 characters (that's the muck-limit for output to a client on a single line of text). For more lengthy descriptions, someone can use lsedit. That stands for LiSt Editor. You can create lists of, say, descriptions, allowing for more then one solid description line."
Let's say you have 5 paragraphs of description you want to create. @desc me=description just won't do it. You create the description with a list name (say, desc). lsedit me=desc creates a list called 'desc' on me. lsedit here=desc creates one for the room.
You attach the list to the player or room by typing @desc me={list:desc} or @desc here={list:desc}.
Lists are item-specific. You have to attach the list to something when you create it, be it an object, room, or person. So to use a list for your description, you'd want to use 'me' as the item to attach the list to."
On you (me) means the list applies to you. If you make a description on you, it means it'll be your description for your character
For anyone that doesn't know, the {} in the @desc me={list:desc} is MPI. It can be placed on any description or property on an object. The list here means that it's going to produce a single description from the specified list, which is desc, which is what you create in lsedit.
WELL! That...that is all the time we have for tonight on The Fine Art of Role Play, with your teacher, Rarity. No, Darling, I have no idea what was going on. I've hardly got my desc working properly. So be SURE to ask Programmer Pony, Econnomistbrony or Derpy Hooves what the hey they're talking about.
Do. Not. Ask. Rarity. She can only give you fashion advice.
