CHE Officer Guide/Criers - Revision history

HOST-GSKEBECHET: Adjusting so level 2 is the highest level header per style guide, added boldmono around verbs where appropriate, added preformatted log2 markup around sample log - if another preformatted method is preferred, please change!

2023-01-31T17:13:34Z

Adjusting so level 2 is the highest level header per style guide, added boldmono around verbs where appropriate, added preformatted log2 markup around sample log - if another preformatted method is preferred, please change!

← Older revision		Revision as of 12:13, 31 January 2023
Line 1:		Line 1:
	{{official-document}}		{{official-document}}

	= House Event Criers =		== House Event Criers ==
	The HOUSE EVENT tool allows an Officer to create a unique crier, which can be sent throughout the world to announce an event. This is an especially useful tool for letting players know something is going on, even if they have not checked the calendar.		The {{boldmono\|HOUSE EVENT}} tool allows an Officer to create a unique crier, which can be sent throughout the world to announce an event. This is an especially useful tool for letting players know something is going on, even if they have not checked the calendar.

	== Crier Guidelines ==		== Crier Guidelines ==
	HOUSE EVENT submissions are due at least two weeks prior to the event. You are encouraged to submit them when you send your Event Support Request.		{{boldmono\|HOUSE EVENT}} submissions are due at least two weeks prior to the event. You are encouraged to submit them when you send your Event Support Request.

	Criers should always be in-character and must have perfect grammar and punctuation. Our goal with a crier is to announce an event, not to jar players out of their gaming experience or to annoy them. As such, criers do have some specific guidelines which they must meet before the CHE Controller can approve them for release.		Criers should always be in-character and must have perfect grammar and punctuation. Our goal with a crier is to announce an event, not to jar players out of their gaming experience or to annoy them. As such, criers do have some specific guidelines which they must meet before the CHE Controller can approve them for release.
Line 24:		Line 24:

	=== Usage ===		=== Usage ===
	Type HOUSE EVENT by itself to get usage information.		Type {{boldmono\|HOUSE EVENT}} by itself to get usage information.

	<nowiki>Usage:		<nowiki>Usage:
Line 49:		Line 49:
	Below is a sample entry with feedback messaging to see how it's done:		Below is a sample entry with feedback messaging to see how it's done:

	>house event create Party		<pre{{log2}}>>house event create Party

	Event message entitled "party" has been created.		Event message entitled "party" has been created.
Line 75:		Line 75:
	>house event status Party		>house event status Party

	The message has been submitted for approval, please check the status again at a later time.		The message has been submitted for approval, please check the status again at a later time.</pre>

	[[category:CHE]]		[[category:CHE]]

GS4-XYNWEN: Protected "CHE Officer Guide/Criers" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

2023-01-04T03:41:51Z

Protected "CHE Officer Guide/Criers" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

← Older revision	Revision as of 22:41, 3 January 2023
(No difference)

GS4-XYNWEN: /* Example */

2023-01-04T03:41:32Z

Example

← Older revision		Revision as of 22:41, 3 January 2023
Line 49:		Line 49:
	Below is a sample entry with feedback messaging to see how it's done:		Below is a sample entry with feedback messaging to see how it's done:

	~~<nowiki~~>house event create Party		>house event create Party

	Event message entitled "party" has been created.		Event message entitled "party" has been created.
Line 75:		Line 75:
	>house event status Party		>house event status Party

	The message has been submitted for approval, please check the status again at a later time.~~</nowki>~~		The message has been submitted for approval, please check the status again at a later time.

	[[category:CHE]]		[[category:CHE]]

GS4-XYNWEN: /* Example */

2023-01-04T03:41:12Z

Example

← Older revision		Revision as of 22:41, 3 January 2023
Line 49:		Line 49:
	Below is a sample entry with feedback messaging to see how it's done:		Below is a sample entry with feedback messaging to see how it's done:

	<nowiki> house event create Party		<nowiki>house event create Party

	Event message entitled "party" has been created.		Event message entitled "party" has been created.

GS4-XYNWEN: /* Example */

2023-01-04T03:40:54Z

Example

GS4-XYNWEN: /* Example */

2023-01-04T03:40:20Z

Example

← Older revision		Revision as of 22:40, 3 January 2023
Line 49:		Line 49:
	Below is a sample entry with feedback messaging to see how it's done:		Below is a sample entry with feedback messaging to see how it's done:

	<nowiki> house event create Party		<nowiki> house event create Party

	Event message entitled "party" has been created.		Event message entitled "party" has been created.
Line 75:		Line 75:
	G>house event status Party		G>house event status Party

	The message has been submitted for approval, please check the status again at a later time. </nowki>		The message has been submitted for approval, please check the status again at a later time.</nowki>

	[[category:CHE]]		[[category:CHE]]

GS4-XYNWEN: /* Example */

2023-01-04T03:39:56Z

Example

← Older revision		Revision as of 22:39, 3 January 2023
Line 49:		Line 49:
	Below is a sample entry with feedback messaging to see how it's done:		Below is a sample entry with feedback messaging to see how it's done:

	<nowiki> G>house event create Party		<nowiki> house event create Party

	Event message entitled "party" has been created.		Event message entitled "party" has been created.

GS4-XYNWEN: /* Example */

