Construct deploys blueprints from the GuildLabs builder — roles, categories, channels, permissions — and then runs the essentials: verification, anti-raid, welcome messages, tickets, and XP leveling. Free and open-source.
Turn a builder blueprint into a live server in seconds.
/setup blueprint:<file>Deploy a GuildLabs blueprint JSON to this server. Construct creates the roles, categories, and channels in the file — anything with a matching name is skipped, and nothing is ever deleted. Takes 10–30 seconds depending on size.
blueprintrequired — The blueprint.json exported from the GuildLabs builder (Download JSON on any template, or Export in the wizard)/setup blueprint:blueprint.json/diagnoseA health check: verifies Construct has the permissions it needs (Manage Roles, Manage Channels, and more), that its role sits high enough in the role list, and which features are configured. Run this first whenever something misbehaves.
/diagnoseSwitch on the server essentials, one subcommand each.
/config welcome channel:<channel> [message]Set the channel (and optional template) for welcome messages. The message supports {user} (a mention), {username}, and {server} placeholders.
channelrequired — Channel to send welcome messages inmessage — Custom message — use {user}, {server}, {username}/config welcome channel:#welcome message:Hey {user}, welcome to {server}!/config verification channel:<channel> role:<role>Set up a verification gate: pick the channel where the Verify panel lives and the role members receive when they click the button. Pair with channel permissions so unverified members can only see the gate.
channelrequired — Channel where the verify panel will be postedrolerequired — Role granted after a member verifies/config verification channel:#verify role:@Member/config antiraid enabled:<true|false> [threshold]Configure anti-raid protection. When more than the threshold of accounts join within 10 seconds, Construct takes action against the flood.
enabledrequired — Enable or disablethreshold — Joins per 10s before action (default 10)/config antiraid enabled:true threshold:8/config leveling enabled:<true|false> [announce]Enable XP leveling. Members earn XP by chatting; level-ups are announced in the channel you choose (or inline where they happen).
enabledrequired — Enable or disableannounce — Channel to announce level-ups (optional)/config leveling enabled:true announce:#level-ups/config tickets category:<category> support_role:<role>Set up the ticket system: choose the category where private ticket channels are created and the role that can see and reply to them.
categoryrequired — Category that ticket channels will be created insupport_rolerequired — Role that can see and reply to tickets/config tickets category:Support support_role:@Mod/config showShow the current Construct configuration for this server — every feature and where it points.
/config show/verify-panelPost (or re-post) the Verify button in the configured verification channel. Run /config verification first.
/verify-panelCommands anyone in the server can use.
/ticketOpen a private support ticket — a channel only you and the support role can see, with a Close Ticket button when you're done. One open ticket per member.
/ticket/rank [user]Check your XP, level, and progress to the next level — or look up someone else's.
user — Whose rank to look up (defaults to you)/rank/rank user:@friend/leaderboardShow the top XP earners in this server.
/leaderboardNo. Deploys are additive-only: Construct creates what's in the blueprint and skips anything with a matching name. It never deletes or modifies existing roles or channels.
It creates roles and channels and sets their permissions, which requires Manage Roles and Manage Channels at minimum; Administrator covers the moderation features (anti-raid) too. The bot is open-source, so you can read exactly what it does with the access.
From the GuildLabs builder: describe your server (or pick a template), review the blueprint, then either deploy directly from the web or use Download JSON and run /setup with the file.
Construct needs Manage Roles and Manage Channels. Run /diagnose for the full checklist — it flags exactly which permissions are missing and whether the bot's role needs to be moved.
Discord only lets a bot manage roles below its own highest role. Drag the Construct role to the top of Server Settings → Roles, then re-run /setup — already-created items are skipped, so it's safe.
Usually the configured role was deleted or is above Construct's role. Re-run /config verification with a valid role, make sure Construct's role sits above it, then /verify-panel to post a fresh panel.
Leveling is opt-in per server. An admin needs to run /config leveling enabled:true once; XP starts counting from that moment.