Verification

The Verified badge tells server admins that dzbot has reviewed what a mod does. It belongs to a published version, not to the mod as a whole: a new version is only verified once it has been reviewed too.

Apply

In the mod's Verification area, pick a published version and apply:

• a message: what the mod does and how to try it
• screenshots, videos or links that show it working

Only a published version can be verified — publish the draft first.

The review

A request goes through these steps, and you see each of them in the Verification area:

1. Submitted — waiting for a reviewer.
2. In review — dzbot looks at the version. The first time it is the whole mod; for every later version, the review compares it with the last verified one: changed files, config fields and the mod's switches.
3. Questions — the reviewer can ask back. You answer in the same conversation, with attachments if needed, and the request goes back to review.
4. Verified or declined. A declined request carries the reason.

You can withdraw a request as long as it is open.

Once a mod is verified

• Every new version you publish goes to review by itself — you do not have to apply again.
• Until it is verified, the badge says up to which version the mod is verified and that the newer one is in review.
• Servers on auto-update stay on the last verified version and only move once the new one is verified. Installing the mod also gives the newest verified version. Server admins can still update to an unverified version by hand; the installation page tells them it is not verified.

Give it up

If you would rather publish without review, give up verification in the Verification area. The badge goes away, open requests are closed, and servers on auto-update follow every version you publish again. You can apply again later.

dzbot can also take verification away, for example when a mod breaks servers.

Mods that were verified before the modding rebuild kept their badge on the version they had published then.