Difference between revisions of "Designing"

From Archives of Lusternian Lore
Jump to navigation Jump to search
(Created page with "__toc__ {| class="wikitable" style="margin-left: auto; margin-right: 0px; float:right; width:30%" !Design Commands |- |DESIGN LIST <cartel> |- |DESIGN REQUEST <pattern> FOR <...")
 
m (added to Guides category)
 
Line 345: Line 345:
===Design List/Approved===
===Design List/Approved===
The final bit of syntax is DESIGN LIST <cartel>, which functions for a trademaster in the same way that CARTEL <cartel> LIST does, and DESIGN APPROVED <trade> which functions identically to the trade specific recipe or pattern verb followed by the ALL argument, such as JEWELRY ALL for jewelry or RECIPES ALL for cooking.
The final bit of syntax is DESIGN LIST <cartel>, which functions for a trademaster in the same way that CARTEL <cartel> LIST does, and DESIGN APPROVED <trade> which functions identically to the trade specific recipe or pattern verb followed by the ALL argument, such as JEWELRY ALL for jewelry or RECIPES ALL for cooking.
[[Category: Guides]]

Latest revision as of 17:51, 23 July 2022

Design Commands
DESIGN LIST <cartel>
DESIGN REQUEST <pattern> FOR <cartel>
DESIGN <sketch> APPEARANCE <description>
DESIGN <sketch> DROPPED <description>
DESIGN <sketch> COMMODITIES <commodity list>
DESIGN <sketch> TASTE/SMELL <description> [cooking only]
DESIGN <sketch> CONSUME [cooking only]
DESIGN <sketch> EXAMINED <description>
DESIGN <sketch> DESIGNEDBY <person>
DESIGN <sketch> RECALL
DESIGN <sketch> COMMENT <text>
DESIGN PATTERNS [TAILORING | COOKING | JEWELRY | FORGING | ARTISAN | BOOKBINDING | TATTOOS]
DESIGN LISTCOMMS
DESIGN COMMS <trade> [<type>]
DESIGN <sketch> TENT_APPEARANCE <text> [tents only]
DESIGN <sketch> TENT_DROPPED <text> [tents only]
DESIGN <sketch> TENT_EXAMINED <text> [tents only]
DESIGN <sketch> CLOSED <text>
DESIGN <sketch> SEAL_TEXT <text> [stamps only]
DESIGN <sketch> SEALHOLDER ORG <organization> [stamps only]
DESIGN <sketch> SEALHOLDER PERSON <person> [stamps only]
DESIGN PENDING [<type>]
DESIGN SEARCH <*pattern*>
DESIGN <sketch> TYPE <type>
DESIGN <sketch> LIQUID <liquid type>
DESIGN <sketch> WEAPONTYPES <types> [scabbards only]
OFF>
DESIGN <sketch> TATTOOWEIGHT <1-100> [tattoos only]
DESIGN APPROVED [TAILORING | COOKING | JEWELRY | FORGING | ARTISAN | BOOKBINDING | TATTOOS]
DESIGN <sketch> MAKECARTEL
DESIGN <sketch> MAKEPUBLIC
DESIGN <sketch> TRASH
DESIGN <sketch> SUBMIT
DESIGN <sketch> NOMORTALREVIEW
DESIGN <sketch> MORTALREVIEW

Getting Started

The Designing system is fairly daunting to look at, but once you have the hang of it it's a simple, if time consuming process.

As can be seen from the syntax lists to the side, each pattern has several fields that need to be filled out, based on the skill and the abilities required. To start with, trademasters should look at DESIGN PATTERNS <tradeskil>.

For instance,

DESIGN PATTERNS COOKING
You may design based on the following patterns:
**********************************************************
[ID]    [Org]         [Type]        [Description]
----------------------------------------------------------
19      Public        Brews         a dark ale
20      Public        Baking        some plain bread
22      Public        Soup          a plain soup
33      Public        Pastries      a plain pie
43      Public        Dishes        a plain fishcake
46      Public        Wine          a red wine
48      Public        Wine          a sparkling champagne
**********************************************************
Total: 7
NOTE: This is just an example, most lists will be much longer to provide a wonderful variety of bases to start your design from.

This returns a list of base patterns that can be used within that tradeskill. A trademaster can then DESIGN REQUEST <pattern> FOR <cartel>. For instance, to create a sandwich design,

