Kamisekai

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Style Guide ======

Use this when writing moves for yourself, or for the system.

===== Bestiary ===

<code>
==== Monster Name ====

**HP:** \\
**Armor:** \\
**Strength:** \\
**Weakness:** \\
**Appearance:** <Visual appearances>\\
**Weapons:** 
  * <Weapon Name> (<Weapon damage details>) - <Weapon details>
**Moves:**
  * <Move Name> - <Move description>

<Flavor texts>
</code>

===== Moves =====

==== Move Template ==

<code>
===== <Move Name> =====
<Move general concept>\\
<Player execution instructions>. <Roll instructions>.
**<Roll Result>:** <Roll action>
**<Roll Result>:** <Roll action>

<Move errata>

__**Perks**__
<Perks, see: perk layout>
</code>

==== Move Names ====

  * No more than two words, or no more than three with a simple conjunction word.
  * Non-conjunction words capitalized like proper nouns.
  * Should not collide with a perk, or other move (for search-ability.)
  * Should not contain system terms (for search-ability.)

==== Move Concepts ====

  * Don't prescribe lore.
  * Describe **what** is done, not **how** it is accomplished.

==== Player execution instructions ====

  * Short and to the point.
  * Contain if applicable:
    * Targeting
    * Range
    * Choice selection
    * Elemental or other selection requirements
    * Conditional logic
    * Target eligibility
  * Do not contain:
    * Descriptions of move effects
    * Lore of any kind
    * Roll instructions

==== Roll Instructions ====

  * Typically are just as simple as: Roll+Charm.
  * Capitalize stat names and roll.
  * No space between Roll, + or Stat.

Roll instructions may be prefixed with conditional logic, and placed onto their own line. For example:
<code>
===== Super Cool Move ====
Do a really cool thing!
Name a target to do the cool thing to and...
**One target:**
**Two targets:** Roll+Charm-Number of Targets.
</code>


==== Roll Results ====

Roll results should be listed in order of best to worst when applicable. It is acceptable to break up results with choice lists when necessary. Results are always written as either single numbers or inclusive numeric ranges. Numbers should be from low to high when written as a range (7-9 not 9-7).

When writing results where the number may exceed X, write X+. Do the same for X and below (6- not '<6' or '6 or less'.)

==== Choice Lists ====

Some moves may call for choice lists, such as selecting an action to take or effect to apply. It may be desirable to put choice lists before or after the roll results and effects depend on a few conditions and desired reading.

  * Choice lists **after** roll effects if:
    * The roll results in a player having **holds** to use at their discretion
    * The choices are not likely to influence the GM's application of consequences based upon actions they took. (For example; targeting an enemy with a heal spell or hitting an ally with a debuff.)
  * Choice lists **before** roll effects if:
    * The consequences are likely to be influenced by the action the player was attempting.
    * The player execution instructions tell the player to choose an option before making the roll.
    * The imperfect roll results in requiring another choice list.

**Player Action** choice lists should feature **names** for quick reference if the effects are very different or especially verbose. Spell like moves that have complicated effects benefit the most from this. They should be formatted as follows:

<code>
  * **<Choice Name>:** <Effect description>
  * **<Choice Name>:** <Effect description>
</code>

However, for **consequences and drawbacks** or when the effects are simple, the following is acceptable:

<code>
  * <Choice>
  * <Choice>
</code>