Start with something you know: your first project, your clan's founding, a place you helped build or an event you witnessed. A short record with a date, a clear account and a source is enough to begin.
en, enter the full path, then select Select. Use lowercase words and hyphens, such as players/your-player-name, clans/your-clan-name or builds/your-build-name.templates/. Replace the copied title, short description and prompts with your own record. Add what you can support, remove headings you do not need, and say when a detail is unknown.Published articles appear in the collection matching their path. Use one of the eight collection prefixes shown on the templates page.
To copy a template manually instead, open its Page Actions → View Source, copy the Markdown body, and choose Markdown when creating your new page.
Your wiki account holds your login and settings. A public biography at players/<name> is a separate community article. Use your Minecraft name and documented server history; do not use the page to publish private contact details or prove account ownership.
Start with the player biography template.
YYYY-MM-DD where known; otherwise label the date approximate or unknown./report or Discord for misconduct allegations and private evidence.Give every image a useful caption and creator credit. Describe what it shows and when it was taken. Check the image itself for coordinates, private messages or other details you did not intend to publish.
Link related articles wherever they help a reader follow the story. A clan record might connect a player biography, a settlement and an event. Do not create empty pages simply to make every link exist.
Make focused edits and discuss substantial or disputed changes with an editor in Discord. Read the page history before revising disputed material. If accounts conflict, identify their sources and ask an editor to help resolve the wording.
Saving a public article publishes your change. There is no automatic approval queue. Editors can review revisions and recover earlier versions; contributors should preview carefully and correct mistakes openly.