DESIGN REQUEST 95 FOR GASTRONOMISTS
You create a design for a cheddar scone with ham and honey-mustard (23799).


Oops, that's not right...If you've made a serious mistake, for instance if you requested the design for the wrong cartel, or you accidentally requested a normal suit instead of a greatrobes suit, you can DESIGN <sketch> TRASH to delete it and start again from DESIGN REQUEST <pattern> FOR <cartel>.

DESIGN 23799 TRASH
You trash the selected design.

DESIGN REQUEST 93 FOR GASTRONOMISTS
You create a design for a plain sandwich (23799).

This creates the sketch with which the remaining commands are used. To see the sketch, enter DESIGN <number>

DESIGN 23799
Item: Sandwich  Type: Dishes  Org: Public
Ingredients: meat 4 grain 3 vegetables 3
Mortal Reviews: Allowed
IMPORTANT: The main noun MUST use one of these: SANDWICH
Appearance:
a plain sandwich
Dropped:
A plain sandwich lies here.
Examined:
This is a very plain sandwich and needs changing.
Consume:
This is very plain and needs changing.
Smell:
This is very plain and needs changing.
Taste:
This is very plain and needs changing.
WARNINGS:
 - Examined might be too short (depending on design type).
Please review the design and correct any problems before submission/approval.
Comments:
NOTE: It's important to pay attention to any warnings, as these are put in place to prevent rejections out of hand. Also, please remember that for all fields, proper British spelling and grammar rules are to be followed unless otherwise noted.

The Specifics of a Sketch

Item, Type, Org, DesignedBy

DESIGN 23799
Item: Sandwich  Type: Dishes  Org: Public

The first field is the item. This entry cannot be changed, and represents the main noun by which the pattern will be interacted. For our current example, this is Sandwich. Type likewise cannot be changed for most patterns, and indicates which skill the tradesperson must possess to create the item. Our sandwich can be either DISHES or GOURMET, but we'll leave it as a dish for now. Org will either be public or cartel, through the MAKECARTEL and MAKEPUBLIC commands.

DESIGN 23799 MAKECARTEL
You note that this design is cartel specific.

Item: Sandwich  Type: Dishes  Org: Gastronomists
DESIGN 33799 makepublic
You make the design public. 

Item: Sandwich  Type: Dishes  Org: Public

A field that does not appear until used is next., the DESIGNEDBY field. While not required, this can still be an important field, and a good trademaster should always fill this in unless there's a good reason.

design 23799 designedby Luce
You note that Luce designed this.

Item: Sandwich  Type: Dishes  Org: Gastronomists  Designer: Luce

The commodities or ingredients are the costs connected to the pattern or recipe, however it's often best to leave this field until last, so we'll skip it for now.

Next is whether or not mortal reviews are allowed. By default, this is true, and should only be switched to DESIGN <pattern> NOMORTALREVIEW if there is something specific that would require divine attention anyway, such as needing admin permission. Our sandwich will not, but examples that might are tapestries depicting the Gods or historical events, jewelry that incorporates Divine symbolism, or something you feel might be on the borderline of Lusternia's tone and theme.

Appearance, Dropped, and Examined

Appearance:
a plain sandwich
Dropped:
A plain sandwich lies here.
Examined:
This is a very plain sandwich and needs changing.

The next few fields are the most important, and every design save for beverages and tattoos have them. These are the Appearance, Dropped, and Examined fields. Appearance is the short description of the item that is shown when you interact with it in the inventory. It should be descriptive, but limited to the item itself, and it is very important to watch the spelling and grammar for the item, and that it includes the main noun. For example:

DESIGN 23799 APPEARANCE a Delportian toast sandwich

Item: Sandwich  Type: Dishes  Org: Public  Designer: Luce
Ingredients: meat 4 grain 3 vegetables 3
Mortal Reviews: Allowed
IMPORTANT: The main noun MUST use one of these: SANDWICH
Appearance:
a Delportian toast sandwich
NOTE: As mentioned in the HELP TRADEMASTERS file, when making the appearance you do not capitalise the first word unless it is a proper noun. You also do not use any punctuation at the end, since the game's inventory engine does this already. Likewise, you must use the main noun so that it can be properly managed.

Next is the dropped, which must be a full sentence, including a leading capital and a full stop at the end.

DESIGN 23799 DROPPED A Delportian toast sandwich lies here upon a porcelain plate.

