The Misfit Bot · Current Version 1.4-Beta

Bot Updates

See what changed, what it does, and what your server team needs to know.

Every standard release includes a quick overview followed by the features, commands, and setup guidance behind it. Owner Override changes remain summary-only for security.

What The Misfit Bot Does

One configurable system for daily community management, staff operations, and member engagement.

Moderation & Safety

Warnings, timeouts, reports, evidence tracking, banned-word controls, and staff action logs help teams keep their communities safe.

Tickets & Staff Workflows

Private ticket panels, claiming, permission controls, transcripts, applications, support requests, venting support, and LOA requests keep staff work organised.

Community Automation

Welcome messages, leveling, birthdays, AFK tools, automatic messages, counters, and configurable server systems reduce repetitive work.

Complete Patch History

Every recorded release from the newest deployed update back through the bot's foundations.

Early development dates were not preserved, so those entries are labelled as historical instead of being assigned an invented date. Patch #001–#017 belong to the Alpha era; Patch #018–#020 belong to 1.0-Beta, Patch #021 is 1.1-Beta, Patch #022 is 1.2-Beta, Patch #023 is 1.3-Beta, and Patch #024 begins 1.4-Beta. Features marked Historical / Disabled are included for reference only.
Patch #0241.4-BetaMajor UpdateDeployed

Server-Scoped Safety and Flexible Staff Roles

Quick summary

Every server now owns its word-filter lists and staff-role selection, while a dedicated Venting Crew can handle venting tickets without receiving access to other ticket types.

What Changed

1

Per-server word filters

Blacklists, whitelists, and enabled state are isolated by Discord server, with safe migration of existing shared lists.

2

Flexible role presets

Server owners can exclude unused preset roles so deleted roles are not recreated, then include or create only the roles they want.

3

Venting Crew

A configured Venting Crew role can view and manage venting tickets without gaining access to other ticket types.

4

New server-config key

VENTING_CREW_ROLE_ID, with the friendly ventingcrew alias, appears in the bot's valid keys and website role selector.

5

Matching dashboard controls

The website edits each server's word lists, role exclusions, and Venting Crew role through the live bot bridge.

Patch #0231.3-BetaMajor UpdateDeployed

Major Dashboard and Staff Management Fix

Quick summary

The website-to-bot connection is restored and traceable, while staff onboarding now safely applies titled role names and restores each member's exact original display name on removal.

What Changed

1

Dashboard bridge restored

The missing local bridge modules are restored so dashboard saves reach the bot and canonical local JSON changes are returned to the website.

2

End-to-end diagnostics

Website and bot requests share a request ID, with clear status and failure logs on both sides.

3

Safe staff names

/staffadd stores the untouched pre-staff display name before applying <Title> <Name> (<Role>); promotions update the role suffix and removals restore the saved name.

4

Duplicate patch protection

Discord history is the delivery source of truth, and duplicate bot-authored copies of the same numbered patch are automatically reduced to the oldest message after restarts or overlapping processes.

5

Permission safety

Council+, role hierarchy, Manage Roles, and Manage Nicknames checks remain enforced, and no owner-only control is exposed.

Patch #0221.2-BetaMinor UpdateDeployed

Same-Server Legacy Ticket Migration

Quick summary

Legacy ticket channels can now be consolidated into the configured ticket transcript channel, while strict same-server routing prevents ticket data from being sent to another Discord server.

What Changed

1

Same-server enforcement

Ticket transcripts resolve only the destination saved inside their source server. Cross-server fallback routing is blocked.

2

Automatic legacy migration

Startup and !settickettranscripts scan recognised legacy and closed-ticket categories, copy each ticket into the local transcript channel, and delete the original only after the upload succeeds.

3

Safe retries

Source-channel archive markers prevent duplicate transcript posts. Any channel that cannot be fully archived remains untouched so staff can correct permissions and retry.

4

Complete records

Transcript files retain chronological messages, edits, reply references, attachment details and URLs, stickers, reactions, and embed contents.

Patch #0211.1-BetaMinor UpdateDeployed

Automatic Discord Patch Notes and Central Transcripts

Quick summary

Patch Notes now auto-post as polished Nightfall embeds without duplicates, and every ticket transcript is kept in one explicitly selected central channel.

What Changed

1

Automatic Patch Notes

New official releases post to every configured server update channel. After a restart, the bot catches up with only the newest unseen patch.

2

Polished Nightfall embeds

Announcements use #C32CDD with a clear summary, version, patch number, release type, status, changes, commands, staff workflow, date, and website link.

3

Duplicate protection

The bot remembers the last patch delivered to each server so reconnects and restarts do not repeatedly post the same announcement.

4

One transcript destination

Every closed-ticket transcript file goes into one explicitly configured channel. The bot does not create a separate transcript channel for each ticket.

Patch #0201.0-BetaMajor UpdateDeployed

Unified Patch Sync and Staff Role Naming

Quick summary

Patch Notes now use the bot's history as the live source for Discord and the website, while release-era labels and Co-Lead staff-role names are consistent everywhere.

