Wiki Administration

@wiki/delete <page>
@wiki/protect <page> and @wiki/unprotect <page>
@wiki/publish <page> and @wiki/unpublish <page>
@wiki/history <page>

Deleting needs wiki.delete and whatever the page requires to edit and delete it; protecting and publishing need wiki.admin. Deletion removes the page and its entire revision history. Protecting a page is a page requirement of wiki.admin to edit and delete it, in-game and on the web portal alike; it shows in @wiki/access and is cleared by @wiki/unprotect. Unpublished pages are drafts: hidden from anonymous web visitors and from the sitemap, and in-game their body and revision history are shown only to their author or a wiki.drafts holder who asks for them with /draft. See wiki reading drafts.

wiki revision history: revisions, numbered per locale
wiki permissions: what each wiki permission allows
wiki requirements combined: how requirements add up
wiki requirements: setting and checking requirements

Revision history

@wiki/history lists every revision with its editor, date, and edit summary, for the revision stream of your own locale. Each locale is numbered independently starting from 1, so “rev 3” of a French translation is unrelated to “rev 3” of the source; @wiki/history/source shows the source locale’s stream. An edit summary is prose about unpublished content, so a draft’s revisions are withheld exactly as its body is: @wiki/history/draft shows them, to a wiki.drafts holder or the author.

::: seealso

Wiki permissions

Every wiki action has a permission everybody needs for it: wiki.read, wiki.create, wiki.edit and wiki.delete. On top of that, a namespace, a category or a single page can require more, as MediaWiki’s namespace and page protections do. A target is namespace <name>, category <name>, or a page title as @wiki takes it.

The wiki’s own permissions:

Permission	Lets you
`wiki.read`	read pages
`wiki.create`	create pages
`wiki.edit`	edit and translate pages
`wiki.delete`	delete pages
`wiki.drafts`	read other people’s drafts (see wiki reading drafts)
`wiki.admin`	protect, publish and set requirements; skips namespace, category and page requirements

How requirements combine

A page requires everything its namespace, each of its categories and the page itself require, for the action and for reading it; deleting also requires what editing does. Requirements only add: no level lifts what another requires. A player needs every permission listed, and a permission comes from their roles, like any other (see roles). wiki.admin skips namespace, category and page requirements, though not the four global permissions.

Filing a page in a category is an edit under its current categories and under the new ones, so a category that requires lore.edit to edit can only gain pages from someone holding it. Creating a page needs what its namespace requires to create it and what the categories it starts in require.

New games start with the system namespace requiring wiki.admin to create, edit and delete its pages.

Wiki requirements

@wiki/require <target>=<action> [<permission> ...][, <action> ...]
@wiki/access <target>
@wiki/access <page>=<player>

@wiki/require replaces what the actions it names require and leaves the rest alone; an action with no permissions after it requires nothing again. The permissions must be built-in or defined with @permission/define (see @permission define). It needs wiki.admin.

@wiki/access <target> lists what a target requires; for a page, also what it inherits. @wiki/access <page>=<player> says, action by action, whether that player may act on the page and which requirement stops them. Asking about anyone but yourself needs wiki.admin. A page you may not read answers as one that does not exist.

> @wiki/require category lore=edit lore.edit, read
WIKI: Category lore now requires:
    edit    lore.edit
> @wiki/access combat_primer=*Alice
WIKI: What Alice may do with 'Combat Primer':
  read    allowed
  edit    category lore requires lore.edit
  delete  needs wiki.delete

From softcode, wikiaccess(<page>, <action>[, <player>]) returns 1 or 0.

::: seealso