Toggle menu
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

Crew:Editor Guide

From Menhirs Fate Wiki
Revision as of 10:47, 15 March 2026 by Menhir wiki admin (talk | contribs) (Add BuildPage template documentation for funded builds)

This guide explains how to make changes to the Menhirs Fate Wiki as an Editor. Your edits are saved immediately but won't be visible to the public until you approve them, giving you a chance to draft, review, and publish when ready.

The Basics

As an Editor, you have a simple workflow:

  1. Edit a page - your changes are saved but stay private
  2. Review what you've changed
  3. Approve when you're happy, the page goes live to all players

The public always sees the last approved version. You can make as many edits as you like before approving.

How to Edit a Page

Step 1: Find the page you want to change

Use the search bar in the top-right corner, or navigate through the menu. Every page on the wiki has an Edit button near the top.

Step 2: Click Edit

You'll see two options when you click the pencil icon:

  • Edit - opens the Visual Editor, a rich-text editor that works like a word processor. This is recommended for most edits.
  • Edit source - opens the raw wikitext. Use this for advanced formatting or template work.

Step 3: Make your changes

In the Visual Editor, you can:

  • Type and format text (bold, italic, headings) using the toolbar
  • Insert links to other wiki pages by highlighting text and clicking the chain icon
  • Insert images via Insert → Media
  • Insert templates (like SkillCard or CreatureCard) via Insert → Template

Step 4: Save your edit

Click the Save changes button (or Publish changes depending on your editor). Add a short summary of what you changed, this helps other editors understand the history.

Your edit is now saved, but it is NOT yet visible to the public. The page still shows the previous approved version to players and logged-out visitors.

How to Approve Your Changes

Once you've made your edits and you're happy with them, you need to approve the revision to make it public.

Option A: From the page itself

After saving an edit, reload the page. You'll see a green banner near the top of the page:

This revision is not yet approved. [Approve Rev XXXX]

  1. Click the green Approve Rev button in the banner
  2. A confirmation dialog will appear — click OK
  3. The page will reload showing the approved version, now live to all players

You can also find Approve in the More menu (the three dots at the top right of any page).

Option B: From the page history

  1. Click View history at the top of any page
  2. Find the revision you want to approve
  3. Click on the revision date to view it
  4. Click the green Approve Rev button in the banner at the top, or use Approve from the More (⋮) menu

How to Check What's Pending

Visit Special:ApprovedRevs to see:

  • Pages whose approved revision is not their latest - these have unapproved edits waiting
  • All pages with an approved revision - everything that's been approved at least once
  • Unapproved pages - pages that have never been approved (new pages)

This is your dashboard for managing what goes live.

Creating a New Page

To create a brand new page:

  1. In the search bar, type the name of the page you want to create
  2. If it doesn't exist, you'll see a red link, click it
  3. Edit the page as normal and save

New pages are visible to the public immediately until they receive their first approval. Once you approve a revision, the approval workflow kicks in for all future edits.

Tip: To keep a new page private while you draft it, create it in the Crew: namespace instead (e.g. Crew:Draft New Rules), then move it to the main namespace when it's ready.

Creating Pages in the Crew Namespace

The Crew: namespace is private — only Editors, Volunteers, and Admins can see it. Regular users and logged-out visitors cannot access these pages at all.

To create a Crew page, simply prefix the page name with Crew: — for example:

  • Crew:Monster Manual
  • Crew:Plot Hooks for Event 3
  • Crew:NPC Stat Blocks

You can navigate to the Crew Wiki landing page at Crew:Main Page.

Using the SkillCard Template

The SkillCard template creates styled cards for skills, rites, spells, cantrips, ceremonies, and abilities. Each card name automatically appears in the page's Table of Contents.

Basic Usage

At minimum, a SkillCard needs a name and an effect:

{{SkillCard
|name=Toughness
|xp=1XP (+1XP per level)
|effect=Adds one base hit point per level.
}}

Sphere Colours

The sphere parameter adds colour-coded headers to visually group skills by type. If omitted, the card uses the default parchment brown.

