New features, useful improvements, and important fixes for the communities using HAF Bot.
Entries describe features at their release date. Check current plans and limits before choosing a subscription.
Version 2026.08.28
Server Levels beta
Server Levels is now available for Premium servers. Connect your DayZ servers with CFTools and give members more Server XP for playing while the server is quiet.
New
Add up to five DayZ servers from the admin dashboard.
Members can check their level and the leaderboard with /serverlevel.
Set a channel for level-up messages if you want them.
Version 2026.07.29
Bring additional participants into Tickets
Support teams can now invite another Guild member into an active Ticket when extra context or collaboration is needed, without exposing which staff member granted access.
New
Enable staff-managed participants separately for each Ticket type from the admin dashboard.
Use /ticket add-user and /ticket remove-user inside an active Ticket to safely grant or revoke a Guild member's access.
Improved
Keep participant notifications neutral while retaining a staff-visible access history in the Ticket transcript for accountability.
Optionally require members to relink Player Link accounts after leaving and rejoining, while retaining their existing account records as inactive.
Version 2026.07.24
Introducing Suggestions and the Operations Inbox
Communities can now collect structured suggestions while Guild admins can see important automation problems in one place and take the next safe action from the Guild overview.
New
Configure Suggestions from the admin dashboard, then publish a permanent panel that guides members through structured proposals in a Discord Forum.
Help members improve proposals with duplicate warnings, configurable categories and questions, author revisions, and Considered Replies.
Let eligible members privately Support or Oppose a Suggestion while showing only aggregate participation totals to the community.
Move Suggestions through its review lifecycle with a written staff outcome for every final decision.
See an Operations Inbox when a scheduled Managed Message fails, a published message disappears, a Webhook destination repeatedly fails, or a Player Count server goes offline.
Review each problem's affected feature, severity, timing, impact, and recommended next step without exposing provider errors or credentials.
Improved
Suggestions includes guided resource setup, readiness checks, and repair tools, while Guild admins with write access can retry eligible Managed Message and Player Count operations directly.
Version 2026.07.19
Clan Management is now in beta
Guilds can now create and manage Clans through a guided Discord workflow. This feature is in beta, and we would love your feedback in the HAF Bot Discord.
New
Configure Clan eligibility, reviewer roles, managed Discord resources, recruitment, and lifecycle settings from the Clan Management dashboard.
Publish a customizable Clan creation panel where members can submit requests without learning a slash command.
Review each request with the applicant in a private Discord ticket using Approve, Request changes, and Reject actions.
Improved
Recover interrupted Clan provisioning and lifecycle work automatically while keeping Clan history and audit events consistent.
Clan Management is a beta feature. Share feedback with us at https://discord.gg/HpRPkdm6dv.
Version 2026.07.18
More reliable Tickets and managed storage
Guild admins can now see managed-storage usage at a glance, while Ticket recovery and background processing are more resilient to temporary failures.
New
View stored, temporarily reserved, and total managed-storage usage from the Guild overview.
Improved
Recover incomplete Ticket creation, closure, panel publication, and template-reply operations automatically after temporary Discord failures.
Process failed background jobs independently so one problem is less likely to delay unrelated moderation, webhook, storage, or Platform Link activity.
Fixed
Prevent duplicate processing when Discord gateway events are delivered more than once.
Version 2026.07.17.2
Reuse embed templates across messages and Tickets
Guild admins can save polished embed layouts once, then reuse them for Managed Messages and consistent Ticket replies.
New
Create, edit, duplicate, and reuse Guild-wide embed templates from the Managed Messages dashboard.
Send approved template replies from a Ticket or Staff Discussion Thread with autocomplete and a private preview before sending.
Version 2026.07.17.1
Better Ticket workflows and custom panel colours
Guild staff can review and respond to Tickets more reliably, while admins gain more control over the appearance and privacy of their Discord panels.
New
View a member's Ticket History from Discord, including links to open Tickets and available transcripts.
Choose custom embed colours for Ticket, LFG Noticeboard, and Player Link panels.
Improved
Staff Discussion Thread messages now remain private by default. When Anonymous Support is enabled, use !send to publish a response to the member.
Fixed
Fixed an issue that could cause an Anonymous Support response to appear twice in a Ticket.
Version 2026.07.17
Turnstile verification is now available
Premium and Premium Plus communities can add a Turnstile challenge to Member Verification before members receive their verified role.
New
Choose Turnstile as the verification method for Welcome DMs or Welcome Panels, giving new members a simple challenge before HAF grants access.
Version 2026.07.16
Draft and schedule Managed Messages
Guild admins can prepare Managed Messages without publishing immediately and schedule one future publication.
New
Save Managed Message drafts without creating a Discord message, then publish immediately or schedule a one-time future publication.
Improved
Edit, reschedule, or cancel scheduled drafts while ensuring the latest saved content is published at the chosen time.
Version 2026.07.14
More automatic responses for Bot Defense
Guild admins can now choose how each Bot Defense detector responds when suspicious message activity is detected.
Improved
Configure the Honeypot Detector and Rate Detector independently to warn the member, delete the triggering message, do both, or only raise a flag.
Apply each detector's selected response on every trip, including while the member already has an open Bot Defense flag.