The ERLC Discord Bot Ecosystem: A Comparison of the Platforms Powering Roblox Communities

Research date: 10 November 2026. Every product, price and feature below was verified against official sources on that date. Discord bot platforms change quickly — confirm current details with each vendor before making a decision.

1. Introduction: running a community inside ER:LC

Emergency Response: Liberty County (ER:LC) is a prominent roleplay experience on Roblox, and it is built around private servers that communities run themselves. That creates a management problem most games don't have: a community needs to control who joins its private server, keep an in-game staff team organised across time zones, police both the Discord server and the game, and prove to applicants that they are who they say they are.

The Discord bot ecosystem that has grown up around ER:LC is the answer to that problem. Some of it is ERLC-native, some of it is adjacent CAD/dispatch software, and — as the 2026 shutdowns below show — some of it doesn't survive. This article maps the ecosystem as it stands in November 2026: who the players are, what they can actually do, where they differ technically, and what the future of this category looks like.

2. Why ERLC communities use Discord bots and management platforms

Three technical realities drive adoption:

1. The ER:LC API exists but is bare. The official private-server API at api.erlc.gg exposes live server state (players, staff lists, join/kill/command logs, queue) and allows a whitelisted application to run in-game commands — but it offers no user-facing interface, no persistent records, no Discord delivery, and no history beyond the current session (official API docs). Every community-facing feature has to be built on top of it — and because the API documents no archival-history guarantee or retention policy, a platform must store whatever records its community will need later.
2. Access to the API is gated. A server owner must purchase the in-game "ERLC API" pack to obtain a server key, and applications serving many servers need a separate global application key. That gate makes turnkey platforms attractive: the platform handles keys, rate limits and error handling for hundreds of communities.
3. Discord is a primary coordination surface. Applications, rosters, shifts, LOAs and moderation records are commonly organised in Discord alongside the web dashboards the platforms themselves provide. A bot that bridges Discord and the game removes a large share of that manual coordination — the exact amount varies by community and none of the vendors publishes measurements of it.

3. The ecosystem at a glance

As of 10 November 2026, the verified landscape looks like this:

• Live ERLC-native suites: Melonly, Boomerang, Central, Trident.
• Adjacent CAD/CMS platform with an official ERLC integration: Sonoran Software Systems (Sonoran CAD / CMS).
• Emerging and smaller bots: a long tail including CADLY, CoreRP Systems, County Control, ERLC Nexus and several listing-only projects with thin evidence. Two of these — CADLY and County Control — are documented and complete enough that smaller communities realistically choose them today (profiles below).
• Recently discontinued giants: ERM (shut down 12 September 2026, formerly 28,000+ servers) and Ducky (shut down 11 August 2026, formerly ~15,100 communities). Both open-sourced their code.

Two observations shape everything that follows. First, the market consolidated sharply in 2026: the two largest verified casualties folded within five weeks of each other — Ducky citing decayed motivation and a complex codebase — and, whatever the cause, their departure left communities scrambling to migrate. Second, among the established suites profiled below, only Melonly and Boomerang ship that combination of live ERLC integration, staff workflow, applications and native Roblox verification; emerging products such as CADLY come close on documented breadth but lack the operating history of the incumbents.

4. Competitor profiles

Melonly

Melonly is the most complete ERLC management suite verified in this research.

• Official links: melonly.com · docs · official Discord (21,361 members)
• Operator: Melonly Ltd, registered in England & Wales (company no. 16956918). Closed-source.
• Status: Active and shipping — latest changelog V5.12.1 ("Watchdog V2"), blog post dated 24 October 2026.

Confirmed current capabilities (per official docs):

• ER:LC API-key integration with live server status, player lists, queue, and join/kill/command logs surfaced in a web "Mod Panel"; remote in-game command execution with a six-second cooldown.
• Staff roster and role management, promotions/demotions with announcements, shift tracking with activity quotas and leaderboards, LOA request/approval flows, and staff infractions (warn/strike/suspend/terminate) with appeals on the Plus tier.
• Applications and forms with quizzes, document workspaces and workflows.
• Departments as a paid add-on: separate rosters, shouts, permissions, and a lightweight CAD, with Discord role sync.
• Built-in Discord↔Roblox verification (no separate verification bot needed), configurable requirements and roles.
• A public server directory with profiles and reviews, plus an AI-moderation product ("Watchdog") sold separately.