2023-01-04T03:39:39Z

Example

← Older revision		Revision as of 22:39, 3 January 2023
Line 49:		Line 49:
	Below is a sample entry with feedback messaging to see how it's done:		Below is a sample entry with feedback messaging to see how it's done:

	<nowiki>G>house event create Party		<nowiki> G>house event create Party

	Event message entitled "party" has been created.		Event message entitled "party" has been created.

GS4-XYNWEN: Created page with "{{official-document}} = House Event Criers = The HOUSE EVENT tool allows an Officer to create a unique crier, which can be sent throughout the world to announce an event. Th..."

2023-01-04T03:39:11Z

Created page with "{{official-document}} = House Event Criers = The HOUSE EVENT tool allows an Officer to create a unique crier, which can be sent throughout the world to announce an event. Th..."

New page

{{official-document}}

= House Event Criers =
The HOUSE EVENT tool allows an Officer to create a unique crier, which can be sent throughout the world to announce an event. This is an especially useful tool for letting players know something is going on, even if they have not checked the calendar.

== Crier Guidelines ==
HOUSE EVENT submissions are due at least two weeks prior to the event. You are encouraged to submit them when you send your Event Support Request.

Criers should always be in-character and must have perfect grammar and punctuation. Our goal with a crier is to announce an event, not to jar players out of their gaming experience or to annoy them. As such, criers do have some specific guidelines which they must meet before the CHE Controller can approve them for release.

# All criers must be in genre.
# All dates must be in Elanthian time (determined by CALENDAR CONVERT).
# All times must be fully spelled out (and in eastern time, 'elven' in game). Example: 10:00 P.M.
# There must be two spaces between each and every sentence.
# Follow standard English grammar. Common mistakes are subject-verb agreement, varying tenses, and either excessively long run-on sentences or sentences that are just phrases. Have a local grammar geek check your message or find a grammar checker online.
# Criers should be in the format of an actual crier. This means that you should write game appropriate messaging to announce the event, such as a herald arriving or a ghostly apparition drifting in. You may also use a disembodied voice, a whisper, or a shout.
# When choosing an area for the messaging, this is the town/realm that the message will be seen in. Worldwide messaging will not be approved unless you have rented a cross-realm room within Ebonstone Manor for the event. The messaging for worldwide criers must be very simple. Please refrain from submitting long dialogues. Worldwide messaging is available for outdoor settings only.
# When choosing a setting for the messaging (inside, outside or all rooms), please refrain from using physical embodiments that enter and leave an area for "all" or "inside" rooms. A voice, a shout, a whisper, a ghost, etc. are all fine. Feel free to be creative here without using a crowd of people to walk through someone’s private locker area, table or swimming pool to discuss your event.
# Avoid criers that tell people what they remember or what they saw at one time. A crier stating that I remembered seeing a note tacked up in Wehnimer's Landing means little to me if I've never been to Wehnimer's Landing.
# Criers that enter an area should also leave the area in their messaging and not just suddenly "be seen." Example: A uniformed Officer enters the area and states, "Blargh!" He then marches off.
# With criers that involve an ongoing dialog between two or more people, ensure that who is speaking is apparent. Having a bunch of ambiguous statements is confusing.
#* GOOD Example: A pair of miscreants enter the area. The first states, "You're horrible." The second responds, "No, you're horrible." As they depart, the first one replies back, "Whatever. Go eat an egg."
#* BAD Example: A pair of miscreants enter the area having a conversation. "You're horrible." "No, you're horrible." "Whatever. Go eat an egg."

=== Usage ===
Type HOUSE EVENT by itself to get usage information.

<nowiki>Usage:
HOUSE EVENT CREATE <title> - Create a new message
HOUSE EVENT MESSAGE <title> <message> - No <message> entry will return the
current message
HOUSE EVENT AREA <title> <town> - Set the towns to receive the message
HOUSE EVENT SETTING <title> <setting> - Controls whether message is sent to
inside, outside or all rooms
HOUSE EVENT REVIEW <title> - Display message, settings, and review
notes for <title>
HOUSE EVENT MEMBER <title> - Toggles the message displaying to members
of your organization only.
HOUSE EVENT STATUS <title> - GM QC approval for message
HOUSE EVENT LIST - List messages for your organization
HOUSE EVENT SUBMIT <title> - Submit message for QC
HOUSE EVENT UNSUBMIT <title> CONFIRM - Clear the message in order to change it
It must be re-submitted afterwards
HOUSE EVENT EXECUTE <title> - Let the message fly
HOUSE EVENT DELETE <title> - Delete an existing message
HOUSE EVENT EXAMPLES - Provides examples of proper message setup</nowiki>

=== Example ===
Below is a sample entry with feedback messaging to see how it's done:

<nowiki>G>house event create Party

Event message entitled "party" has been created.

G>house event message Party We're having a party tonight!

The text "We're having a party tonight!" has been saved for message "Party".

G>house event area Party Solhaven

Message "Party" is set to message Solhaven.

G>house event setting Party All

Event message party is now set to message all rooms.

G>house event submit Party

You must use CONFIRM to submit the message for review.

G>house event submit Party confirm

Event message Party has been submitted for review.

G>house event status Party

The message has been submitted for approval, please check the status again at a later time. </nowki>

[[category:CHE]]