Ensuring a Stable and High-Performance Setup

FlameCord is engineered for peak performance and compatibility. As a BungeeCord fork, it works seamlessly with the vast majority of plugins like BungeeGuard, AuthMeBungee, and various portal plugins. However, achieving a perfectly stable and fast server requires understanding a few key best practices, particularly regarding plugin placement and potential conflicts.

The Golden Rule: ViaVersion on Spigot, Not the Proxy

This is the most critical configuration advice for any proxy server. While it may seem convenient to install ViaVersion (and its related plugins like ViaBackwards) on the proxy, this is a major performance bottleneck.

  • ❌ Incorrect Setup: Do not install ViaVersion on FlameCord (or any BungeeCord proxy). On a standard BungeeCord, this will cause significant server lag as the proxy struggles to translate packets for every single player. On FlameCord, our optimizations mean it won't even work correctly.
  • ✔️ Correct Setup: You must install ViaVersion directly on your backend Spigot (or Paper, Purpur, etc.) servers. This allows each backend server to handle the packet translation for its own players, which is infinitely more efficient and scalable. This setup works perfectly with FlameCord.

Potential Conflicts: Packet-Modifying Plugins

A small number of plugins heavily modify or listen to packet events on the proxy. In some cases, these deep-level modifications can interfere with FlameCord's performance and security optimizations. This is not a guaranteed incompatibility, but it's the first place to look if you experience unexplained issues.

  1. What are Packet Event Plugins? These are often complex anti-cheat systems, custom anti-bot solutions (which are redundant with FlameCord), or plugins that introduce unique gameplay mechanics by directly manipulating Minecraft's data packets.
  2. Symptoms of a Conflict: If you experience strange connection issues, rubber-banding, or specific features not working, a packet-level plugin conflict is a likely cause.

Troubleshooting Steps

If you encounter unexpected behavior, follow this diagnostic process:

  1. Check ViaVersion: First and foremost, confirm that ViaVersion and its addons are NOT in your proxy's `plugins` folder. They should only be on the backend servers.
  2. Isolate Packet-Event Plugins: Temporarily remove any plugins that you suspect might be heavily modifying packets (e.g., complex anti-cheats). Restart the server and see if the issue is resolved. If it is, you've found the conflict.
  3. Seek Updates: Ensure all of your plugins are fully up to date. A conflict you're experiencing may be a known bug that has already been fixed by the plugin author.
  4. Join Our Discord for Support: If you've followed these steps and are still facing issues, our support team on Discord is available to help you pinpoint the problem.