Everything DJ-zeros does, explained step by step

When to use it

Setup appears before a Discord has an active DJ-zeros configuration. It applies all starting choices together, so moving between steps does not create a partial setup.

Walkthrough

1. Choose Universal, Gaming, Business, or Minimal as a starting point. A preset only selects starting modules.
2. Choose existing trusted roles for Super Admin and Admin, or allow DJ-zeros to create/reuse zero-permission bot roles.
3. Choose whether existing Discord roles should be imported as deny-by-default Access Groups. Importing grants nothing.
4. Review the summary, check the confirmation, and apply setup.

Verify

Overview should report Setup Complete. Then configure actual Access Group capabilities and test /dj help as a normal member.

The status row covers bot connection, setup, access policy, and service health. Configuration cards link to each area and distinguish Ready, Off, and Needs attention. Optional features may remain off permanently; an unused feature is not a failure.

The eight cards mirror Manage, Moderation, Roles, Support, Community, Games, Servers, and Info in Discord. The list is personalized from live role authority. If an action is absent, review its Access Group, module, and native Discord permission instead of granting Administrator.

1. Create a product, service, project, game, or showcase with a unique short URL name.
2. Add a summary, detailed description, lifecycle status, visibility, and safe HTTP/HTTPS resources.
3. Optionally connect an interest role and Discord channels.
4. Preview the member panel before publishing. Publishing again updates the saved panel when possible.
5. Members can follow, leave feedback, or report a problem. Staff review Intake Items, set priority/status, request details, and publish sanitized updates.

Archiving hides an Offering without deleting its history.

Key terms

• Access Group: reusable DJ-zeros policy.
• Binding: connection from a Discord role or person to that group.
• Capability: one bot action.
• Inheritance: a standard group adds another standard group's rules.

1. Select or create an Access Group.
2. Bind the correct Discord roles or people.
3. Open only the relevant capability group and choose Allow, Deny, or Inherit for each action.
4. Save and test through personalized help.

Explicit deny wins. Protected Admin groups do not participate in inheritance. Dragging groups changes display order only.

Anti-spam watches unusually rapid/repeated posting. Anti-link applies the configured link policy. Word filter matches your maintained list. Choose a private moderation log destination when you want records. Review each control; none must be enabled just to complete setup.

Select destinations only for workflows you use. DJ-zeros needs View Channel, Send Messages, and sometimes Read Message History in each destination. Keep moderation, tickets, feedback review, and logs private to the appropriate staff. Category-synced permissions reduce configuration drift. Use Start Here for your public rules, onboarding, and role-selection channel.

Auto Role is assigned when a member joins. Verification Role is assigned after the configured button workflow. DJ-zeros' Discord role must be above roles it assigns. It does not need Administrator permission.

Choose a category for generated ticket channels and a staff-only log channel. Confirm the bot can manage channels in that category and that ordinary members cannot see other members' tickets.

Set welcome/farewell text and destinations, suggestions, birthdays, level-up messages, starboard, and optional economy/progression. Welcome text supports {user}, {username}, {server}, {membercount}, {level}, {discordpage}, and {starthere}. The last two link the configured Start Here channel. Welcome messages are public and are not duplicated in DMs. Economy can remain disabled without affecting other commands.

Community games and rewards use guild-scoped data. Linked game profiles are user-supplied identifiers and stored statistics. Generic game-server monitoring tests TCP reachability only; see the complete gameserver tutorial.

Approved services report a simple state without exposing host addresses, ports, paths, process IDs, logs, or raw errors. Private DJ-server actions are separate fixed commands and appear only to the Supreme Ruler or an exact delegation.

Audit events identify the actor, action, and time for configuration changes. They support accountability and troubleshooting and remain when ordinary guild configuration is reset.

This area is hidden from customers. It lists fixed DJ-server commands and lets the Supreme Ruler grant selected commands to an exact person or role in a trusted Discord. Codex access is never delegatable. No dashboard field accepts arbitrary shell commands. The owner-only install control opens Discord's official server chooser with the reviewed least-privilege permissions; it never asks for Administrator. Installed servers appear in a private inventory here. Pausing one stops all guild activity while retaining its settings and records so it can be resumed later.

• View Profile: opens that member's DJ-zeros profile.
• View Warnings: shows authorized moderation history.
• Warn User: opens the existing warning workflow and requires moderation authority.

• Report Message: opens a structured report tied to that message.
• Star Message: submits the message to the configured starboard workflow.

Discord must allow the relevant app action in that channel, and DJ-zeros still applies its own capability checks.

1. Run /dj help.
2. Confirm the member is bound to the intended Access Group.
3. Confirm the exact command capability is allowed and not explicitly denied.
4. Confirm any required native Discord permission.
5. Confirm the optional module is enabled when applicable.

Use Discard Changes or reload the latest server data. “Changed elsewhere” means another save occurred first; DJ-zeros intentionally refuses to overwrite it.

Move the DJ-zeros bot role above the target role and grant Manage Roles only when the workflow needs it. Managed integration roles and roles above the bot cannot be assigned.

Confirm View Channel, Send Messages, Embed Links, and Read Message History as relevant. Check both category and channel-specific overrides.

/gameserver performs a TCP connection check. A UDP-only gameplay port cannot pass. Confirm public DNS/address policy, firewall access, and a real TCP service port.