Pricing (published): Free tier (2 linked ERLC servers, 100 API requests/month); Melonly Plus $5.99/month or $49.99/year or $139.99 lifetime per server; Pro (account-level, $2.49/month); Watchdog $9.99/month; Departments from $1.99/month; bundles from $6.99 to $34.99/month. This is the most transparent pricing structure in the category.

Limitations and unknowns: The status page could not be independently read (HTTP 403 to automated checks). Community-size figures are not published. Scale claims are vendor-published rather than independently audited.

Boomerang

Boomerang is the closest all-round competitor to Melonly and, by dated-release frequency, the fastest verified shipper among the established suites — and it is emphatically not a generic "utility bot": it is an ERLC/Roblox community suite.

• Official links: bmrg.app · docs · status · official Discord (2,566 members)
• Operator: a sole trader in Australia (ABN published in site Terms, updated 26 October 2026). Closed-source.
• Status: Active — the "Boomerang Panel" launched 28 October 2026. Self-reported scale: 586K+ members across 4,600+ communities.

Confirmed current capabilities (per official site and help centre):

• ER:LC API integration powering a live panel: player/team lists, joins/leaves/kills/mod-call logs, command execution, weather/time sync, and in-game role changes on join.
• Team, vehicle and livery restrictions mapped to Discord roles (team restrictions on the Premium tier).
• Staff roster and profiles; shifts, quotas and activity tracking; infractions with a case system; promotion scoring across weighted signals (activity, conduct, time in rank and more, each with a tunable weight); terminations.
• Applications, appeals, quizzes and forms with reviewer workflows, including Roblox account and group checks.
• Departments on Premium: linked department servers with cross-server bans, kicks and nicknames, plus an audit trail.
• Native Discord↔Roblox verification with minimum account age and group requirements, nickname sync, and verified/unverified roles.
• Multi-server dashboard, analytics, audit logs, sessions scheduling, tickets with transcripts.

Pricing (published): Free forever tier; Premium $4.99 per server per month (annual billing saves 17%; bulk discounts from four servers). A direct head-to-head with Melonly: Melonly vs Boomerang.

Limitations and unknowns: No public API documentation for developers; no GitHub presence. Scale figures are self-reported. Notably, the brand page states that use of the Boomerang brand requires written permission — this article therefore uses Boomerang's name rather than its logo.

Central

Central has the largest verified install base of any ERLC bot found (32,200 servers on the Discord Bot List) and the weakest public documentation.

• Official links: centralbot.xyz · DBL listing · support Discord (3,621 members)
• Status: Live but in transition — no public documentation could be found (/docs returns 404), the premium page's copy was last updated 31 July 2024, and a "v4" is waitlist-only.

What is verifiable: Central is marketed as an "All-In-One solution for ER:LC Private Server Management", and its DBL listing documents Discord-side commands for session management (/session, /sessionvote, /shutdown, /lowplayers, /full, /bolo). Its marketing and listing describe staff feedback, LOA tracking, staff requests and moderation.

What could not be verified: Whether Central integrates with the ERLC API at all (no official evidence of live server data or in-game command execution was found), any roster/application/department functionality, any Roblox verification, and whether it is actively developed (no dated changelog). Pricing is unusual for the category: free core plus Premium tiers at 500/800/1000 Robux for one/two/three guilds.

Assessment: Central deserves its place in this comparison on installed-base evidence, but a community choosing between platforms should ask its developers direct questions — the public record here is thinner than for any other verified competitor.

Trident

Trident is a leaner roleplay-management bot with a genuine ERLC integration and documentation that has not kept pace with its development.

