Discord3rdparties: the Discord Client Encyclopedia as a reference index

What the Discord Client Encyclopedia actually is

This repository is a Markdown document. The top level holds .github/, LICENSE, README.md and badges.md, and the README is the product: a set of tables listing third-party clients and mods for Discord, grouped by platform. The project describes itself as "a non-exhaustive collection of third-party clients and mods for Discord," and the table of contents splits the world into Mobile (Android and iOS), Desktop (official clients, mods, plugin bundlers, wrappers and adapters, third-party reimplementations), Game console clients, Other clients, and Third party server implementations.

That structure is the point. Someone who wants to modify the Discord Android app has a different problem from someone who wants a desktop client with plugins, and a single alphabetical list would serve neither. The audience is narrow but real: people who have heard a name such as Vendetta, Bunny or Aliucord and want to know whether it is alive, dead, or a fork of something else. The README answers that with a Development Status column rather than prose.

How the tables encode status, lineage and risk

Each row carries a name, a link, a Features description, one or more language badges, and a Development Status cell. The status vocabulary is small and literal: Active, Active (Legacy App), Active (In beta), still in development state, Discontinued, Broken, and Malware. The Android table shows the full range in one screen: Microcord and Vendroid are Active, Aliucord is Active but marked as a legacy app with a footnote, Rain is Active in beta, ReCord, Lumi, Bunny, Vendetta, CutTheCord, OpenCord and Treecord are Discontinued, Wintry is Broken, and Bluecord carries the Malware label with a footnote about scams and spying.

The Features column is where lineage lives. Vendroid is described as a WebView embedding the Discord site and loading Vencord; Kettu is described as continuing Bunny's mission; Voxi is a fork of Revenge Classic; ShiggyCord is a fork of Kettu; Revenge is a fork of Bunny. Reading those cells together gives you a dependency graph of sorts, which matters because a discontinued parent often explains a discontinued child. The language badges, Kotlin, Java, TypeScript, Python, Shell Script, are pulled from shields.io and tell you what you would be compiling if you forked something. Note what is absent: there is no column for last commit date, no version number, and no security review. The status label is an editorial judgement, and the README does not document how it is assigned.

Using the list for a first reference pass

There is nothing to install. The project is a README, so the practical first step is reading it: the Homepage field points at a Gitea mirror on dawn.wine, where the same content renders as tables rather than raw Markdown. The repository itself carries no build step, no package manifest and no scripts, and the README gives no setup commands of any kind.

What the document does give you is a set of status markers you can scan for. The Android table uses them consistently: a row marked Discontinued or Broken can be ruled out before you open its upstream page, while Active (In beta) and still in development state tell you the project is not finished. The README states the collection is non-exhaustive, so a name missing from the tables is not evidence that the project does not exist. The fastest workflow is to read the tables for the platform you care about, note the two or three names marked Active, then leave the document and go read those projects' own repositories, because everything below the status cell is a one-line summary.

Where the catalogue stops being useful

The status column has no timestamp. A row marked Active tells you the maintainers believed it was active when they last edited that line, and the README does not say when that was or what evidence backed it. For a fast-moving category where the Android table alone lists Bunny, Vendetta, Lumi and ReCord as discontinued, that gap is the main limitation. You cannot tell from the document whether Active means a release last week or a repository that has gone quiet since the table was written.

The second gap is scope. The README calls itself non-exhaustive and the table of contents has sections for game console clients, other clients and third-party server implementations, but the visible portion of the document is dominated by mobile. Server implementations in particular are a different risk class from a client mod, and a single status vocabulary covering both flattens that difference. The Malware label is the exception: it is a real warning, but it is carried by a footnote, and the README does not describe the review that produced it. If your question is "is this safe to run with my account," this document gives you a starting list of names to investigate and nothing more.

Compared with searching GitHub topic pages yourself

The obvious alternative is the discord-client and discord-mod topics on GitHub, or a general search for "alternative Discord client." The difference is curation versus recency. Topic pages are generated from repository metadata, so they update automatically and will surface a project the day it is tagged, but they carry no judgement: a topic page will list an abandoned fork next to a live one with no distinction, and it will not tell you that one project is a fork of another. Discord3rdparties inverts that trade. It gives you lineage notes and a status label, and in exchange you accept a manual edit cycle and no freshness guarantee.

A second alternative is the upstream project's own README, which is authoritative for that one project but useless for comparison. The encyclopedia's real function is triage: it narrows a long list of names down to a short one, and then you go read the upstream documentation for whichever candidate survives. Treat the status column as a filter, not as a verdict.

Licence, maintenance and the cost of keeping a list current

The repository is licensed CC-BY-SA-4.0, which is a content licence rather than a software one, consistent with a project whose deliverable is documentation. If you copy the tables into your own page, the share-alike term applies to your adaptation; the LICENSE file is the authoritative text and this is not legal advice. The language badges in the tables point at shields.io, so any mirror you build inherits those external image dependencies.

The last push to the default branch was on 2026-09-24, four days before this writing, and the repository is not archived. Maintenance cost for a catalogue like this is editorial rather than technical: every fork, rename and abandonment in the Discord client ecosystem is a row that needs updating, and the Android table already shows how quickly that churn accumulates. There are no releases, so there is no version to pin. If you depend on the status labels, you are depending on a document that changes in place, and your only upgrade path is to re-read the diff.

Editorial conclusion

Adopt Discord3rdparties as a starting map if you are choosing between Android mods such as Kettu or Revenge, or checking whether a name you saw elsewhere is marked Discontinued or Malware. Do not treat it as a security audit: the repository lists no review methodology, and entries such as Bluecord are flagged only by a footnote. Before installing anything it names, verify the linked upstream repository yourself, confirm the status column still matches that project's own release notes, and read the LICENSE file for the CC-BY-SA-4.0 terms that apply if you republish the tables.

Frequently asked questions

Official sources

1. Discord-Client-Encyclopedia-Management/Discord3rdparties on GitHub
2. Issues
3. License: CC-BY-SA-4.0
4. Project website
5. README