Gswiki:Style guide/Verb pages

Verb pages are articles displaying information about commands used inside GemStone IV to navigate and manipulate the world. These commands are colloquially called verbs. A verb form is available with instructions and easy input for parameters to create or edit a verb page. This page offers instruction on how to manually create or edit a page with the GSWiki editor.

PLEASE NOTE: There are a multitude of existing verb pages that require updating to these new guidelines. If using the verb form to update these pages, please either move the page to the updated naming standard prior to editing the page, or enter the current page name into the form to populate the current contents, then move the page when edits are complete. Doing otherwise will create a new page, causing information duplication, and the page history will not properly transfer over.

Article Title

There are two ways to create a verb page. For instructions on manually creating a new wiki page, see the GSWiki Editing Guide. Alternatively, utilize the Verb form. The article title for the page should make use of the namespace Verb: followed by the name of the verb in all capital letters. There should be no space before or after the colon (ex. Verb:SNEEZE).

Page Setup

Verbinfo Template

The verbinfo template should be entered into the code editor first to ensure it appears in the top right corner of the article. This creates an informational sidebar for verb pages that details verb type (limited to Roleplaying, System, and Special case), as well as other information. By entering it in first, it eliminates weird spacing errors. Based on entries, the template will automatically categorize the verb and additionally assigns properties to values to assist with semantic query searches. The verb form allows editors an interface to enter parameters based on the template. If the form is used to edit a page that already exists with the verbinfo template, many of the parameters automatically populate.

Copy/Paste Code

Below is the copy and paste code to be entered for the sidebar template.

{{Verbinfo
|verb = VERB <!--Name of the verb.  This should always be capitalized. -->
|type = TYPE <!--Type of verb: Roleplaying, System, Special Case.  If multiple, enter each separated by a comma and no spaces. -->
|demeanor = YES <!-- Simply answer "Yes" if there are demeanor actions -->
|wedding = Yes <!--Simply answer "Yes" if there are wedding variations -->
|citizen = CITIZEN <!--If there is a citizen version of the verb.  If multiple, enter each separated by a comma and no spaces. -->
|race = RACE <!--If there is a racial version of the verb.  If multiple, enter each separated by a comma and no spaces. -->
|culture = CULTURE <!--If there is a cultural version of the verb.  If multiple, enter each separated by a comma and no spaces. -->
|profession = PROFESSION<!--If there is a profession version of the verb.  If multiple, enter each separated by a comma and no spaces. -->
|system = SYSTEM <!--If this verb is specific to a system.  If multiple, enter each separated by a comma and no spaces.-->
|special = SPECIAL <!--If this verb is due to a special case and does not work otherwise.  If multiple, enter each separated by a comma and no spaces. -->
}}

Introduction

An introductory sentence or paragraph should follow the template. This may include the definition of the verb, as well as notate what messaging may apply, which system it supports, or various other quick bits of information.

Example from Verb:ARMOR

ARMOR is a system verb that is part of the Player System Manager for Armor Specializations. It is only available to Warriors, Rogues, and Paladins.

Help

The first subsection that should be setup, if available, is "Help." Most verbs will have a help menu which may be accessed by entering (VERB) by itself, with (VERB) HELP, or with HELP (VERB) (this is the least likely used of the three options due to the HELP verb). When creating the section, ==Subheader 2== should be utilized, ex. ==Help==. Prior to entering the help menu information, while not required, please consider noting how the menu is accessed, and format it as: <small>'''''Note''' (how the help menu is accessed)''</small>. The help menu itself should be surrounded by <pre{{log2}}></pre> to retain formatting and indicate it is pulled directly from the game window, ex. <pre{{log2}}>Help menu</pre>. Additionally, some roleplaying verbs will display additional styles dependent on race, culture, or other variables that would be specific to the character who is viewing the information. This information should be captured on the verb page, but placed below the standard help text, separated based on type using ===Subheader 3===, using the same <pre{{log2}}></pre> formatting. For roleplaying verbs that may have an abundance of help styles (three or more) based on the additional parameters of race, culture, etc., please consider utilizing collapsed section as more detailed information can be found in the Verb Info section of the verb page.

Verb Info

The second subsection that should be setup, if available, is "Verb Info." This subsection is primarily used with roleplaying verbs and is populated with VERB INFO (VERB). This section of the verb page details a breakdown of the verb's variables and offers first person messaging. In some cases, it will also display additional second or third person messaging if there is a substantial difference in the returned text from the first person messaging.

