Gswiki:Style guide/Spells: Difference between revisions

The official GemStone IV encyclopedia.
< Gswiki:Style guide
Jump to navigation Jump to search
No edit summary
m (VANKRASN39 moved page Help:Style (spells) to Help:Spells: makes sense)
(8 intermediate revisions by 4 users not shown)
Line 1: Line 1:
All spell entries are required to include a spell template inclusion at the top of the article. Additionally, all spell entries should include one or more the following:
All spell entries are required to include a spell template inclusion at the top of the article. Additionally, all spell entries should include one or more the following in order:


* a blurb about the spell, describing its visual effects in simple english.
* A blurb about the spell, describing its visual effects in plain English. The intro should also include base bonuses conferred, when the spell is used if situational, and any other key effects of the spell, and maybe a short summary of any other factors that will be described later in detail.
* Low level profession circle spells, and any other odd usage spells, should have a '''Usage''' section describing how to cast the spell. For spells with multiple uses (see [[Web (118)]]), usage can be integrated into each version of the spell's section.
* a sub-section named '''Factors that affect <spell name>''' listing what skills, lores, attributes, etc. factor into and in what manner they do so.
* One of the key uses of the Wiki is for people to learn how to train to increase the effectiveness of a spell. Thus, there should be a '''Mana Control Benefit(s)''' section and a '''Lore Benefit(s)''' section if applicable. Other skills/stats, such as Spell Aiming/Dexterity for bolts, should go in the intro, or if there are a lot of unusual factors, the Mana Control and Lore Benefits should be subheaders under a larger section. Each Mana Control and Lore Benefits section should have a training chart showing thresholds and benefits, if possible. If there are a lot of thresholds, create a progressive chart of thresholds that make sense and indicate that not all thresholds are shown (see [[Web (118)#Chance to Ensnare Target]]). '''All Mana Control and Lore benefits should also be added to the respective page for that skill.''' If [[skill bonus]] is used in thresholds or equations, the training threshold chart should convert the skill bonus to ranks.
* an '''Effects''' section describing the mechanical effects of the spell, such as bonuses confered. This section is expected in defense and utility spell articles.
* A '''Messaging''' section showing the in-game text when the spell is cast and when its effect expires (if applicable). Spells that have specific messaging for every single deity should have one example (or a summarized example) on the spell page and a link to the application section of the [[deity messaging]] page (see [[Prayer (313)#Messaging]] for example).
* a '''Using <spell name>''' section, describing how the spell is used and the mechanics underlying its effects. This spell is expected in attack and utility spell articles.
* If there are any '''alchemy recipes''' that directly cast the spell or make a key component (e.g. chalk for 740), the recipe should be added in via transclusion (see [[Unlock (407)]] for an example with 1 recipe, or [[Elemental Blast (409)]] for an example with 2 recipes), otherwise a link to the related recipe is fine.
* A '''Resources''' section listing any guides, saved posts page(s), and links to the official spell description, if applicable. As of this writing in October 2015, there are several spells without an official spell description (see [[Grasp of the Grave (709)]]). How helpful the release posts are is really dependent on the overseeing [[GameMaster]].

Other important information for spell pages:
*'''When a spell is rewritten''', the spell page edit should be approached as a rewrite and '''every section and linked page should be looked over'''. This includes changes to success determination, addition or subtraction of applicable skills, etc. When the release post is copied and pasted into the article text and the existing information is not read over and edited, information that is not applicable anymore remains in the article, and the article does not read like an article. Besides the obvious links in the article text, see the "What links here" link on the bottom left of the sidebar on every page for a full list of pages that link to the article.
*'''When a spell is no longer implemented''', the spell page should be marked deprecated and all links to the page should be reviewed and updated if needed (e.g. [[Spell Store (502)]]).


== The Spell Template ==
== The Spell Template ==
Line 11: Line 17:
For example, this would be the spell template for [[Minor Shock (901)]]:
For example, this would be the spell template for [[Minor Shock (901)]]:


<nowiki>{{spell | name = Minor Shock | number = 901 | mnemonic = MINORSHOCK | duration = Instantaneous | type = Attack ([[bolt]]) }}</nowiki>
<nowiki>{{spell | mnemonic = MINORSHOCK | duration = Instantaneous | type = Attack }}</nowiki>


Which results in the following table being added to the article page:
Which results in the following table being added to the article page:


{| style="margin-left: 20px; margin-bottom: 5px;"
{| style="width: 23em; margin: 10px 0 10px 10px; clear:both;"
|-
|-
|
|
{| style="width: 100%; font-size: 95%; text-align: left; background: #FFF; margin: 0 0 0 0; border: 1px #aaa solid;"
{| {{prettytable}}
|+ style="white-space: nowrap; font-size: larger; text-align: left;" | '''Minor Shock (901)'''
! colspan=2 style="background:#DDD; font-size: larger; text-align: center;" | '''Minor Shock (901)'''
|-
|-
! Mnemonic
|
{| style="width: 23em; font-size: 95%; text-align: left;"
| valign="top" style="white-space: nowrap; text-align: right;" | [MINORSHOCK]
|-
|-
! Duration
! Mnemonic
| valign="top" style="white-space: nowrap;" | [MINORSHOCK]
| valign="top" style="white-space: nowrap; text-align: right;" | Instantaneous
|-
|-
! Type
! Duration
| valign="top" style="white-space: nowrap;" | Instantaneous
| valign="top" style="white-space: nowrap; text-align: right;" | Attack
|-
|}
! Type
| valign="top" style="white-space: nowrap;" | Attack ([[bolt]])
|-
|}
|}
|}
|}


This table will float along the right-hand side of the article, and article content will attempt to flow around it as best as possible. Please keep this in mind when writing articles and preview articles before saving to make sure the table flows well with the rest of the article's content.
This table will float along the right-hand side of the article, and article content will attempt to flow around it as best as possible. Please keep this in mind when writing articles and preview articles before saving to make sure the table flows well with the rest of the article's content.


The template inclusion should be kept as a single line as illustrated above, unless the spell has a particularily long or complex duration, in which case an inclusion in the following form is prefered:
The template inclusion should be kept as a single line as illustrated above, unless the spell has a particularly long or complex duration, in which case an inclusion in the following form is preferred:


<nowiki>
<nowiki>{{spell
| mnemonic = MSUMMON
{{spell |
| base_dur = 600 sec
| name = Minor Summoning
| add_dur = +20 sec per [[Sorcerer Base|rank]] <br>+30 sec per [[Sorcerous Lore, Demonology|Demonology]] rank
| number = 725
| span = [[Refreshable]]
| mnemonic = MSUMMON
| type = Utility
| duration = 600 sec <br/> + 20 sec per [[Sorcerer Base]] spell ranks <br/> + 30 sec per [[Sorcerous Lore, Demonology]] rank
}}</nowiki>
| type = Utility }}
</nowiki>


Take note of the inclusion of the <nowiki><br/></nowiki> HTML tag for line-breaks in the duration. This keeps the width of the table at a minimum and makes the duration more readable at the same time.

* Name should be in capital case, as all spell names are proper nouns.
* Number is the spell's number.
* Mnemonic should be typed in all capital letters.
* Mnemonic should be typed in all capital letters.
* Duration should be one of the following: ''instantaneous'', ''permenant'', ''special'' or the duration formula.
* Duration should be one of the following: ''instantaneous'', ''permanent'', ''special'' or the duration formula.
** Time units should be abbreviated as follows: ''sec'' (seconds), ''min'' (minutes), ''hr'' (hours)
** Time units should be abbreviated as follows: ''sec'' (seconds), ''min'' (minutes), ''hr'' (hours)
* Type should be a combination of any of the following as appropriate: ''attack'', ''defense'' or ''utility''.
* Type should be any of the following, as appropriate: ''attack'', ''defense'', ''offense'', or ''utility''.
** Attack type should include a internally linked sub-type in parentheses. The list of sub-types includes but is not limited to: ''[[bolt]]'', ''[[warding]]'' and ''[[maneuver]]''.
** Attack type should include an internally linked sub-type. The list of sub-types includes but is not limited to: ''[[bolt]]'', ''[[warding]]'' and ''[[maneuver]]''.

=== Advanced Functions ===
The spell template has many, many more functions than those listed here. For more information, see '''[[Template:Spell]]'''.

[[Category: Help]]

Revision as of 20:31, 20 February 2017

All spell entries are required to include a spell template inclusion at the top of the article. Additionally, all spell entries should include one or more the following in order:

  • A blurb about the spell, describing its visual effects in plain English. The intro should also include base bonuses conferred, when the spell is used if situational, and any other key effects of the spell, and maybe a short summary of any other factors that will be described later in detail.
  • Low level profession circle spells, and any other odd usage spells, should have a Usage section describing how to cast the spell. For spells with multiple uses (see Web (118)), usage can be integrated into each version of the spell's section.
  • One of the key uses of the Wiki is for people to learn how to train to increase the effectiveness of a spell. Thus, there should be a Mana Control Benefit(s) section and a Lore Benefit(s) section if applicable. Other skills/stats, such as Spell Aiming/Dexterity for bolts, should go in the intro, or if there are a lot of unusual factors, the Mana Control and Lore Benefits should be subheaders under a larger section. Each Mana Control and Lore Benefits section should have a training chart showing thresholds and benefits, if possible. If there are a lot of thresholds, create a progressive chart of thresholds that make sense and indicate that not all thresholds are shown (see Web (118)#Chance to Ensnare Target). All Mana Control and Lore benefits should also be added to the respective page for that skill. If skill bonus is used in thresholds or equations, the training threshold chart should convert the skill bonus to ranks.
  • A Messaging section showing the in-game text when the spell is cast and when its effect expires (if applicable). Spells that have specific messaging for every single deity should have one example (or a summarized example) on the spell page and a link to the application section of the deity messaging page (see Prayer (313)#Messaging for example).
  • If there are any alchemy recipes that directly cast the spell or make a key component (e.g. chalk for 740), the recipe should be added in via transclusion (see Unlock (407) for an example with 1 recipe, or Elemental Blast (409) for an example with 2 recipes), otherwise a link to the related recipe is fine.
  • A Resources section listing any guides, saved posts page(s), and links to the official spell description, if applicable. As of this writing in October 2015, there are several spells without an official spell description (see Grasp of the Grave (709)). How helpful the release posts are is really dependent on the overseeing GameMaster.

Other important information for spell pages:

  • When a spell is rewritten, the spell page edit should be approached as a rewrite and every section and linked page should be looked over. This includes changes to success determination, addition or subtraction of applicable skills, etc. When the release post is copied and pasted into the article text and the existing information is not read over and edited, information that is not applicable anymore remains in the article, and the article does not read like an article. Besides the obvious links in the article text, see the "What links here" link on the bottom left of the sidebar on every page for a full list of pages that link to the article.
  • When a spell is no longer implemented, the spell page should be marked deprecated and all links to the page should be reviewed and updated if needed (e.g. Spell Store (502)).

The Spell Template

Each spell entry should begin with a spell template inclusion.

For example, this would be the spell template for Minor Shock (901):

{{spell | mnemonic = MINORSHOCK | duration = Instantaneous | type = Attack }}

Which results in the following table being added to the article page:

Minor Shock (901)
Mnemonic [MINORSHOCK]
Duration Instantaneous
Type Attack

This table will float along the right-hand side of the article, and article content will attempt to flow around it as best as possible. Please keep this in mind when writing articles and preview articles before saving to make sure the table flows well with the rest of the article's content.

The template inclusion should be kept as a single line as illustrated above, unless the spell has a particularly long or complex duration, in which case an inclusion in the following form is preferred:

{{spell
  | mnemonic = MSUMMON
  | base_dur = 600 sec 
  | add_dur = +20 sec per [[Sorcerer Base|rank]] <br>+30 sec per [[Sorcerous Lore, Demonology|Demonology]] rank
  | span = [[Refreshable]]
  | type = Utility
 }}
  • Mnemonic should be typed in all capital letters.
  • Duration should be one of the following: instantaneous, permanent, special or the duration formula.
    • Time units should be abbreviated as follows: sec (seconds), min (minutes), hr (hours)
  • Type should be any of the following, as appropriate: attack, defense, offense, or utility.
    • Attack type should include an internally linked sub-type. The list of sub-types includes but is not limited to: bolt, warding and maneuver.

Advanced Functions

The spell template has many, many more functions than those listed here. For more information, see Template:Spell.