Item: Sandwich  Type: Dishes  Org: Public  Designer: Luce
Ingredients: meat 4 grain 3 vegetables 3
Mortal Reviews: Allowed
IMPORTANT: The main noun MUST use one of these: SANDWICH
Appearance:
a Delportian toast sandwich
Dropped:
A Delportian toast sandwich lies here upon a porcelain plate.

And next we come to the examined. This is a full description of the final product. Anything that is readily observable can and should be included, including sounds that can be heard or vague scents. (For food, there is a smell field that is specific to it, which is where a similar detailed description of scent alone would go, but it is acceptable to include a brief or vague sense of the scent in the examined as well, especially for non-food items with a particular smell.)

Unlike previous commands, this one is simply DESIGN <pattern> EXAMINED, which opens the editor to allow for more robust values, like so:

DESIGN 23799 Examined

You sketch out the fine details of how the proposed item will look when examined closely.

Design 23799
Item: Sandwich  Type: Dishes  Org: Public  Designer: Luce
Ingredients: meat 4 grain 3 vegetables 3
Mortal Reviews: Allowed
IMPORTANT: The main noun MUST use one of these: SANDWICH
Appearance:
a Delportian toast sandwich
Dropped:
A Delportian toast sandwich lies here upon a porcelain plate.
Examined:
Resting on a glazed porcelain plate, this sandwich is positively covered in maple syrup. It is primarily composed of thick-sliced bread that has been dipped in an egg yolk batter and lightly glazed with maple syrup before being fried. Two such slices were used for this sandwich, easily an inch thick each. Between them, the egg whites have been used to make an omelette that rests on a bed of more syrup. On top of this, three thick-cut slices of maple-soaked bacon have been added, and on top of that, a second slice of bread dusted with confectioner's sugar. Finally, a sausage link has been cut in half, fried in syrup, and skewered to the top of the sandwich, with still more syrup drizzled over it. Helpfully, a napkin has been provided.
The entire dish smells strongly of syrup, and still sizzles faintly.

Trade Specific Fields

The next three fields are for food items only. They are the Consume, Smell, and Taste. Each is accessed similarly to the appearance save the consume, which functions like the examined. Other tradeskills can have fields specific to them as well, such as the SEALHOLDER field for stamps, the WEAPONTYPES field for scabbards, or the TATTOOWEIGHT field for tattoos.

Please see existing patterns or another Trademaster if you have questions about a specific field unique to your pattern.

Wrapping Up

Commodities

Now that the design itself is fully sketched out, we go back to the commodities. To see how many are required, use DESIGN COMMS <trade> <type>. For our example pattern, this is going to be

DESIGN COMMS COOKING DISHES
Designs for Cooking Dishes require at least 10 commodities.

It's important to remember HELP DESIGN COMMS for this, because each pattern must be made from at least 75% (rounded up) base commodities, which are provided in that file. As well, each of those ingredients, and ideally their logical ratio, should reflect what might actually be required for the design. For our sandwich, the bread requires grain, and it's fairly thick bread so we'll use 2 of them, the bacon and sausage are obviously meat, but there's not much of either so we'll only use 1. Both the omelette portion and the toast itself require eggs but since the dip for the toast was made from yolk and the rest from the whites, we'll use just 1 egg commodity. To represent the onions in the omelette we'll need a vegetables and milk for the butter, and for the cinnamon and pepper mentioned we'll need spices. So far, that makes grain 2 meat 1 egg 1 milk 1 vegetable 1 spice 1, for a total of 7. We still need 10, though, and we never made a commodity for all that syrup. Since the syrup is by far the biggest chunk of the design, it's mentioned everywhere after all, it's fair to assume the remaining 3 commodities could go to syrup, which is sugar.

DESIGN 23799 COMMODITIES GRAIN 2 MEAT 1 EGGS 1 MILK 1 VEGETABLES 1 SPICES 1 SUGAR 3
You propose the recommended commodity cost for this item. Please make sure it is in the form of type and amount of commodity (e.g., cloth 5 leather 5). NOTE: This is only a recommendation and may be adjusted upon approval.
NOTE: Some designs require exotic materials. To see a full list of what materials are available, see DESIGN LISTCOMMS. These can make up no more than 25% of your required commodities, which means that whatever is given under DESIGN COMMS <trade> <type> must have at least 75% base comms, as provided by HELP DESIGN COMMS.
SPECIAL NOTE FOR COOKING: Cooking designs are somewhat unique in that you do not need to account for the non-food portions of the design. Notice that our example did not include the marble comm to account for the porcelain plate, or the cloth for the napkin. This is not true in reverse. If an artisan rack mentioned jerky drying on it it would need a meat commodity or a corpse for instance.

