01 Scope & Self-Hosting
These Terms apply to Combat Master, a self-hostable Discord staff-operations bot published by mob5824 (the “Maintainer”), and to any Combat Master instance actually operated by or for the Maintainer. The bot offers tools such as announcements, schedules, polls, events, support tickets, role menus, welcome messages, an audit log, and a browser dashboard. Features may differ by version.
Combat Master is software that an operator runs on a machine they choose. If you install and operate a copy, or use a copy run by another community, that instance’s operator controls its configuration, access, availability, records, and retention. The Maintainer does not administer or control an independent instance.
If you do not agree to these Terms for an instance operated by the Maintainer, stop using that instance and contact its operator. These Terms do not replace the open-source license applicable to a copy of the software.
02 The Software
Combat Master is a discord.py bot whose staff tools are organized under the /manage command group. Depending on the version and configuration, staff can publish, schedule, repeat, edit, and delete announcements; use templates, approval queues, quiet hours, and pins; run polls and events; open support tickets; manage reaction roles and role menus; configure welcome messages; and review audit records through Discord or the browser dashboard.
Combat Master is an operations tool. It does not provide moderation punishments or warnings, member applications, music, voice playback, or streaming features. The bot follows staff configuration and requested actions; it does not judge whether a post, poll, ticket decision, role assignment, or server policy is fair or lawful.
03 Eligibility & Discord Rules
You must meet Discord’s minimum age requirement and any higher minimum age that applies where you live. Use must comply with applicable law and Discord’s current , , and applicable developer policies.
Discord is a separate service. Discord may change its API, permissions, platform, or policies, or restrict an account, application, or server. The Maintainer does not control those decisions.
04 Server Operator Responsibilities
Server owners and administrators decide whether Combat Master is appropriate and are responsible for the instance they configure. They agree to:
- Grant only the Discord permissions required for the features they enable, configure appropriate staff roles and channels, and keep trusted staff access current.
- Secure the bot token, dashboard token, host, configuration, database, logs, and backups, and limit access to the dashboard and records.
- Enable and configure Discord’s privileged Server Members and Message Content intents only when needed for features such as welcome messages and ticket transcript handling.
- Tell members what the bot does in their server, including that ticket transcripts may be saved and shared with the configured staff log channel.
- Choose suitable access, retention, and deletion practices for the instance and for messages sent through Discord.
Removing the bot from a Discord server does not necessarily stop a separately running process or remove files from its host. The operator must stop the instance and handle local data.
05 Content & Announcements
Text entered by server staff—such as announcement titles and bodies, templates, poll questions and options, event descriptions, welcome messages, approval requests, and audit details—is controlled by the people who create or configure it. Use only content you have permission to share, and do not put passwords, payment details, or unnecessary sensitive information into bot features.
Announcements and other messages may be posted to Discord channels and become visible to their members. Server operators are responsible for deciding what to publish, choosing the audience, and responding to requests about records they control. Discord messages already sent may remain subject to Discord’s own systems and policies.
06 Support Tickets & Transcript Notice
When a ticket is closed, Combat Master attempts to read up to the first 1,000 messages in the ticket channel. If successful, it saves a transcript containing message timestamps, authors, text, and attachment URLs in the local database, and posts a text-file copy to the configured staff log channel. The ticket channel is then deleted; closing the channel does not delete the saved transcript. The project does not document a general automatic transcript-expiration period.
Ticket authors and staff should not include information they do not want the server’s authorized staff or instance operator to retain. The operator is responsible for informing members, restricting access to the database and staff log channel, and deciding how long transcripts are kept. If the channel cannot be read, the ticket can still close without a transcript.
07 Dashboard & Security
The browser dashboard runs in the bot process and listens on loopback (127.0.0.1:8765) by default. It is protected by a separate dashboard token. The project advises against exposing its port directly to the public internet. If an operator deliberately makes it reachable through a proxy or other network, the operator is responsible for HTTPS, host and proxy configuration, access restrictions, credential protection, and firewall rules.
No software or configuration can guarantee absolute security. Do not publish bot or dashboard tokens, database files, or private ticket transcripts in a public repository, screenshot, issue, or chat. Replace any credential that has been exposed.
08 Acceptable Use
You may not use Combat Master or an instance operated by the Maintainer to violate law or Discord policy, infringe another person’s rights, threaten or harass people, disclose information without authorization, disrupt or probe systems, bypass access controls, or interfere with Discord, the bot, the dashboard, or another person’s account.
Server operators remain responsible for the actions of their staff, the content they publish, ticket access, and the configuration and security of their own instance.
09 Third Parties & Source Code
Combat Master communicates with Discord and may depend on the machine, network, and services selected by an instance operator. Those services have separate terms and privacy practices. The Maintainer does not control or guarantee them.
The Combat Master repository identifies the project as MIT-licensed. Review the for the terms that accompany your copy. These Terms do not grant rights to Discord or other third-party services.
10 Availability & Changes
Combat Master is provided on an “as available” basis. Features may change, be interrupted, or stop working due to software updates, configuration, host conditions, or changes to Discord and other dependencies. The Maintainer does not promise uptime, a support response, or continued availability of any feature.
These Terms may be revised by posting an updated copy with a new “Last updated” date. Continued use of an instance operated by the Maintainer after a revision takes effect means you accept the revised Terms. If you do not, stop using that instance.
11 Disclaimer of Warranties
TO THE MAXIMUM EXTENT PERMITTED BY LAW, COMBAT MASTER AND RELATED MATERIALS ARE PROVIDED “AS IS” AND “AS AVAILABLE,” WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NON-INFRINGEMENT. THE MAINTAINER DOES NOT WARRANT THAT THE SOFTWARE WILL BE UNINTERRUPTED, ERROR-FREE, OR SECURE. NOTHING HERE EXCLUDES A WARRANTY THAT CANNOT LAWFULLY BE EXCLUDED.
12 Limitation of Liability
TO THE MAXIMUM EXTENT PERMITTED BY LAW, THE MAINTAINER WILL NOT BE LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES, OR FOR LOST DATA, LOST PROFITS, SERVICE INTERRUPTION, STAFF DECISIONS, POSTED CONTENT, ROLE CHANGES, TICKET DISCLOSURES, OR THIRD-PARTY CONDUCT ARISING FROM USE OF COMBAT MASTER. NOTHING IN THESE TERMS LIMITS LIABILITY THAT CANNOT LAWFULLY BE LIMITED.
13 Ending Use & Contact
A server administrator can remove Combat Master from a Discord server, and an instance operator can stop their own copy at any time. The Maintainer may suspend an instance they operate for abuse, security, legal, or operational reasons. Ending use does not automatically erase information held by Discord, an instance operator, a staff log channel, or a hosting provider. See the for data requests.
Questions about these Terms or Combat Master may be sent to . Include “Combat Master” in the subject. For an independent instance, contact its operator about its operation, decisions, or records.
Project: ·