1. General Provisions
Warning: By using MOD_BOT, you agree to these terms. If you do not agree, please do not add the bot to your server.
1.1. Definitions
- Bot — MOD_BOT software for the Discord platform
- Developer — the creator and owner of the bot
- User — any Discord user interacting with the bot
- Administrator — a user with permissions to manage a Discord server
1.2. General Conditions
- The bot is provided on the basis of best-effort stability
- 100% uninterrupted operation is not guaranteed due to external factors
- The developer reserves the right to change functionality without notice
- Usage is governed by Discord Terms of Service
2. User Responsibilities
2.1. Prohibited Actions
- Spam — mass sending of commands
- Abuse — using the bot to harass users
- Bypassing restrictions — attempts to circumvent the punishment system
- Violating Discord rules — using the bot in violation of Discord policy
- Birthday command spam — attempts to bypass the hourly limit or mass sending of birthday commands
- Ticket spam — opening tickets without reason or mass-creating requests
- Uploading prohibited files — attempts to upload non-image files or files with malicious content to tickets
2.2. Administrator Responsibilities
- Server administrators are responsible for the actions of users with the bot
- It is recommended to restrict access to moderation and birthday settings commands
- When using commands, correct punishment reasons must be provided
- It is forbidden to use the punishment system to abuse power
- Administrators have the right to remove birthday data via the
/birthday_admin_remove command if server rules are violated
Example: If a user uses the bot for spam, the server administrator must restrict their access to the bot or remove their birthday data.
3. Limitation of Liability
Important: These limitations are standard practice for online services. They protect us from situations we cannot control.
- Data loss when the bot is removed from a server
- Conflicts with other bots
- Operation of the bot on modified Discord clients
- Direct or indirect damage from using the bot
- Missed or delayed birthday greetings due to technical failures
3.1. Guarantees and Availability
- We strive to ensure stable operation of the bot, but cannot guarantee 100% availability
- Technical maintenance is carried out to improve the bot
- We are not responsible for issues caused by changes in the Discord API
- We do not guarantee the exact time birthday greetings are sent — it depends on server load
4. Bot Commands
The bot provides the following commands for server management:
4.1. Moderation Commands
/ban
/unban
/banlist
/kick
/mute
/unmute
/vcmute
/vcunmute
/warn
/unwarn
/tempban
/untempban
/clear
4.2. Information and Utility Commands
/history
/stats
/avatar
/userinfo
/commands
/serverinfo
/roleinfo
/channelinfo
/ping
/invite
/slowmode
/logs_setup
/logs_disable
/messagelogs_setup
4.2.1. Weather
/weather
/forecast
/air_quality
/set_my_city
/set_weather_unit
4.2.2. Translation
/translate
/set_my_language
/my_language
4.2.3. Announcements
/announce
/embed_create
4.3. Birthday Commands
/birthday
/birthdays
/birthday_help
/birthday_channel
/birthday_role
/birthday_admin_remove
Birthday usage rules:
- Provide only your own birth date
- Birth year is optional
- Using birthday commands for spam is prohibited
- Attempting to bypass the 1-hour limit between birthday changes is prohibited
- The server administrator may remove birthday data via
/birthday_admin_remove if rules are violated
Change Limit: The /birthday commands (set, update, delete) have a limit — once per hour per user. If you try to use the command earlier, the bot will show the remaining time.
Important: For moderation commands to work, the bot requires the Manage Roles and Moderate Members permissions. For birthday setup — Manage Channels (channel setup) and Manage Roles (role setup).
4.4. Voting Commands (Top.gg)
/vote
/checkvote
Top.gg voting usage rules:
- You can vote once every 12 hours
- The Voter role is automatically assigned after voting
- Using bots for mass voting is prohibited
- Creating fake accounts for voting is prohibited
4.5. Ticket Commands
/ticket_panel
/ticket_setup
/ticket_history
Ticket system usage rules:
- One user — one open ticket at a time
- Opening tickets for spam or jokes is prohibited
- Uploading non-image files to tickets is prohibited
- Maximum attachment size — 10 MB
- Allowed formats only: PNG, JPEG, GIF, WEBP
- Using tickets for advertising or distributing prohibited content is forbidden
- An administrator may close or delete a ticket without explanation
- Transcripts are stored and may be used to audit moderator work
Content responsibility: The user is responsible for the content of the ticket. Publishing the following in tickets is prohibited:
- Insults and threats
- NSFW content
- Personal data of third parties
- Virus files and malicious software
- Advertising of third-party services
Important: For the ticket system to work, the bot requires the Manage Channels permission (creating and deleting ticket channels).
4.6. Voice Mute
The bot provides a voice mute system through the /vcmute and /vcunmute commands.
How it works:
- ✅ Automatic removal — the mute is removed automatically when the specified time expires
- 🔄 Database storage — all issued mutes are stored in the database. When the bot restarts, timers are restored
- 🔁 Restoration on rejoin — if a user leaves and rejoins the channel, the bot checks the duration and reapplies the mute (if still active)
- ⚙️ Works with special server settings — even if the channel rule is "everyone joins muted," the bot correctly removes the mute via
/vcunmute or after expiry
Important: For voice mute to work, the bot requires the Mute Members permission.
Voice mute usage rules:
- Provide a correct reason for the mute
- Do not use mutes to abuse power
- It is recommended to issue mutes for a specific time (10m, 1h, 1d)
- Use permanent mute only for serious violations
4.7. Event Logging
The bot provides a logging system through the /logs_setup and /logs_disable commands.
What can be logged:
- 👥 Member joins and leaves — avatar, mention, ID, account age, time on server, roles
- 🔊 Voice events — join, leave, channel switch, mic mute/unmute, server mute/unmute, deafen/undeafen
- 🎭 Role history — role creation, deletion, updates, role assignments and removals
Important: For logging to work, the bot requires the Manage Channels (to send messages to log channels) and View Audit Log (to track role changes) permissions.
Logging system usage rules:
- Logs are used exclusively for moderation and server security
- Administrators are responsible for setting up channels (ensure the bot has access to them)
- It is prohibited to use logs to collect or distribute user personal data outside the server
- The bot does not store logs on its own servers — all messages are sent only to the Discord channels you specify
4.8. Message History
The bot stores message history in its own database for auditing and conflict resolution.
What is stored and retention periods:
- Regular messages — stored for up to 90 days.
- Deleted messages — stored for up to 7 days.
- Edited messages — both versions are saved (before and after editing).
Important: The bot does not store direct messages (DMs) or messages from channels it cannot access. Data is used exclusively for moderation. There is no direct command to delete history — if you want to delete your data, please contact support.
4.9. Smart Filters (Stop Words and Banned Words)
The bot allows you to configure two independent word lists for content filtering.
How it works:
- 🟡 Stop words — the bot does not delete the message. It sends a notification to the log channel (with "Checked" and "Delete" buttons). The moderator decides manually.
- 🔴 Banned words — the bot instantly deletes the message and logs it. The user doesn't even have time to see it.
Edit check: If a user sends a message and then edits it to add a banned word, the bot will still notice it and apply sanctions (even if the message is old).
Responsibility: Server administrators are solely responsible for the added word lists and their compliance with Discord rules. It is prohibited to use filters to collect data or discriminate on grounds protected by Discord policy.
4.10. Weather and Translation
The bot provides access to third-party APIs for weather data and text translation.
How it works:
- 🌤️ Weather — data is taken from open weather services. The bot does not guarantee 100% forecast accuracy.
- 🌐 Translation — performed via DeepL API. The bot translates text but does not guarantee perfect accuracy for complex technical terms.
- ⏳ Caching — weather data is cached for 10 minutes to save API limits.
Important: Do not send confidential information (passwords, personal data, tokens) via /translate. The text is sent to the third-party DeepL service for processing.
4.11. Announcements and Embed Builder
The /announce and /embed_create commands are available only to administrators and moderators.
Usage rules:
- Using
/announce and mass pings (@everyone, @here) for spam is prohibited.
- Publishing content that violates Discord rules (NSFW, ads, scams) via the embed builder is prohibited.
- Spoiler pings (hidden pings) still send notifications — use them responsibly.
- The embed builder automatically shuts down after 15 minutes of inactivity.
5. Changes to Terms
Notification: The developer reserves the right to change these terms. Continued use of the bot constitutes acceptance of the new terms.
- Changes are published on this page
- The date of the last update is indicated at the beginning of the document
- Major changes may be announced on the support server
6. Developer Rights
- Changing bot functionality
- Restricting access to the bot in case of violation of terms
- Terminating the bot's operation with prior notice (except in force majeure cases)
- Removing birthday data in case of violation of usage rules
- Removing ticket transcripts in case of rule violations
7. Contacts and Support