• Official links: trident.bot · docs · status (all operational) · official Discord (4,035 members)
• Status: Live, with a healthy status page and active Discord — but the docs' "last updated" footer reads two years old, and the latest documented feature wave is v2.1 "ER:LC Integration" from March 2024. The site itself reports v2.4.

Confirmed current capabilities (per official docs): ER:LC API-key integration with /erlc commands for server info, players, logs, kills, joins, mod calls, ban checks and in-game command execution; shift management with types and leaderboards; activity reports; LOA request/extend/end flows; moderation logging with ban requests and BOLOs; Discord role assignment on shift and preset permission roles; a multi-server web dashboard.

Important limitations: No roster/promotion, application or department modules are documented. Roblox linking depends on Bloxlink rather than a native verification system. The documented ERLC integration describes the 2024-era PRC API and mentions a paid "R$600 per server" API pack; whether Trident has migrated to API v2 is not stated publicly — a question worth asking directly. No pricing is published anywhere official (this article treats that as "no published price", not as a "free forever" promise).

Sonoran CAD / CMS (adjacent platform)

Sonoran is not a Discord staff bot — it is an established multi-game CAD/CMS platform with an official, free ERLC in-game integration, and ER:LC lists it among its featured partner clients.

• Official links: sonoransoftware.com · ER:LC integration page · pricing · official Discord (10,103 members)
• Operator: Sonoran Software Systems LLC.

Confirmed current capabilities: The free CAD tier includes the official ER:LC integration: a live in-game 3D map with unit positions, 911-call handling, ID checks, vehicle registration, traffic stops and plate-reader/ALPR features. Sonoran CMS covers applications, rosters, departments, ranks and permissions as a separate product.

Pricing (published): CAD Free $0 (1 server, 35 users) up through Pro at $22.50/month; the all-in-one Sonoran One bundle is $49.99/month. Important caveat from Sonoran's own FAQ: while the ER:LC integration is free on the CAD free plan, the ER:LC private server still needs the paid "API Expansion Pack", and CAD plan limits apply.

Assessment: For communities whose centre of gravity is dispatch and CAD, Sonoran competes for the same budget. For Discord-first staff management, it solves a different problem than the bots above — see Sonoran CAD vs Melonly for the direct comparison.

The departed giants: ERM and Ducky

Both deserve mention because they shaped the market and demonstrate its risks.

• ERM (Emergency Response Management) was free, whitelabel, and claimed 28,000+ servers. Its GitHub readme announces that "starting from the 12th of September, ERM has shut down forever"; the notice documents the date and the release of the source under CC BY-NC-SA for self-hosting, but does not state a reason for the decision. Notably, ERM migrated to ER:LC API v2 in July 2026 — weeks before folding. A small community fork ("ERM CE") has since appeared, though its site was unreachable during the fact-check pass, so its self-reported scale remains unverified — it is not an established product.
• Ducky claimed 15,107 communities and ~991,000 users. Its official shutdown notice (11 August 2026) cites "significantly decayed" motivation and an "unnecessarily complex and messy" codebase; ERLC API keys were deleted and the global key was deactivated. All data was destroyed on 12 October 2026. The notice itself recommends Melonly as a migration destination — a useful signal about where the market stands.

Emerging tier highlights: CADLY and County Control

The emerging tier is documented in the research register in full; two of its members are complete enough that smaller communities genuinely choose between them and the established suites today.

