Quick answer
FlameCord is travertine/waterfall/bungeecord-family proxy fork. Add exploit mitigations, security-oriented features, and functionality to the older BungeeCord-family proxy stack.
| Developer / maintainer | Iverly / FlameCord maintainers |
|---|---|
| Software type | Travertine/Waterfall/BungeeCord-family proxy fork |
| Upstream / lineage | Built on Travertine, which was based on Waterfall/BungeeCord lineage. |
| Current status | Verify version fit |
| Best fit | Existing networks that specifically need FlameCord’s security/legacy protocol features and already understand the BungeeCord-family stack. |
Who develops FlameCord?
Iverly / FlameCord maintainers develops or maintains this project. Built on Travertine, which was based on Waterfall/BungeeCord lineage.
This matters because “Minecraft server software” covers very different kinds of projects. Some are direct forks of Paper, some are mod loaders, some are compatibility layers, some are proxies, and some reimplement the server from scratch. The lineage above tells you what ecosystem, APIs, and operational assumptions carry over.
What is its main goal?
Add exploit mitigations, security-oriented features, and functionality to the older BungeeCord-family proxy stack.
A good reason to choose a server implementation is that its design goal matches a real requirement you have. Switching only because a fork is advertised as faster, more configurable, or more modern usually creates extra compatibility work unless you can name the problem it solves for your server.
How is it different from normal Minecraft?
FlameCord is a proxy, so it does not implement Vanilla game mechanics.
“Vanilla compatibility” can mean several things: the same client protocol, similar gameplay, identical redstone/farm behavior, the same world format, or simply the ability for an unmodified client to join. Those are not equivalent. For technical survival, modded worlds, or long-lived production servers, test the exact behavior you depend on.
How does it differ from its upstream or related forks?
Its lineage is BungeeCord → Waterfall → Travertine → FlameCord. That means it inherits an ecosystem whose PaperMC branch (Waterfall) is discontinued, even though FlameCord itself may still be maintained separately.
Fork relationships are especially important for plugins and configuration. A downstream fork usually inherits much of its upstream API, but extra patches can change internals, scheduling, defaults, and edge-case mechanics. The closer a plugin is to undocumented internals, the less useful a generic “Paper-compatible” or “Bukkit-compatible” label becomes.
What type of server is FlameCord good for?
Existing networks that specifically need FlameCord’s security/legacy protocol features and already understand the BungeeCord-family stack.
For a new server, start with the simplest software that meets the requirement. More layers—especially hybrid plugin+mod stacks or multithreaded forks—mean more combinations to test when Minecraft, Java, plugins, or mods update.
Plugin, mod, and ecosystem compatibility
BungeeCord-family concepts/plugins may apply, but exact FlameCord behavior and supported versions should be checked against its current documentation/build.
Always match extensions to the exact Minecraft version and software family they target. A JAR being Java does not make it universally compatible, and a plugin/mod loading successfully does not prove every code path is safe.
Stability and project maturity
FlameCord is specialized and based on legacy proxy lineage. That does not automatically make it unusable, but new networks should compare it with actively maintained modern alternatives such as Velocity.
Current version note: The public repository describes FlameCord as a patch/fork around Travertine and highlights exploit fixes and additional functions.
MSH does not assign a numeric stability score. Release status, maintenance activity, official warnings, supported Minecraft versions, architecture, and ecosystem compatibility are more useful than a single rating. A mature project can still be the wrong fit, while a beta project can be useful for a team that deliberately accepts the risk.
Before switching to FlameCord
Version-specific decision: FlameCord belongs to a BungeeCord/Waterfall-related proxy family and is not a Minecraft world host. Some public repositories describe different lineages or releases, so the exact distribution and maintenance record must be checked.
- Select the maintained project and download page you actually plan to use; do not assume unrelated FlameCord forks are the same distribution.
- Configure listener, backend address, authentication/forwarding and restricted access to every backend before public DNS points to the proxy.
- Test connecting through the proxy and trying the backend directly; direct outside access should be blocked at the network layer.
- Review proxy plugins for BungeeCord-family compatibility; Velocity plugins use another API and are not drop-in JARs.
Do not infer current protocol/security support from the old Waterfall/Travertine README text alone. Verify the specific FlameCord build you intend to deploy.
If the server contains modded blocks/entities, switching away from the loader or mods that created that data can permanently damage a world. If the change involves proxies or threading models, compatibility problems may appear only when players move between servers or when plugins access data concurrently.
Official references
These primary project sources were checked on September 23, 2026. Software status changes quickly, so the linked project documentation should win over this article if a newer release changes support or requirements.
Related server software
Help us improve this article
Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.