V Rising Wiki:Style guide

This style guide keeps articles predictable: a reader who has seen one boss page knows where to find the loot table on every boss page. When in doubt, copy the structure of a well-maintained article of the same type. Propose changes on the talk page.

Shortcut: VRW:STYLE

Universal article layout

Every article follows this sequence (omit sections that don't apply — never reorder):

1. Hatnotes (disambiguation, "For X, see Y")
2. Maintenance banners ({{Stub}}, {{Outdated}})
3. Infobox
4. Intro — one or two sentences stating what the subject is, with the article title in bold
5. Body sections (per page type, below)
6. See also
7. Notes / References
8. Update history
9. Navbox
10. Categories

Page-type layouts

Boss (V Blood carrier)

1. Infobox ({{Boss Infobox}}) — level, location, unlocks
2. Intro with in-game journal quote
3. Location
4. Attacks — with a Brutal difficulty subsection where behavior differs
5. Strategy — situational advice, not prescriptive loadouts; long walkthroughs belong in a Guide page, linked with Main article:
6. Rewards — Spells, then Structures/Recipes, then a sortable loot table with drop percentages
7. Quotes
8. Trivia
9. Update history
10. V Blood navbox

Weapon / equipment

1. Infobox ({{WeaponInfobox}} / {{EquipmentInfobox}})
2. Intro
3. Obtaining — crafting recipe (costs via {{ItemFrame}}), drops, vendors
4. Usage / stats — per-tier comparison table where applicable
5. Notes — interactions and edge cases (what stacks, what doesn't)
6. Update history
7. Type navbox ({{Navbox Weapons}})

Ability / spell

1. Infobox ({{AbilityInfobox}}) — school, cooldown, unlock source
2. Intro
3. Effect — per-tier/jewel values
4. Notes — interactions (explicit "stacks with / does not stack with" lists)
5. Update history
6. School navbox

Item / consumable

1. Infobox ({{ItemInfobox}})
2. Intro
3. Obtaining
4. Usage — organized by what it's used for (recipes, quests, refinement), one subsection each
5. Update history
6. Navbox

Structure (castle object)

1. Infobox ({{StructureInfobox}})
2. Intro
3. Obtaining / unlock
4. Usage — what it crafts/refines, with recipe tables
5. Update history
6. Navbox

Location

1. Infobox — region, level range, notable drops
2. Intro
3. Inhabitants — enemies and V Blood carriers, grouped by spawn condition
4. Resources
5. Points of interest
6. Update history
7. Region navbox

Game mechanic

1. Quick-reference facts box at top where useful
2. Intro definition
3. Body ordered by graduated complexity: overview → practical use → exact numbers/formulas; put a small summary table before any dense reference table
4. Update history

Patch

See Template:Patch documentation: infobox, then Additions / Changes / Fixes / Hotfixes.

Guide

Long-form walkthroughs and build advice live in guide pages ("Guide:" prefix), not in reference articles. Mark superseded guides prominently: "Outdated as of Patch X". Reference articles link to guides; guides link back to reference articles for numbers.

Standard sections

Brutal difficulty

Differences on Brutal servers go in a labeled Brutal difficulty subsection of the relevant section — never scattered inline.

PvE / PvP differences

Where values differ by server type, present both in one place, labeled — e.g. a two-column table or a PvP differences subsection. Do not fork pages.

Update history

Reverse-chronological bullet list, one entry per patch, linked to the patch article:

==Update history==
* [[Patch 1.1]] — Physical power increased to 35 from 33.7. '''Bug Fix:''' no longer loses durability when parried.
* [[Patch 1.0]] — Added.

Notation: "increased/reduced to X from Y". Prefixes: Bug Fix:, Removed:, New:. When a value changes, the old value moves here — body text and infobox always show only the current value. Removed content moves to a Removed section or page, never silently deleted.

Linking

• Link the first mention of an entity in the intro, in each infobox, and in each table row; avoid re-linking in running prose after the first mention.
• Item and entity mentions in lists and tables use {{ItemFrame}} (icon + link). In prose, plain links — no icons mid-sentence.
• Prefer redirects over piped links ("Keely" not "Keely") — redirects make search work.
• Create a redirect for every common alias, plural, and short name. Only create a disambiguation page when two or more real targets exist; otherwise redirect to the primary topic and add a hatnote.

Naming

• Article titles use exact in-game names, singular.
• Section headings are sentence case ("Update history", not "Update History"). Start at level 2 (==); never skip levels.
• Dates are written "May 8, 2024" (unambiguous across regions).

Images

• Infobox images use in-game inventory icons or renders on transparent/dark background.
• Screenshots: name files Subject description patchX.Y.png so superseded shots are identifiable after visual updates.
• Every image in templates gets meaningful alt= text (the entity name); purely decorative images get empty alt=.

Tables

• Stat comparisons use class="wikitable sortable" or a Cargo query — never image galleries laid out as tables.
• Header cells use ! (real <th>), with icons accompanied by text.
• Wrap wide tables in <div class="vr-table-scroll"> so they scroll on phones.
• Conditional cases (drop-rate modifiers, difficulty scaling) go in footnotes below the table, not inline in cells.

Colors

Never hardcode colors in templates or articles. Use the semantic tokens from MediaWiki:Citizen.css (--vr-rarity-*, --vr-infobox-*) or the classes in MediaWiki:Common.css (.vr-rarity-legendary etc.) — they adapt to both themes.