What Changed

1

Automatic history sync

The bot exposes a public read-only Patch Notes feed. The website reads it on every request and uses its deployed history as a fallback whenever the bot bridge is unavailable.

2

Alpha and Beta eras

Patch #001–#017 are labelled Alpha. Patch #018 and every later release are labelled 1.0-Beta.

3

Correct Co-Lead naming

Co Lead A, Co Lead B, and Co Lead A/B now display as Co-Lead A, Co-Lead B, and Co-Lead A/B without changing saved role IDs or legacy command aliases.

Patch #0191.0-BetaMajor UpdateDeployed

Complete Bot Update History

Quick summary

The website and bot now carry one chronological, numbered release history with summaries, full staff breakdowns, commands, status labels, and protected Owner Override notes.

What Changed

1

Patch #001–#019 timeline

Every reconstructed bot milestone is listed oldest to newest with Major Update or Patch labels and honest date status.

2

In-Discord history

Staff and members can browse the same built-in history, and the owner can publish any recorded release to configured update channels.

3

Public update page

The Bot Updates page explains what each feature does, which commands belong to it, and what server staff need to configure or check.

Patch #0181.0-BetaFeature IntroductionDeployed

Patch Notes Introduction + LOA Ticket System

Quick summary

Welcome to the first official Misfit Bot patch notes. Future features, fixes, commands, permission changes, and staff actions will now be documented, while LOA tickets give staff a clear way to request time away.

What Changed

1

Patch Notes System

An official update tracker now covers new features, bug fixes, command additions, permission changes, version numbers, setup notes, required steps, and a staff-ready summary.

2

LOA Ticket System

Staff can request time away, provide the information required by their server, notify leadership, and keep activity records accurate. Leadership can review, approve or deny, and track active absences.

3

Improved staff communication

Structured documentation and a clear absence process help staff understand what changed, which permissions to confirm, and whether any follow-up action is required.

4

Protected internal changes

Public Patch Notes do not expose owner-only systems, private maintenance commands, or protected operational details.

Patch #017AlphaMajor UpdateDeployed

Staff Presets and Dashboard Reliability

Quick summary

Server role presets, reliable dashboard saves, clearer failures, and central owner activity transcripts improved configuration and auditing.

What Changed

1

Role presets

Default/Misfit and Legacy presets quickly apply the expected staff-role layout, with matching dashboard choices.

2

Reliable dashboard saves

Configuration is saved canonically and read back for verification; stale or wrong-server channel values no longer block unrelated saves.

3

Auditing and diagnostics

Exact errors, request IDs, audit logs, central bot-use transcripts, and a missing dashboard logger fix make problems easier to trace.

Patch #016AlphaPatchDeployed

Birthday Slash Commands

Quick summary

Members can manage their birthdays while staff can configure announcements, roles, and manual checks.

What Changed

1

Member self-service

Members can set, remove, list, and check saved birthdays through slash commands.

2

Staff administration

Staff can update another member, select the birthday channel and role, review settings, and run a manual check.

Patch #015AlphaMajor UpdateDeployed

Legal and Information Commands

Quick summary

Members gained direct access to the bot's terms, EULA, privacy policy, and official website.

What Changed

1

Legal access

Terms/EULA and privacy-policy commands make important bot information available without staff intervention.

2

Official links

A website command directs users to the recognised Nightfall Syndicate site.

Patch #014AlphaPatchDeployed

Expanded Moderation

Quick summary

The moderation toolkit gained a complete unban workflow with reasons, evidence, aliases, and slash-command support.

What Changed

1

Flexible member lookup

Staff can identify a banned member by ID, username, or tag.

2

Documented decisions

Reasons and optional evidence keep reversal decisions accountable.

3

Prefix and slash support

The workflow is accessible from both command styles for staff convenience.

Patch #013AlphaPatchDeployed

Owner Override Controls

Quick summary

Private owner-only recovery and administrative controls were expanded to help resolve exceptional server situations. Operational details remain intentionally private.

Summary-only release

This entry concerns Owner Override controls. Commands, implementation details, and staff workflow are intentionally withheld for operational security.

Patch #012AlphaMajor UpdateDeployed

Timed Server Events

Quick summary

Staff gained scheduled server events, including time-limited XP multipliers with start, stop, list, and slash-command controls.

What Changed

1

Timed XP events

Authorised staff can run a chosen XP multiplier for a natural duration such as an hour or a day.

2

Event controls

Events can be started, inspected, and stopped from prefix or slash commands.

Patch #011AlphaMajor UpdateHistorical / Disabled

Temporary Voice Channel Controls

Quick summary

Temporary voice owners received an interactive control panel for editing and managing their created channel; the module is currently disabled.

What Changed

1

Interactive control panel

Buttons and modals supported renaming, limits, privacy, locking, hiding, permits, rejects, ownership, and channel deletion.

2

Shared management

Channel owners could manage their temporary space from a reusable voice-control panel.

3