Comments

Our Design so Far

Item: Sandwich  Type: Dishes  Org: Public  Designer: Luce
Ingredients: grain 2 meat 1 eggs 1 milk 1 vegetables 1 spices 1 sugar 3
Mortal Reviews: Allowed
IMPORTANT: The main noun MUST use one of these: SANDWICH
Appearance:
a Delportian toast sandwich
Dropped:
A Delportian toast sandwich lies here upon a porcelain plate.
Examined:
Resting on a glazed porcelain plate, this sandwich is positively covered in maple syrup. It is primarily composed of thick-sliced bread that has been dipped in an egg yolk batter and lightly glazed with maple syrup before being fried. Two such slices were used for this sandwich, easily an inch thick each. Between them, the egg whites have been used to make an omelette that rests on a bed of more syrup. On top of this, three thick-cut slices of maple-soaked bacon have been added, and on top of that, a second slice of bread dusted with confectioner's sugar. Finally, a sausage link has been cut in half, fried in syrup, and skewered to the top of the sandwich, with still more syrup drizzled over it. Helpfully, a napkin has been provided.
The entire dish smells strongly of syrup, and still sizzles faintly.
Consume:
You pause for a moment to consider how best to eat this sandwich before deciding to just tackle it with your bare hands. You start with the sausage on top, using the skewer as a utensil to bring each half of the link to your mouth, where you are treated to a smoky and savoury symphony of tastes that is prompty smothered by syrup. Once the sausage is gone, you pick the sandwich up to find that it's been cut diagonally and fit back together nearly seamlessly. This makes it more managable, and you bite into one corner of your first half. Once again, there is a subtle blend of flavours: butter, garlic, and onion mixed into the omelette; smoky bacon just at the edge of crispness, with a hint of cracked black pepper accenting its natural flavour; a tinge of cinnamon on the toast. All of which is drowned out by the maple syrup and the confectioner's sugar. You finish the first half and move on to the second, which is more of the same, and leaves you with a sticky sensation on your hands and mouth that the napkin just can't fully clean off.
Smell:
You take a whiff of a Delportian toast sandwich, and are rewarded with the savoury scent of cooked sausage and bacon, and the not-so-subtle overtones of maple syrup.
Taste:
You nibble the edge of one of the slices of toast, and your tongue is practically assaulted by maple syrup. Your fingers are left sticky.
Comments:

Commenting

This is our example design as it stands now. If you feel something needs to be explained, or if the Charites and mortal reviewers have returned the design and you need to delete the comments, you can use the DESIGN <sketch> COMMENT <text> command to do so.

design 23799 comment Hello, this is being used as an example for a guide. Please don't approve me yet, I'll be recalled in a moment and resubmitted when it's time to be considered.
You add comments for this design.

Comments:
Hello, this is being used as an example for a guide. Please don't approve me yet, I'll be recalled in a moment and resubmitted when it's time to be considered.

Submission

It's important to take a moment to give the design a final review to make sure everything is just so. Once you're satisfied with it, DESIGN <sketch> SUBMIT will send it to be reviewed.

design 23799 submit
You submit your design for review on behalf of the cartel.

Now you can take a look at DESIGN PENDING to see a list of designs currently being considered.

DESIGN PENDING
23799: a Delportian toast sandwich

If you notice a mistake at this point, use DESIGN <sketch> RECALL to recall the design and edit it further.

design 23799 recall
You recall the design for your cartel.

If the design has been rejected, you'll receive a notice or a message depending on whether you're online at the time, and the comments will have been edited to reflect what was found wrong with the design. Address whatever concerns were raised, then remove the comments by doing DESIGN <sketch> COMMENTS with no further text, and submit it for re-review.

Design List/Approved

The final bit of syntax is DESIGN LIST <cartel>, which functions for a trademaster in the same way that CARTEL <cartel> LIST does, and DESIGN APPROVED <trade> which functions identically to the trade specific recipe or pattern verb followed by the ALL argument, such as JEWELRY ALL for jewelry or RECIPES ALL for cooking.