Sphere Colour Used For
Air Gold/Yellow Air rites and spells
Earth Green Earth rites and spells
Fire Orange/Red Fire rites and spells
Water Blue Water rites and spells
Spirit Purple Athria rites, faith skills, ceremonies
Vigour Red Vigour skills and abilities
Focus Dark Blue Magical skills (Mage, Extra Focus, etc.)
(omitted) Brown Default for general skills, calls, etc.

Example with a sphere:

{{SkillCard
|name=Precision Strike
|sphere=Vigour
|level=2
|restriction=Weapon Master
|recharge=1/encounter
|effect=Crush or Rend (depending on your weapon physrep) on torso hit only.
}}

All SkillCard Parameters

Parameter Description Example
name Required. The name of the skill/spell/rite. Fireball
sphere Colour-coded header. See table above. Fire
level Displays as "Lvl X" in the header badge. 2
xp XP cost, displayed in the header badge. 3xp
cast_time How long the rite or spell takes to cast. 2 minutes
fp_cost Focus Point cost for cantrip spells. 1
cost Resource cost (flickers, faith, vigour, etc.). 1 Fire Flicker
type The type of ability. Ceremony – 1 min
restriction Usage restriction or skill tree. Weapon Master
target Who the ability targets. Self
duration How long the effect lasts. 5 minutes
recharge How the ability recharges. 1/encounter
threshold Minimum threshold needed to unlock. 2
extension How flickers extend the rite. Shown in italics. Each Flicker adds 1 minute
range Range of the ability. 10 metres
effect Required. Full description of what the skill does. (free text)
vocals Spell vocals. By the element of Fire...
note Optional note, shown in italics. Arrows only

All parameters except name and effect are optional — the card automatically hides rows for any field you leave out.

SkillCard Examples by Type

A rite with sphere colour and extension:

{{SkillCard
|name=Feast of Flesh
|sphere=Spirit
|level=2
|cast_time=1 minute
|duration=5 minutes
|range=Touch through foci
|extension=Every Flicker of Spirit expended in the rite increases the duration by 5 minutes
|effect=The Weaver may choose a willing target who is currently in their terminal state...
}}

A vigour skill tree ability:

{{SkillCard
|name=Catch Breath
|sphere=Vigour
|level=1
|restriction=Weapon Master
|recharge=1/encounter
|effect=When a nearby ally (within 5m) enters critical state, call Stagger twice on the next 2 hits or shield blocks.
}}

A purchased ceremony with threshold:

{{SkillCard
|name=Spiritual Reading
|sphere=Spirit
|xp=2xp
|threshold=1
|effect=You may use 1 minute of roleplay with a willing target to detect the presence of Curses or other spiritual afflictions.
}}

A call (no sphere, default brown):

{{SkillCard
|name=Crush
|duration=10 seconds
|effect=Target cannot use the struck limb for 10 seconds. Weapon strikes do 0 damage but still trigger this effect.
}}

A cantrip spell:

{{SkillCard
|name=Burning Taunt
|sphere=Fire
|fp_cost=1
|target=Other
|duration=10 seconds
|effect=The target is compelled to focus their attacks on the caster.
|vocals=By the element of Fire / I ignite your fury / Burning Taunt
}}

Inserting a SkillCard via the Visual Editor

  1. Place your cursor where you want the card
  2. Click Insert → Template
  3. Search for "SkillCard"
  4. Fill in the fields — the form shows all available parameters with descriptions
  5. Click Insert

You can edit an existing SkillCard by clicking on it in the Visual Editor and selecting the pencil icon.

Using the CreatureCard Template

The CreatureCard template creates styled stat blocks for NPCs and monsters, primarily used in the Beastiary. Like SkillCards, each creature name appears in the Table of Contents.

Note: CreatureCards are typically used in the Crew: namespace, since monster stats are usually crew-only information.

Basic Usage

At minimum, a CreatureCard needs a name:

{{CreatureCard
|name=Forest Wisp
|rank=Grunt
|hp=3
|weapons=Claws (short sword)
|skills=
* '''Fade''' – May call Refuge once per encounter
|description=A faint, glowing spirit drawn to areas of strong ambient magic.
}}

Rank Colours

The rank parameter determines the header colour, helping crew quickly identify threat level at a glance:

