# How we write and check our guides

> The Wilderack Crew's editorial policy. Where our guides get their facts, how we check them, how we keep them current and how to tell us about a mistake.

By the Wilderack Crew. Last reviewed 2026-11-13.

Every guide on Wilderack is written by the Wilderack Crew for people running a game server, often for the first time. This page explains where our facts come from, how we check them, and what we do when we get something wrong.

## What we publish

- **Server guides** in the [wiki](https://wilderack.com/wiki/): setting up, connecting, settings, mods, backups, performance and fixes for common errors, for every game we host.
- **Free tools**, like config generators and calculators, at [/tools](https://wilderack.com/tools/). Each tool page says which game version its facts match.
- **Buyer's guides**, which explain what to look for in a host for one game. We sell servers, so these say so at the top.
- **News** about game updates and what they mean for your server.

## Where our facts come from

We use sources in this order, and every guide lists the ones it used under **Sources**:

1. **The publisher or developer.** Official documentation, patch notes, the server's own readme or help output, and the default config files the server ships with.
2. **The platform.** Steam and SteamCMD documentation, Microsoft's Minecraft documentation, and the mod platform's own docs.
3. **A community reference** that the developers themselves point players to, such as a game's official community wiki, when the publisher has no page on the subject.

We never use another hosting company's guides or blog as a source, and we don't copy text from anyone. Facts are checked at the source and written in our own words.

## How we check a page

- **Settings, file names, ports and commands** are checked against the server's own files or the publisher's documentation for the version we name.
- **Each guide shows two dates.** "First published" is when it went up. "Last reviewed" is the last time we checked it against the game. When a guide was checked against one exact version, it says so next to the date.
- **Automatic checks run on every page** before it can be published: every link and section link must work, every source must be a publisher, a platform or a neutral reference, and no page may claim we are official or partnered with a publisher.
- **Our own service is described as it is today.** A feature that is still being built is labeled as coming, never written up as if you can use it now.

## How we use AI tools

We use AI tools to help with research, drafting and checking, the same way we use spell checkers and link checkers. They are never a source. Every fact on a page has to trace back to a source listed on that page, and the same checks run on every page however it was drafted.

## Independence

- **We are a host.** We sell game servers, and our guides link to our plans. Buyer's guides say this in their first lines and include a section on where Wilderack falls short for that game.
- **We don't rate or review other hosts.** You won't find scores, rankings or comparisons with named companies on this site.
- **Nobody pays us to mention them.** Publishers, mod authors and tool makers we link to have not paid for it.
- **We are not official.** Wilderack is not made by, approved by or partnered with any game's publisher. Game names and art belong to their owners, and each game's pages carry the notices its publisher asks for.

## Keeping guides current

Games update often, and a setting that worked last month can move. We review a game's guides after big updates and patch notes, and when players tell us something changed. When we check a page and nothing needed fixing, we still move its "Last reviewed" date, so you can see how fresh it is.

## Corrections

If you find a mistake, email support@wilderack.com with the page and what is wrong. We check it against the source and fix it. Small fixes, like a typo or a broken link, are made quietly.

When a fix changes what a reader should do, like a wrong port, setting or step, we don't change the page silently:

- We fix the page and move its "Last reviewed" date, or a news post's "Updated" date.
- We add a dated note under **Corrections** at the end of the page that says what was wrong and what the page says now. The note stays on the page.
- The byline shows the date of the latest correction, linked to that note.

## Who we are

Wilderack is run by Wilderack Inc., a Delaware corporation in the United States. Read more [about us](https://wilderack.com/about/) and [the crew](https://wilderack.com/company/team/), or see our [support promise](https://wilderack.com/company/support/).

## Questions and answers

### Who writes the Wilderack guides?

The Wilderack Crew, the team behind Wilderack. Every guide, tool and buyer's guide is signed with the crew's name, and the about page says who we are.

### Where do the facts in Wilderack guides come from?

From the game's publisher or developer first, then the platform it runs on, such as Steam or Microsoft, then a community wiki the developers point players to. Each guide lists its sources at the bottom.

### Does Wilderack use AI to write guides?

We use AI tools to help research, draft and check. They don't count as a source. Every fact has to come from a primary source listed on the page, and a page that fails our checks doesn't get published.

### How do I report a mistake in a guide?

Email support@wilderack.com with the page and what is wrong. We check it against the source and fix the page. When the fix changes what you should do, the page also gets a dated note under Corrections saying what changed.

---

Canonical page: https://wilderack.com/company/editorial-policy/
How we write and check our guides: https://wilderack.com/company/editorial-policy/
Corrections: support@wilderack.com
