03-07-2014, 04:40 AM
(This post was last modified: 03-07-2014, 04:55 AM by LooseWilly.)
A note for those who like to use actual paragraphs...
The #T#Letter to <letter recipients name> ... line is the title of a document. If you are sending a letter via the caravan folks, that is the format you want to use. Type it like you were talking, then use your quill and target the sealed letter or document you want to use.
You can also use the #T#<stuff> to title any document or sealed letter with whatever you want. The format listed above is necessary to send via the caravan masters... but there may be other uses for a document/letter. Likewise, using #T# allows you to set a title on a message board document ...
#W#<content stuff> ... will give you content. What you will be able to see as you type is limited by the length of your chat bar. You can type what you can see, then press <return>, use the quill on whatever you're writing on, then follow up with another #W# (followed by a space, to you aren't right on top of the previous writings) ... and type in more... or you can type blindly, hope for the best, and edit between the <return> and the use of the quill upon the paper.
You can also, however, type #P# <return> and use the quill... and in so doing get a <return> in your document. Better yet, you can use a #P#2<return> and use the quill, so you get a double <return> and a blank line between paragraphs.
The #F#<return> is not necessary... but it will "finish" a document. What does that mean? It means it can not be further edited. If you are just sending an innocuous note, it doesn't matter much... if you're sending a sealed letter that you don't want anyone to "add to", potentially opening you up to accusations or feuds... then the #F# is a good idea.
The signet rings can be used generically with a #S#<description of one's sigil> followed by a targeting of a document (sealed letters, primarily)... or one can target the ring itself, which will carve the <description> into the ring... so that you can use it to #S# and target documents without any further need of adding the <description of one's sigil> on further uses.
The seal description will actually read, in the case of sealed letters, in the color of the ink that one uses when sealing a letter.
(I have not found a method for choosing between sealing waxes on my person with a given letter... if one has only one vial of wax, that's the color that will be used... if one has multiple colors, I am not sure what the algorithm is for deciding which wax gets used on any given letter... or if there might be a command flag to control that. I suggest dropping colors one doesn't want to use... then picking them back up after the fact.)
Ohh ... and some more details about different kinds of letters.
There are documents. They are essentially just sheets of paper able to hold a (relatively) limited amount of text.
There are letters... they have a seal, and you can use a signet ring to seal one with your own personal seal (#S#<description of personal seal> target letter). The interesting detail about these is that... they are sealed. You can't read them while they are sealed- because they are sealed. If you want to read one, then you have to open it... at which point the seal is broken... and it will become immediately obvious to anyone who looks at it that the letter has been intercepted and read (unlike a document, which anyone can read... and no one's the wiser).
This brings up an additional complication. Were there any typos in the writing of the sealed letter?... if you open it to find out... you've broken the seal. Did you overrun the text limit on the sealed letter? (OK, I might be the only one apt to do that...) ... no way to know, short of breaking that seal.
Well, that's not entirely true.
There are a couple more options of the quill that can come in handy here... if you're not worried about the costs of ink and stray paper. There's a #C# option that you can use... #C#<return> target something to copy... then target something else to copy to... as I recall #C# will just copy the body (which will allow you to add a different title).
Then there's also the #C#all option, which will copy title and body of a letter, then re-write it onto a targeted "pastee" document. Presto... you can address a document, and write it out... edit it... then use a #C#all to copy it to a sealed letter... and then mail it and know that the recipient will know if the message arrived secure, or not.
And, of course, there are the message board documents. These I have the least experience with, but there's a title, there's the #W#<body> #P#2 #W#<more body>... not sure about the need for a #F# (note... the #P#2 does not use up any ink... so I'm presuming that the #F# also doesn't use any ink). Once it's written... talk to the board and post it.
The #T#Letter to <letter recipients name> ... line is the title of a document. If you are sending a letter via the caravan folks, that is the format you want to use. Type it like you were talking, then use your quill and target the sealed letter or document you want to use.
You can also use the #T#<stuff> to title any document or sealed letter with whatever you want. The format listed above is necessary to send via the caravan masters... but there may be other uses for a document/letter. Likewise, using #T# allows you to set a title on a message board document ...
#W#<content stuff> ... will give you content. What you will be able to see as you type is limited by the length of your chat bar. You can type what you can see, then press <return>, use the quill on whatever you're writing on, then follow up with another #W# (followed by a space, to you aren't right on top of the previous writings) ... and type in more... or you can type blindly, hope for the best, and edit between the <return> and the use of the quill upon the paper.
You can also, however, type #P# <return> and use the quill... and in so doing get a <return> in your document. Better yet, you can use a #P#2<return> and use the quill, so you get a double <return> and a blank line between paragraphs.
The #F#<return> is not necessary... but it will "finish" a document. What does that mean? It means it can not be further edited. If you are just sending an innocuous note, it doesn't matter much... if you're sending a sealed letter that you don't want anyone to "add to", potentially opening you up to accusations or feuds... then the #F# is a good idea.
The signet rings can be used generically with a #S#<description of one's sigil> followed by a targeting of a document (sealed letters, primarily)... or one can target the ring itself, which will carve the <description> into the ring... so that you can use it to #S# and target documents without any further need of adding the <description of one's sigil> on further uses.
The seal description will actually read, in the case of sealed letters, in the color of the ink that one uses when sealing a letter.
(I have not found a method for choosing between sealing waxes on my person with a given letter... if one has only one vial of wax, that's the color that will be used... if one has multiple colors, I am not sure what the algorithm is for deciding which wax gets used on any given letter... or if there might be a command flag to control that. I suggest dropping colors one doesn't want to use... then picking them back up after the fact.)
Ohh ... and some more details about different kinds of letters.
There are documents. They are essentially just sheets of paper able to hold a (relatively) limited amount of text.
There are letters... they have a seal, and you can use a signet ring to seal one with your own personal seal (#S#<description of personal seal> target letter). The interesting detail about these is that... they are sealed. You can't read them while they are sealed- because they are sealed. If you want to read one, then you have to open it... at which point the seal is broken... and it will become immediately obvious to anyone who looks at it that the letter has been intercepted and read (unlike a document, which anyone can read... and no one's the wiser).
This brings up an additional complication. Were there any typos in the writing of the sealed letter?... if you open it to find out... you've broken the seal. Did you overrun the text limit on the sealed letter? (OK, I might be the only one apt to do that...) ... no way to know, short of breaking that seal.
Well, that's not entirely true.
There are a couple more options of the quill that can come in handy here... if you're not worried about the costs of ink and stray paper. There's a #C# option that you can use... #C#<return> target something to copy... then target something else to copy to... as I recall #C# will just copy the body (which will allow you to add a different title).
Then there's also the #C#all option, which will copy title and body of a letter, then re-write it onto a targeted "pastee" document. Presto... you can address a document, and write it out... edit it... then use a #C#all to copy it to a sealed letter... and then mail it and know that the recipient will know if the message arrived secure, or not.
And, of course, there are the message board documents. These I have the least experience with, but there's a title, there's the #W#<body> #P#2 #W#<more body>... not sure about the need for a #F# (note... the #P#2 does not use up any ink... so I'm presuming that the #F# also doesn't use any ink). Once it's written... talk to the board and post it.