• [CADLY](https://cadly.me/) — free core plus CADLY PRO at $5/month (or Robux). Documented capabilities include live ERLC player data and remote in-game commands, a shared moderation log across linked servers, promotions and infractions, application forms (15 free / 200 on PRO), department-server linking with delegated permissions, branded Roblox↔Discord verification with role assignment and suspicious-account detection, a multi-server web console with analytics (7-day history free / 30-day PRO), and a downloadable desktop app. Development is active, but the developer's identity is not published, there is no dated changelog, and its large-community install claims are self-reported.
• [County Control](https://cc.pcdev.info/) (Cordyx Studio) — free for every ER:LC community. Documented capabilities include an ERLC API-key connection with live sessions, join/kill/command and mod-call logs, arbitrary in-game commands, duty tracking with automatic in-game time capture, quotas and leaderboards, LOA, applications, infractions, a full Discord case system with anti-nuke, tickets, and a browser CAD with a live ER:LC map, records and voice radio. Weaknesses: no automated Roblox→Discord role sync (only per-command role scoping and a duty-account link), departments unverified, no published audit log, no changelog, and no public roadmap. Live in 87 servers (site counter, self-reported).

Both show how low the barrier to entry has become — and, with no changelogs and undisclosed operators in CADLY's case, they also show why operating history is part of any buying decision in this niche.

5. Feature comparison

Legend: ✓ available (officially documented, usable now) · ◐ limited (meaningful restrictions) · ? unverified (could not be confirmed or refuted) · — unavailable (evidence indicates not offered). "Unverified" is not a negative mark — it records an evidence gap, often caused by absent documentation.

Methodology note: entries come only from official product documentation, sites and announcements, verified on 10 November 2026 (sources in the register linked at the end of this article). The matrix covers the established products profiled above; the two documented emerging suites (CADLY, County Control) are summarised in their profiles rather than given full columns, because their records are thinner and partly self-reported. A competitor was never marked down for something that could not be verified — Central's row is mostly "?" because its documentation is absent, not because its features were found wanting. No numerical scoring is applied: with this much evidence asymmetry between vendors, any single number would imply false precision.

6. Differences in ERLC API integration

The official ER:LC API (apidocs.erlc.gg) defines what every platform above can and cannot do — and the differences between platforms are largely choices about how they use it.

Authentication is two-layered. Every request requires a server-key header — the per-server key a server owner gets after buying the in-game "ERLC API" pack. That key carries Co-Owner-equivalent in-game authority. Applications serving many communities additionally need a bare (non-Bearer) global Authorization application key (error code 2005 is returned to multi-server apps without one), with a higher-limit tier available by ticket for apps serving 100+ servers.

What the API provides: a single GET /v2/server endpoint returning required fields (name, owner and co-owners, current/max players, join key, verified-join requirement, team balance) plus optional data via query flags: full player details (location, callsign, wanted status), staff lists split by Admins/Mods/Helpers, join logs, queue, kill logs, command logs, mod calls, emergency calls and vehicles. Legacy v1 splits this data across separate paths and uniquely includes a bans endpoint that v2 does not. In-game commands are run via POST /v2/server/command (documented rate example: one command per five seconds).

What the API does not provide — and this is where platform implementations genuinely diverge:

• No user identity. There is no "login with ERLC" or OAuth flow linking a player to a Discord account. Platforms claiming to "know" who a player is are joining API player data with their own Roblox verification records.
• No documented history. Ban reasons and history, chat logs and archived logs are not exposed by the documented API — and the docs publish no archival-retention guarantee, so how long the live data remains readable is undocumented. Anything "historical" a platform shows is data it collected and stored itself; a community that wants history must rely entirely on the platform's retention.
• No webhook for everything. Event webhooks exist but are configured in-game and, per the current docs, only fire for ;-prefixed messages and emergency calls, signed with Ed25519. Join/leave logs and the rest must be polled.
• No audit trail. The API does not report back which commands a third-party platform ran. A community must rely on the platform's own logging.

Rate limits are per-key and unpublished ("varies per app"), with documented behaviour that ignoring a 429's Retry-After leads to temporary blocking (error 4001) and eventually a Cloudflare ban. This is why a platform's polling discipline matters — and why Melonly's free tier (100 API requests/month) and command cooldowns are not arbitrary: they reflect real upstream constraints.

The v1→v2 migration is a live fault line. ERM's commit history shows it migrated to api.erlc.gg v2 in July 2026; Trident's public documentation still describes the 2024-era PRC integration. When evaluating any platform, ask specifically whether it runs on API v2 today. A plain-language guide to the whole API: What the ER:LC API can and can't do.

7. Staff management and moderation capabilities

This is where the verified products separate into tiers.

Full-stack staff workflow (Melonly, Boomerang). Both ship roster management, shift/activity tracking, LOA flows, infractions, applications with reviewer workflows, and departments with cross-server coordination. Differences are matters of emphasis: Melonly couples its staff suite to a live "Mod Panel" and sells departments à la carte; Boomerang bundles departments into Premium and adds distinctive mechanics like weighted promotion scoring.

Focused staff tooling (Trident). Shifts, activity reports and LOAs are genuinely implemented and documented, but rosters/promotions, applications and departments are absent from its documentation. Trident suits communities that already organise staff elsewhere and want game-side automation.

Discord-side only or unproven (Central). Staff feedback, LOA and staff-request features are advertised, but without documentation the depth is unverifiable.

A note on moderation. "In-game moderation" through the API means executing in-game commands (kick, ban, jail, teleport and similar) as virtual server management, subject to the 5-second command pacing and the platform's own logging. Discord-side moderation (warnings, timeouts, message filtering, BOLOs) is a separate layer the bot itself implements. The strongest implementations — Melonly's and Boomerang's — combine both under one record system, so a Discord warning and an in-game kick end up in the same case history.

8. Discord and Roblox integration

Verification is table stakes at the top. Melonly and Boomerang ship native Discord↔Roblox verification with requirement controls (account age, group membership) and role syncing on verification. Trident delegates to Bloxlink — functional, but it means maintaining a second service and inheriting its limits. Central's verification support is unverified. This matters because ERLC's API can tell a platform which Roblox user is in the server, but only a verification record can tell the platform that Discord user X is Roblox user Y — the API itself offers no identity linkage.

Role sync as a differentiator. All the full-suite platforms synchronise Discord roles against staff state (verification, promotion/demotion, shifts). The depth of integration with department structures — per-department role mapping and permissions — is where paid tiers typically begin (Melonly Departments, Boomerang Premium).

9. Current features versus announced roadmaps

A methodological point worth making plainly: in this research, almost nothing was classified as "Announced/Planned", because almost nothing could be. A feature earns that label only when the developer has explicitly announced it with evidence — not when a community member wishes for it, and not when it would make sense for the product. What the verified record shows instead:

• Shipping cadence is the honest signal. Melonly's changelog (V5.12.1, October 2026) and Boomerang's launch log (Panel, 28 October 2026) demonstrate active development in the observable present.
• Transition states exist. Central's v4 is a waitlist page rather than a product surface; its current state should be evaluated as-is.
• Documentation lag is real. Trident's site reports v2.4 while its docs stop at a 2024 feature set. Features may exist that its documentation doesn't reflect — which is why this article classifies undocumented capabilities as "unverified" rather than assuming either direction.

The corollary for buyers: treat any roadmap claim that isn't on an official changelog, announcement channel or status page as speculation, whoever makes it — including us (see the Axolix section below).

10. Introducing Axolix

Axolix is an ERLC-focused Discord bot ecosystem and web platform in active development by a solo developer. In the spirit of the methodology above, here is what Axolix actually has today, verified against its own codebase on 10 November 2026 — separated carefully into shipped, partial and planned.

Implemented and verified today:

• A sharded Discord bot with slash commands and a staff-record system whose ranks are real Discord roles, with hierarchy rules (staff cannot act on themselves or on anyone at or above their rank).
• A per-rank staff permission matrix (seven keys: manage staff, moderation, configuration, integrations, logs, staff LOA and Discord moderation), editable in a web dashboard, enforced server-side by the API.
• Leave-of-absence (LOA) request and decision workflows.
• Departments with membership management and department-scoped permissions.
• Axolmod: a Discord word filter with a management dashboard, backed by audit logging.
• Axolcad: ER:LC integration built on the official API — server-key connection management, /v2/server status synchronisation with rate-limit handling and documented error-code mapping, /v2/server/command support, and a roster scheduler.
• Roblox account-link status, Discord OAuth login, a multi-server dashboard with a searchable server picker, and a searchable/filterable audit-event log.
• A live product site and API (axolix.xyz, api.axolix.xyz), both verified online on the research date.

In development / partial: billing (pricing is not yet published or live); overview analytics panels (deliberately shown as placeholders rather than invented numbers); fuller Discord role-sync automation; deeper Roblox identity verification flows.

Planned direction (internal aspiration — not an announced roadmap). In its internal product notes (not yet shipped), Axolix's positioning is to reach parity on staff-management essentials, compete on price and dashboard quality, and invest in permission-recovery and resilience — areas where the 2026 shutdowns demonstrated how much communities lose when a platform disappears. This paragraph is the same kind of evidence-free claim the methodology above rejects when vendors make it; treat it accordingly, and judge Axolix by what actually ships. A current known limitation: the permission registry already contains keys for features that are not built yet — manageModeration is annotated in the code as "issue warnings/infractions (Axolmod, once built)", and today it only guards the word-filter dashboard.

What Axolix does not claim: it does not yet match the breadth of Melonly or Boomerang — there are no applications/quizzes, no shift-activity tracking, no CAD, and no AI moderation today. Communities needing those today should choose the established suites; this article's purpose is a fair map of the ecosystem, and Axolix will have to evidence its place in it the same way every other platform here was judged: by what is documented, shipped, and verifiable.

11. What the future of ERLC management platforms could look like

Extrapolating only from verified 2026 evidence, three forces seem likely to shape the next year:

1. Consolidation around multi-server operators. The paid tiers of Melonly ($5.99/server) and Boomerang ($4.99/server) are priced per server, and both vendors court communities running department servers as separate Discord guilds. Expect bundling, bulk pricing and "one platform for the whole organisation" competition to intensify.
2. API v2 as a competence test. The 2026 shutdowns and ERM's last-minute v2 migration show that the ERLC API's evolution is a real maintenance liability. The platforms that treat rate-limit discipline, key security (Axolix's own client, for instance, treats the server key as a secret that must never appear in any error path) and endpoint migration as first-class engineering will be the ones still here in 2027.
3. Resilience and data portability become selling points. Ducky deleted all data on schedule; ERM left a self-hosting path. Communities are now visibly asking what happens if their platform folds. Export tools, data ownership and transparent status pages will likely move from nice-to-have to expected.

12. Research methodology and sources

This article is based on a multi-agent research project completed on 10 November 2026. Every competitor's official website, documentation and status page was fetched and read; claims were cross-checked across independent research passes; Discord member counts came from Discord's own API; install counts came from the Discord Bot List; shutdown evidence came from official notices and source repositories. The full evidence chain — competitor register, feature matrix, source register and asset register — is published in the accompanying research files.

Primary sources by competitor:

• Melonly: melonly.com, docs.melonly.com (pricing, ERLC integration, staff, verification pages), changelog
• Boomerang: bmrg.app, help centre, premium page, brand page, status
• Central: centralbot.xyz, Discord Bot List listing
• Trident: trident.bot, docs.trident.bot, status
• Sonoran: sonorancad.com/erlc, pricing, docs
• ERM: ermbot.xyz (redirect to export tool), GitHub
• Ducky: duckybot.xyz (official shutdown notice), GitHub
• ER:LC API: apidocs.erlc.gg, OpenAPI specifications
• Axolix: axolix.xyz, product documentation and source code

Known limitations of this research: vendor scale claims are self-reported; Melonly's status page and some JS-heavy pages (Sonoran CMS pricing) resisted automated checks; Central's absence of documentation means several of its capabilities are marked unverified rather than confirmed either way. No competitor logo is reproduced in this article: where official assets exist, reuse licences were not established (and Boomerang explicitly requires written permission), so competitor names are presented as text. Product features change — re-verify before deciding.

More in this series

• Melonly vs Boomerang: Which ERLC Management Bot Should Your Community Use?
• Sonoran CAD vs Melonly: CAD, Staff Suite, or Both?
• The Best ERLC Discord Bots in 2026
• What the ER:LC API Can and Can't Do
• ERM and Ducky Shut Down: Choosing a Platform That Won't Disappear

Written by the Axolix team. Axolix is our own product; its section above was fact-checked against our shipped code, and its "in development" list is deliberately as short on promises as it is long on disclosure.