Gemcodes

Messaging in the Santa Cruz Chronicles is accomplished by the use of gemcodes. It might seem odd at first but it is a long standing tradition and one gets accustomed to it fairly soon. Gemcodes are prefixes in the subject of any e-mail message used for game communication. The gemcode used denotes the subject matter of the message and help game participants prioritize and organize their game e-mail without having to read the message itself. Gemcode priority is roughly approximate to colour of the gemstone used. Warmer colours generally have a higher priority than do cooler colours.

Players, directors, storyline editors. and stage hands are required to learn and follow gemcode etiquette. Patrons and associates are not expected to know or understand gemcodes.

Gemcoded e-mail should use the following format: Gemcode/Subject or in the cases of combat or dialogue, Gemcode/Acting Character/Receiving Character. See below for examples.

	Pearl Use: storyline editor messaging Example: Pearl/Plot contradiction Pearl is reserved for storyline editor use. The Pearl gemcode denotes material concerning game governance. It should not be used by players.
	Amber Use: general messaging, highest priority, immediate response required Example: AMBER/Lack of contact You need it, you need it now. Amber requires immediate response. This gemcode is generally reserved for storyline editors or directors contacting a player or players. Players should refrain from using Amber as there are few situations that require an immediate response for a player. This is an e-mail game after all, and as such, some lag is a given. Storyline editors, however, juggling many threads, often don't have the luxury of waiting since an inappropriate delay to an answer could hold up moves for several intertwined players.
	Opal Use: timestop announcement, very high priority Example: Opal/March 17th This is a high priority announcement that you should open and take note of immediately, as it might concern the move you are writing. Please refer to the Timestop rules for more information. This gemcode is reserved for the main storyline editor contacting the players.
	Topaz Use: combat, very high priority Example: Topaz/Connor/Kurgan Formal combat requires numerous messages to resolve an action or series of actions that often only span seconds or minutes. Such combat actions need to be resolved as quickly as possible in order to bring the combat to a conclusion. Topaz messages do not require immediate response but should be attended to as soon as conveniently possible. Topaz gemcodes always indicate the attacker and then the person being attacked. In the above example, this sequence deals with an attempt by Connor to attack the Kurgan. Reference the specific rules on combat for more information.
	Ruby Use: general messaging, high priority Example: Ruby/Need clarification For general messages out of character, there are two priority levels, low and high. Ruby denotes a high priority message and should be used if you need the response sooner than a Jade gemcoded would allow for. Essentially, your move or dialogue cannot proceed without an answer, or you would like an answer before proceeding.
	Amethyst Use: dialogue, moderately-high priority Example: Amethyst/Woody/Buck Amethyst means a conversation, in character, either between two principal players, or between a featured player character and a supporting character that is run either by a storyline editor, understudy or stand-in. Reference the specific rules on dialogue for more information. The subject of the example says this is a dialogue message from Woody speaking to Buck. Common courtesy means you must respond to dialogue fairly soon, lest the conversation stall and loose steam. Always keep on top of Amethyst gemcoded e-mails.
	Iolite Use: move rework, moderately-high priority Example: Iolite/Raphael This is not a good one to get. It means your move is being returned to you for corrections. Corrections could be: skipping spell-check; continuity or plot errors; missing portions from move outline; or the fiction is just generally not up to snuff. Generally you will receive guidance, examples, or suggested corrections as part of this gemcoded message to help you correct your move. Your move will not progress until corrections have been made. Storyline editors send out Iolite messages only after they review and concur with a director request. Storyline editors must get the approval of the governing director if they are the initiator of an Iolite.
	Sapphire Use: move, moderate priority Example: Sapphire/Raphael Sapphires are the gems you want to look out for if you're a player or playwright, sending or expecting a move. To a storyline editor or playwright, it means that a fictionalized outline, ready for editing and then posting has been received. To a player, it means that a move outline based on her previous action list has arrived in her in-box. Now she can see what happens based on her move intentions.
	Aquamarine Use: art, moderately-low priority Example: Aqua/Vampire - New Art List Feel free to shorten this one to just Aqua. For artists only, Aquamarine is used for art specific messaging, usually an announcement of a new chronicle overhaul and a list of new illustration needs. Any Aqua/Aquamarine gemcoded messages are presumed to deal with art.
	Jade Use: general messaging, low priority Example: Jade/Bianca costume clarification Low priority gemcode that denotes something the sender needs but which is not in a great hurry for, and he can proceed without hearing from the director or storyline editor. If there is a crush of e-mail, Jade gemcodes will be skipped over until there is time to deal with them. However, they are not lost and forgotten.
	Peridot Use: technical problems, very low to very high priority Example: Peridot/Page won't load It might seem odd to think that technical problems are low priority, but in the scheme of things, the actual dealing with moves and answering game questions are considered more important. Technical problems are generally something that can be taken care of in time, unless they prevent viewing of the information, in which case they are high priority issues. The yellow-green of this gemcode complete the colour wheel and indicates the dual purpose use of Peridot. Stage technicians tasked with dealing with Peridot gemcodes can prioritize them as they see best.
	Onyx Use: announcement, lowest priority Example: Onyx/Move Update - Heathcliff The gemcode is used for game announcements that do not require a response. Typical Onyx gemcoded messages include move updates, art and article announcements, and information posts about web resources.