When creating the section, ==Subheader 2== should be utilized, ex. ==Verb Info==, and the contents should be formatted using <pre{{log2}}>, similar to Help. While not required by the style guide, please consider utilizing the {{blue}} template and bold items that are "monsterbold" in game to ensure they stand out, ex. {{blue|People targets:}}. This small bit of formatting helps readers with understanding what is happening in the displayed text. Additionally, some roleplaying verbs will display additional styles dependent on race, culture, or other variables that would be specific to the character who is viewing the information. This information should be captured on the verb page, but placed below the standard verb info text, separated based on type using ===Subheader 3===, using the same formatting and labeling why specialized verb info exists.

Usage

The second subsection that should be setup, if available, is "Usage." When creating the section, ==Subheader 2== should be utilized, ex. ==Usage==. This subsection may be used for all verb types, and what is entered, along with formatting, is dependent on the verb type.

What is entered under the Usage subheader and how it is displayed is based on the verb type (roleplaying, system, or special case). There are some instances where a verb may fall under one, two, or all three types, depending on how it is used.

Roleplaying Verbs

Roleplaying verbs are verbs that are used to enhance the roleplaying environment, and may also be known as "emotes." They may have additional special messaging based on: demeanor, citizenship, race or culture, profession, and if two characters are married from a wedding package.

If the verb has variables that may be set, ie. separate messaging that may be set as the default instead of the standard messaging, it will be indicated in the help menu as (Verb) SET. This should be the first entry under Usage as a ===Subheader 3===, as well as use {{boldmono}} to indicate it is a command in game, ex. ==={{boldmono|SET}}===. There is no need to repeat the verb in the subheader as its use is already implied.

If a verb does not have "(Verb) SET" as an option, tables for messaging can be entered immediately following the Usage subheader. Otherwise, the tables will require a Messaging as a ===Subheader 3===, ex. ===Messaging===. If there is a significant amount of messaging, the tables themselves should be broken up based on any variables that may apply, such as standard messaging, targeted, untargeted, racial styles, cultural styles, etc., under their own ====Subheader 4====, ex. ====Erithian====. Otherwise, pages with simple messaging can utilize a single table to house it.

The below code is a general use for entering verb actions into the table. It is preformatted and modular, allowing for additional headers to be added as needed, including for a second person view when targeting an action. Headers, modifiers, and the second person view will not populate in the table if nothing is entered into them.

Example:

{{VerbTableStart |header1= Style |header2= Target|2Pview= Yes}}
{{VerbTableEntry|modifier1= Style |modifier2= Target |1Pview = 1st Person View |2Pview= Second Person View |3PView: 3rd Person View}}
{{Table end}}

Style	Target	First	Second	Third
Style	Target	This section has not been added yet; please add to it now!	This section has not been added yet; please add to it now!	This section has not been added yet; please add to it now!

For an example of how a roleplaying verb should be set up, please see: Verb:BOW.

System Verbs

System verbs are verbs with specific tie-ins to the various systems within GS. While not entirely mechanical in nature, many of them tie into game or character mechanics. Examples include Verb:ARMOR and Verb:ASSESS.

Most of these types of verbs will have a HELP menu with information. When creating a verb page, remember that a detailed explanation of how or why a verb is used and its mechanical implications would not be placed on the verb page. This kind of mechanics information should be on a separate article linked from the verb page. The verb page should only focus on information directly about the verb itself.

Unlike roleplaying verbs, most system verbs will not require a verb table to display messaging. However, each option should be set up under Usage with a breakdown of their use, and if warranted, an example. These should be done as ===Subheader 3===, as well as use {{boldmono}} to indicate it is a command in game, ex. ==={{boldmono|(VARIABLE)}}===. There is no need to repeat the verb in the subheader as its use is already implied.

For an example of how a system verb should be set up, please see: Verb:ARMOR.

Special Case Verbs

Special case verbs are verbs that are not directly tied to roleplaying or a system. In most cases, a special case verb is a verb that requires interaction with a target or for you to be in a specific room and will not work otherwise. They will not always have a full article, and should note in the verbinfo template what the particular case may be, if known. Unless otherwise noted, page setup will be similar to system verbs.

Additional Information

The Additional Information subsection, if applicable, offers additional information to supplement the verb article and should be entered as ==Subheader 2==, ex. ==Additional Information==. If there are external links, they should be listed under ==Resources==, and would include links to definitions. If there are internal links, they should be listed under ==See Also==, and may include links to other similar verbs articles that pertain to certain variables of the verb.

Form & Templates

Form for verb page creation or editing:

• Verb form

Primary templates used with verbs are:

• Verbinfo
• VerbTableStart
• VerbTableEntry
• Table end
• Log2