Live dashboard widgets, the Metabans plugin, in-game @report, and ban management that syncs across every server you run — for both Java and Bedrock communities.
Both. We use RCON over TCP for Java (vanilla, Paper, Spigot, Forge, Fabric) and the same console for Bedrock instances that expose a compatible RCON port. Players from either edition flow into the same reputation graph.
Yes — Metabans is plugin-agnostic. We connect over standard RCON, so any Minecraft server software that ships with /op-style admin commands works out of the box. The optional Metabans plugin (from the plugin registry) adds richer features (live dashboard widgets, in-game @report routing, ban-list sync) without replacing your existing plugins.
Yes. Add as many as you need; they all surface in the same dashboard, share the same ban-list, and feed the same cross-server reputation record. The dashboard widgets aggregate across them automatically.
A community ban is issued by your staff and applies only to your community’s Minecraft servers. A Metabans network ban is enforced when a player joins any connected Metabans community’s servers. Metabans staff issue network bans on a community’s request or after review; anti-cheat issues one automatically only for its strongest detection, and Metabans staff review every one. The network registry is a separate public list, not a copy of all community bans, and each network ban message includes its own appeal link.
Free Scout plan, no credit card, set up in under two minutes.