ZMN Bot Logo
    Documentation

    ZMN Bot Documentation

    Setup guides and configuration reference for every ZMN module — security, moderation, roles, leveling, and access control.

    Quick Navigation

    Basics
    Modules

    Templates

    Apply a ready-made server structure to a fresh or existing server, or build and submit your own.

    Overview

    A template describes a full server structure — roles, categories and channels, with their names, permissions and settings — that ZMN can build for you in one operation instead of one channel at a time. Browsing and previewing a template renders the exact same permission and channel math ZMN will actually apply, so what you see before confirming is what you get.

    Perfect for

    • • Standing up a brand-new server from a proven layout instead of building it channel by channel
    • • Recovering a known-good structure after a mistake or a compromise
    • • Restructuring an existing community without starting from zero

    Owner-only, and why

    Every Templates route is gated by requireGuildOwner, not the dashboard's usual access check. That means dashboard access — even an administrator grant, even the highest tier of it — does not open this page. Only the Discord-recorded owner of the server can browse, apply, restore a backup, or submit a template.

    Dashboard access is deliberately generous: it can be handed to trusted admins, specific roles, or specific modules. A template apply can delete every channel and role ZMN is allowed to delete. That is not a permission dashboard access was ever designed to hand out, so it never does — which is also why Templates never appears in the Dashboard Access grant list.

    Fresh vs. Add

    Every apply asks which of two modes to use, and the choice decides what happens to what you already have.

    Start fresh

    Deletes every channel and role ZMN is allowed to delete, then builds the template from nothing. The confirmation screen lists exactly what will be removed — and what Discord won't let ZMN touch.

    Add to this server

    Keeps everything already there and appends the template's categories, channels and roles alongside it. Nothing existing is deleted or changed.

    What a wipe cannot delete

    A fresh apply never queues these for deletion, and the confirmation screen says why each one was skipped:

    The @everyone role
    Managed roles and bot/integration roles — Discord owns their lifecycle, not ZMN
    Any role at or above ZMN's own highest role, the same hierarchy rule that governs every other moderation action
    A Community server's Rules and Community Updates channels, which Discord requires to exist

    The will-break warning

    Before you can confirm a fresh apply, ZMN scans the server's own settings — every module, not a fixed list of known ones — for anything pointing at a channel or role that is about to be deleted: a logging channel, a case-manager role, a ticket category, or anything else. Each hit is named on screen before you commit, so you can repoint it afterwards instead of discovering a silently broken setting days later.

    Structure backups

    Before a fresh apply deletes anything, ZMN captures the server's current structure and saves it as a structure backup — automatically, with no way to switch it off, written durably before the first delete is ever sent. A backup is kept for 24 hours and can be restored exactly once.

    Restoring

    Restore structure runs the same apply engine again, against the backup's own saved structure, as a full fresh rebuild. It sits outside the entitlement below entirely: a restore does not consume an apply and ignores the 24-hour cooldown. The only limit is the backup's own one-time use.

    A structure backup restores structure. It does not bring back everything a wipe destroys:

    Comes back

    • Categories, channels, their order and settings
    • Roles: name, colour, permissions, hoist, hierarchy
    • Role-based permission overwrites

    Does not come back

    Every member's role assignments — roles are recreated empty

    • Messages in deleted channels — gone permanently
    • Channel and role IDs — every #channel mention, invite, webhook, third-party bot config and ZMN setting still points at something dead
    • Member-specific channel overwrites
    • Webhooks, integrations, active invites

    Entitlement

    One rule decides whether an apply is allowed — read by the apply button and by the status the dashboard shows, so the two can never disagree.

    Free

    One apply, for the life of the server, and only of a free-tier template.

    Premium

    Any template, free or premium, with a 24-hour cooldown between applies.

    A structure backup restore is separate from all of this — see Structure backups above.

    Submitting your own template

    Building a structure in the builder is free for every server owner. Submitting it for staff review needs premium, and needs you to be the server's owner — the same requirement as applying, tightened to owner only.

    Up to 3 of your submissions can be pending review at once. Staff approve it, reject it with a reason, or leave it pending. An approved template is credited to your Discord username and appears in the public library at whatever tier staff assign it.

    A template started from an imported Discord template records where it came from, visible to the staff who review it.