What it is
This wiki is written by staff, in the browser, on the site itself. There is no separate editor to install and no markup to learn: pages are made of blocks (headings, paragraphs, steps, callouts, tables, images, command cards and so on) in an editor that behaves like a document. Every save is a revision you can compare and restore, a page is a draft until someone publishes it, and readers only ever see the published version.
Some pages are not written at all. The command reference, the changelog, the server rules, the laws and the FAQ are mirrors rebuilt from the game database on a schedule, so they cannot drift from what the game actually does. Editors can change a mirror page's summary and icon, not its body.
Before you start
You need a Roleplay Project account at admin level 3 (Senior Admin) or above. Sign in from the header link or by going to /editor; the site sends you to the UCP to sign in and back again. If your rank was raised recently and the editor still refuses you, sign out and in again. Before writing a guide, read two of the existing ones so the tone matches: en-GB, plain sentences, no em dashes, no staff-only information (no admin commands, tunables or table names), and every number taken from the game rather than remembered.
Steps
- Open the dashboard
Go to /editor. The dashboard lists every page by category with its status (draft, published, changes since publish), the last editor and a Needs attention list of pages nobody has touched in three months. Search finds a page by title or slug.
- Create a page from a template
New page asks for a title, a parent (which decides the slug and where it sits in the tree) and a template: System guide, How-to, Job, Faction, Law, Event, Reference or Blank. The template inserts the section headings with a hint under each; a system guide gets What it is, How to start, Step by step, Tips, Related commands and Worked example in that order.
- Write with the slash menu
Type a slash at the start of a line for the block list: Text (headings, paragraph, quote, divider), Lists (bullets, numbered, steps), Boxes (tip, warning, staff note, danger, toggle, tabs, columns, table), Media (image, YouTube), Code (code block, command line, keycap) and RPP (command card, worked example, stat, item card, location card). Typing filters the list; arrows and Enter pick. Type two square brackets to link to another page by title, or press Ctrl+K on selected text. Ctrl+S saves with a note; the editor also autosaves every couple of seconds.
- Use the RPP blocks for anything live
A command card takes a command id and shows its syntax, description and who can use it from the game's own command list, refreshed on every view. A stat block shows a live number such as players online. An item card shows the icon and name from the item catalogue. A location card takes coordinates and draws a map crop. Use these instead of typing the same facts by hand, so the page stays right when the game changes.
- Add a worked example
Every guide ends with a worked example: a scene or a walkthrough following one character through the feature. Write it yourself and leave the source set to author. The Generate button drafts one from the assistant if you are stuck, and marks it as generated; edit it before publishing.
- Publish
Ctrl+Shift+P, or the Publish button. The site renders the page and refuses to publish if a command card has no id, an image has no alt text, or a step is empty; unknown command ids and stats are warnings you can override. On success the page appears in the tree, the search, the sitemap, the in-game reader on F1 and the UCP assistant's knowledge within a few minutes.
- Review and revise
History shows every revision with a diff; Restore brings an old one back as a new draft. Comments can be anchored to a block for review notes and resolved when dealt with. Settings renames the page (old links redirect), moves it, and changes its icon, cover and template. Delete puts a page in the trash, from which an admin can restore it.
House style
Do | Do not |
|---|---|
Write for a player who has never seen the feature | Assume they know the command names |
Take every number from the game code or the live database | Guess prices, timers or limits |
Use a Steps block for anything with an order | Write numbered paragraphs by hand |
Put warnings in a Warning callout and tips in a Tip callout | Bold random sentences |
Link the first mention of another guide with a page link | Paste URLs |
Use a command card for every command the guide relies on | Type the syntax out and let it go stale |
Keep en-GB spelling: licence, colour, organise | Mix in en-US |
Use commas, full stops and brackets | Use em dashes, or placeholder text you mean to come back to |
If it goes wrong
The editor says someone else has the page. Pages have a soft lock while another editor is in them. Wait, or take over if you know they have gone; both of you keep your revisions either way.
Your publish was refused. The list of problems is shown; fix each and publish again. A command that the game does not have yet can be published as a warning, but the card will say the command is unknown until the game ships it.
You saved over something good. Open History, pick the revision from before and Restore it. Nothing is ever overwritten; every save is kept.
A mirror page is wrong. Fix the source: the command's description in the game, the rule on the rules panel, the law in the laws site or the FAQ entry. The mirror rebuilds on its own within the hour, or an admin can run the sync from the admin page.
Related commands
/rulesEveryoneOpen server rules UI.
/lawsEveryoneOpen the laws panel.
See also
Command reference for the ids command cards use
Getting started for the guides written to this standard