Current status

The feature is retained in history but disabled and hidden from normal help until it is ready to return.

Patch #010AlphaMajor UpdateDeployed

Graphic Rank Cards

Quick summary

Text rank output was upgraded into tailored graphic cards for chat and voice progression.

What Changed

1

Two progression cards

Members can request separate chat and voice cards showing level, XP progress, and ranking context.

2

Visual refinements

Card proportions, long-name handling, staff display-name overrides, and colour customisation were improved.

Patch #009AlphaPatchDeployed

Moderation and Logging Refinements

Quick summary

Startup recovery, slash-command reporting, purge behaviour, verified-role display, and staff help were cleaned up.

What Changed

1

Startup recovery

Ticket views are repaired at startup so older panels keep responding after restarts.

2

Cleaner operations

Purge no longer creates an unnecessary moderation case, and slash-sync results can be reported in the appropriate channel.

3

Accurate guidance

Verified-role emoji output, role-filtered staff help, command aliases, and hidden restart controls were corrected.

Patch #008AlphaMajor UpdateDeployed

Local Storage Conversion

Quick summary

Runtime configuration and server data were converted to local-only storage with health checks, backups, and an offline recovery path.

What Changed

1

Local-only runtime

The bot no longer depends on GitHub for normal server configuration reads and writes.

2

Health and backups

Owners can inspect paths, list files, verify data, and create targeted or complete backups.

3

Recovery tooling

An offline pull utility remains available for deliberate recovery without restoring live GitHub dependency.

Patch #007AlphaPatchHistorical / Disabled

Storage Migration Tools

Quick summary

Temporary migration and validation tools helped move server data safely from GitHub-backed storage to local files.

What Changed

1

Migration checks

Dry runs, pull checks, forced migrations, and backups protected configuration during the transition.

2

Historical system

These GitHub migration commands were intentionally retired after local storage became the active system.

Patch #006AlphaPatchDeployed

Counter Improvements

Quick summary

Server counters gained clearer emoji presentation and configuration refinements.

What Changed

1

Readable counters

Counter channel names can include the server's chosen emoji and clearer labels.

2

Safer refreshes

Counter updates were refined to reduce unnecessary or confusing channel-name changes.

Patch #005AlphaMajor UpdateDeployed

Voice Activity and Anti-AFK

Quick summary

Voice XP, AFK movement, solo-channel rules, lockouts, ignored channels, and owner exemptions were made safer and configurable.

What Changed

1

Meaningful voice activity

Voice XP requires another non-bot participant; muted or deafened members do not gain activity time or XP.

2

Anti-AFK safeguards

Solo inactivity can trigger an AFK action and a temporary 5–10 minute lockout, while muted/deafened members are not incorrectly kicked.

3

Server controls

Auto AFK, return handling, activity checks, ignored voice channels, staff disconnect roles, and owner exemptions can be configured.

Patch #004AlphaMajor UpdateDeployed

Custom Leveling

Quick summary

Chat and voice XP ranges, cooldowns, owner and booster bonuses, and graphic rank cards became configurable.

What Changed

1

Custom XP rules

Administrators can independently tune minimum XP, maximum XP, and cooldowns for chat and voice activity.

2

Boosts and rank cards

Owner and configured booster bonuses are supported alongside graphic chat/voice rank cards.

3

Member styling

Members can customise rank-card colours and display names within server rules.

Patch #003AlphaPatchDeployed

Staff Activity Tracking

Quick summary

Daily and weekly staff AFK activity reports, aliases, limits, and historical week lookup were added.

What Changed

1

Activity leaderboards

Authorised staff can review daily or weekly AFK activity with an optional result limit.

2

Weekly history

Archived week numbers can be requested for earlier staff activity reviews.

3

Command flexibility

Both slash and prefix versions are supported, including the legacy 'weak' spelling alias.

Patch #002AlphaMajor UpdateDeployed

Action Log Routing

Quick summary

Server teams gained one central action log plus optional event-specific routes and reusable routing groups.

What Changed

1

Central and individual routes

All events can use a main log channel while message, moderation, punishment, staff-command, and other categories can be routed separately.

2

Saved groups

Named groups let administrators configure several related event types together without repeating every route.

3

Better case context

Punishment and staff-command records include clearer staff, member, reason, evidence, and case information where available.

Patch #001AlphaMajor UpdateDeployed

Foundational Bot Systems

Quick summary

The Misfit Bot's core moderation, tickets, logging, leveling, automation, and server configuration systems were established.

What Changed

1

Moderation foundation

Warnings, timeouts, bans, reports, evidence handling, and staff permission checks created a consistent moderation workflow.

2

Tickets and server tools

Configurable ticket panels, transcripts, welcome tools, counters, reaction roles, and staff utilities became available from one modular bot.

3

Engagement systems

Chat and voice leveling, AFK tools, automatic messages, and member utilities provided the base for later community features.

Keep your server informed

Server administrators can select a Patch Notes channel in the dashboard or with !setupdatechannel #channel.