Rank Colour Typical Use
Grunt Dark Grey Basic monsters, low-threat NPCs
Leader Dark Blue Pack leaders, minor named NPCs
Elite Dark Purple Powerful monsters, significant threats
Boss Dark Red Event bosses, major encounters
Divine Dark Gold Divine beings, world-level threats
(omitted) Brown Default, for unranked creatures

All CreatureCard Parameters

Parameter Description Example
name Required. The creature's name. Vampire Thrall
rank Threat level. Sets header colour. Elite
subtitle Subtype or flavour label under the name. Undead – Vampire
hp Hit points. 10
armour Armour type or description. Heavy
weapons Weapons the creature uses (for phys-rep). Two short swords
soul_type Soul classification. Aberrated
vulnerability Weaknesses or special damage modifiers. Fire damage +1
shield Elemental shield details. Fire 4, Water 5
focus Focus pool amount. 6
skills Abilities and skills. Supports full wikitext. (see examples)
description Lore and flavour text. (free text)
note Crew/referee notes. Shown in italics. Spawns 2 Grunts on death

CreatureCard Examples

A boss-rank creature:

{{CreatureCard
|name=The Hollow King
|rank=Boss
|subtitle=Undead Sovereign
|hp=25
|armour=Heavy
|weapons=Great sword, shield
|soul_type=Aberrated
|vulnerability=Spirit rites deal double damage
|skills=
* '''Sovereign Command''' – Call Mass Stun once per encounter
* '''Unholy Resilience''' – Resist any one call per encounter
* '''Raise Dead''' – Summon 2 Grunt-rank Hollow Soldiers (5HP each)
|description=An ancient king who refused to pass on, sustained by dark pacts.
|note=Requires minimum 10 players for encounter balance. Brief before sending.
}}

A simple grunt:

{{CreatureCard
|name=Hollow Soldier
|rank=Grunt
|hp=5
|weapons=Sword and shield
|skills=
* '''Shambling''' – Cannot run, always walks
|description=Animated remains of fallen soldiers, bound to serve the Hollow King.
}}

Inserting a CreatureCard via the Visual Editor

  1. Place your cursor where you want the stat block
  2. Click Insert → Template
  3. Search for "CreatureCard"
  4. Fill in the fields, start with name and rank, then add stats
  5. Click Insert

Tips for Beastiary Pages

  • Group creatures by type or encounter, use section headings (e.g. == Undead ==) above your CreatureCards
  • Use the note field for crew briefing info like encounter balance or special instructions
  • The skills field supports full wikitext, use bullet points with bold ability names for consistency:
|skills=
* '''Ability Name''' – Description of what it does
* '''Another Ability''' – Another description

Using the BuildPage Template

The BuildPage template creates styled pages for Bankers Guild Funded Builds. It gives every build a consistent look with a subtitle, flavour quote, lore text, build details table, and a contributions table showing who funded the project.

All funded build pages live under: Bankers Guild Builds/Funded Builds/Nation/Build Name

Basic Usage

At minimum, a BuildPage needs lore text and a nation:

{{BuildPage
|subtitle=A Hearth of Warmth and Sweet Delights
|quote=Where the oven glows like the moon and each bite carries the sweetness of the stars.
|lore=
Nestled within the winding lanes of Embermount, the '''Starlight Bakery''' now stands...

(Write your full lore description here. You can use '''bold''' and ''italic'' wikitext as normal.)
|cost=5 Legends · 3 Myths · 9 Saga
|location=AVEREAUX - EMBERMOUNT
|build_code=BG.MRS.09
|contributions=
{{!}} Bankers Guild {{!}}{{!}} Valdraeth {{!}}{{!}} 1 Legend, 5 Myths, 5 Sagas
{{!}}-
{{!}} Avereaux Nation {{!}}{{!}} National Support Fund {{!}}{{!}} 3 Myths
|balance=PAID IN FULL
|nation=Avereaux
}}

All BuildPage Parameters

Parameter Description Required?
subtitle A short flavour subtitle displayed in gold below the page title. No
quote An italicised flavour quote, displayed with decorative curly quotes. No
lore The main body text describing the build. Supports full wikitext (bold, italic, links, etc.). Yes
cost ) here — they will break the template. No
location Where the build is located, typically in ALL CAPS by convention. No
build_code The unique Bankers Guild build code (e.g. BG.MRS.09). Displayed in a monospace badge. No
contributions The contributions table rows. See the section below for formatting. No
balance The remaining balance (e.g. PAID IN FULL or 6 Legend). Displayed in gold in the table footer. No
nation The nation this build belongs to. Used to auto-categorise the page (e.g. Avereaux, Hammerstadt, Valdraeth). Yes

How to Format Contributions

The contributions table uses wiki table syntax inside the template. Because you're inside a template, you must use {{!}} instead of the normal pipe character (|).

Each row has three columns: Contributor, Source, and Amount.

Single row:

|contributions=
{{!}} Character Name {{!}}{{!}} Nation {{!}}{{!}} 2 Myths, 5 Sagas

Multiple rows (separate with {{!}}-):

|contributions=
{{!}} Bankers Guild {{!}}{{!}} Bankers Guild {{!}}{{!}} 6 Legends, 12 Myths
{{!}}-
{{!}} Hendrik Smeets {{!}}{{!}} Hammerstadt {{!}}{{!}} 1 Myth
{{!}}-
{{!}} Hieronymous Sweetsmith {{!}}{{!}} Hammerstadt {{!}}{{!}} 15 Myths

The template automatically adds the header row (Contributor / Source / Amount) and the Remaining Balance footer — you only need to provide the data rows.

Page Naming Convention

All funded build pages follow this path structure:

Bankers Guild Builds/Funded Builds/Nation/Build Name

For example:

  • Bankers Guild Builds/Funded Builds/Avereaux/The Starlight Bakery
  • Bankers Guild Builds/Funded Builds/Hammerstadt/Temple of Endless Echoes
  • Bankers Guild Builds/Funded Builds/Valdraeth/Unicorns Rest

The template automatically adds the page to three categories: the nation category, Funded Builds, and Bankers Guild Builds.

Creating a New Funded Build

  1. Navigate to the new page path (e.g. search for Bankers Guild Builds/Funded Builds/Avereaux/My New Build and click the red link)
  2. Switch to Edit source mode (the BuildPage template is easier to work with in source mode)
  3. Paste the template skeleton below and fill in the fields:
{{BuildPage
|subtitle=
|quote=
|lore=

|cost=
|location=
|build_code=
|contributions=
{{!}} Contributor Name {{!}}{{!}} Source {{!}}{{!}} Amount
|balance=
|nation=
}}
  1. Save your edit and review the page
  2. Approve the revision when you're happy with it

Inserting a BuildPage via the Visual Editor

  1. Place your cursor at the top of the page
  2. Click Insert → Template
  3. Search for "BuildPage"
  4. Fill in the fields in the form
  5. Click Insert

Note: The contributions field is easier to write in source mode due to the table syntax. You can insert the template via the Visual Editor for all other fields, then switch to source mode to add the contribution rows.

Quick Reference

Task How
Edit a page Click the pencil icon → Edit
Save (without going live) Click "Save changes" — it stays private
Approve (push live) View latest revision → "Approve this revision"
See what's pending Special:ApprovedRevs
Create a private draft Create in the Crew: namespace
Insert a SkillCard Insert → Template → SkillCard
Insert a CreatureCard Insert → Template → CreatureCard
Insert a BuildPage Insert → Template → BuildPage
Upload an image Special:Upload or Insert → Media
Make an image responsive Wrap in <div class="responsive-img">...</div>

Tips

  • Preview before saving - use "Show preview" in the source editor, or just review your changes in the Visual Editor before saving.
  • Write edit summaries - a few words about what you changed helps everyone understand the page history.
  • Don't worry about breaking things - your edits aren't public until you approve them. If something looks wrong, just edit again before approving.
  • Use the Visual Editor for templates - it gives you a form with labelled fields, which is much easier than writing template code by hand.
  • Use sphere colours consistently - if a skill belongs to a sphere or skill type, always include the sphere parameter so it matches the rest of the wiki.
  • Check existing pages for examples - look at Rules/Vigour Skills, Rules/Faith Skills, or Rules/Magical Skills to see how SkillCards are used in practice.