--- title: "Fabric hosting in Brazil: a light, up to date server" description: "Fabric server hosted in São Paulo: mods that run on the server alone, short restarts, and what really changes when you come over from Paper and Bukkit plugins." url: "https://streethosting.com.br/en/minecraft-fabric" type: "page" language: "en-US" --- Light loader, early versions # Fabric hosting with short restarts and mods in place of plugins Fabric swaps the Bukkit ecosystem for mods, restarts fast and reaches new versions early. Here are the three points that decide the migration: restart, optimization and where your plugins end up. [See plans for Fabric](https://streethosting.com.br/en/minecraft-pro#plans) [Compare with Paper and plugins](https://streethosting.com.br/en/minecraft-paper) * São Paulo, Brazil * Anti-DDoS up to 400 Tbps * NVMe Quick answer Fabric runs mods, not Bukkit plugins, so EssentialsX and friends never load and optimization comes from mods like Lithium, Krypton and FerriteCore. In exchange the server restarts fast and follows a new version before the plugin forks do. ## Cheap restarts change the routine, not just the benchmark The Fabric loader is thin on purpose: it reads each mod fabric.mod.json, resolves dependencies and applies the mixins, with no heavy bytecode transformation step before the world loads. The effect shows up in your schedule, not in the TPS graph. When restarting costs little, updating a mod version stops being a job for the small hours: you warn the chat, stop, swap the jar and come back up before the community gives up waiting. When it costs minutes, the fix waits for the next window. ## Each performance mod solves one class of problem The list going around the forums is not a pile of generically fast mods. Installing all of them at once, without knowing which one hurts on your server, gets in the way of the diagnosis later. Lithium rewrites tick logic, meaning mob AI, pathfinding and redstone, without changing game behaviour. Krypton lowers the per packet cost on the network layer, which weighs more the more people are online. FerriteCore cuts memory by deduplicating blockstates. C2ME parallelizes chunk generation and reading, the classic bottleneck of a new world. Order matters more than the list: run spark, see whether the time goes into entity ticking, chunk generation or garbage collection, and only then choose. A chunk optimizer on a server stalled by a mob farm changes nothing. ## A Bukkit plugin does not load, and there is no clean workaround Fabric does not implement the Bukkit API. EssentialsX, Vault and PlaceholderAPI are not incompatible with the version, they simply have nowhere to plug in, and the jar sitting in mods/ does not even raise an explanatory error. LuckPerms and WorldEdit survive because they publish their own build for the loader. Everything else becomes a separate mod, each with its own file under config/. Hybrid layers expose the Bukkit API on top of Fabric, work in the demo and break in the corners: a plugin that touches NBT or packets finds the edge of the emulation. If you depend on ten plugins, the honest answer is to stay on Paper. ## A vanilla client still gets in, with the right mods A mod that adds a block, an item or a dimension has to be on both sides, and anyone who did not install it is refused at the handshake. A mod that only optimizes the server asks nothing of the client, the case of Lithium, Krypton, FerriteCore and spark itself. Out of that comes an underexplored design: a Fabric server carrying only optimization and administration mods, with the community joining on plain vanilla Minecraft, no install tutorial needed. Infrastructure ## What is already sorted * Fabric Loader and Fabric API on the version your mod set requires. * The mods/ folder over the panel and over SFTP, so you swap a jar without opening a ticket. * Restart from the panel, since Fabric has no restart-script like spigot.yml does. Use cases ## Who usually picks Fabric * A server that wants to be on the new version within the first weeks. * A closed SMP with few content mods and a light client. * A technically vanilla server that only wants the optimization toolkit. Optimization ## How the server gets tuned * Mods chosen by what spark points at, not by the list that is trending. * Simulation distance and view distance kept apart: one weighs on the tick, the other on bandwidth. * A fixed heap with headroom outside it, so the collector does not compete with the tick. Tech sheet ## Where Fabric runs here Numbers from the line, no estimates. Performance line entry R$ 54.00 per month 4GB DDR5, 30GB NVMe and 300% of CPU on a Ryzen 9 9950X. Paying yearly R$ 48.60 per month 4GB on the annual cycle, 10% below the monthly price. Scaling ceiling 64GB From 4GB to 64GB with no manual migration. Location São Paulo, Tier III datacenter A national network, which is what holds the ping down in PvP and parkour. Comparison ## Fabric against Paper for someone already running plugins What you gain and what you lose by switching ecosystems. | Criterion | Fabric | Paper | | ------------------------------- | ------------------------------------------------------- | ---------------------------------------------------------------- | | Bukkit plugins | They do not load: the API does not exist on the loader. | The base of the ecosystem: EssentialsX, Vault, PlaceholderAPI. | | Content mods | Supported, installed on the server and on the client. | Out of reach without a hybrid layer. | | Configuration | server.properties plus one file per mod under config/. | bukkit.yml, spigot.yml and paper-global.yml. | | Changing mechanics without code | It comes from the mods. With no mod, it is vanilla. | Hundreds of ready configuration keys. | | New version | It arrives early, but each mod needs its own build. | It arrives once the fork stabilizes, with the plugins alongside. | Standing out through economy and rank plugins calls for Paper. Standing out through content and a recent version calls for Fabric. Checklist ## Checklist before opening the Fabric server It works for a new project and for anyone leaving Paper. * Confirm every mod has a build for the target version. The most behind one sets the date, not the loader. * Download the Fabric API on that same version: a good share of mods fail at boot without it. * Separate what runs on the server alone from what the client has to install, before you publish the IP. * Set simulation-distance and view-distance separately in server.properties. * Generate the world before opening and put spark up on day one. ## Frequently asked questions 01 Do my Paper plugins work on Fabric? No. Fabric does not implement the Bukkit API, so EssentialsX, Vault and PlaceholderAPI never load. LuckPerms and WorldEdit have an official build and keep serving. The rest has to become an equivalent mod. 02 Does the player need to install anything to join? It depends on the mod. The ones that only optimize the server, like Lithium and Krypton, ask nothing of the client. The ones that add blocks, items or dimensions have to be on both sides. 03 How much RAM does a Fabric server need? The loader costs little. What pushes memory up is the number of content mods and of loaded chunks. A server focused on optimization runs fine on the 4GB entry plan. 04 Can I run mods and plugins on the same server? There are hybrid layers that expose the Bukkit API on top of Fabric, but they fail in edge cases and support ends up in no man land. If you depend on many plugins, the stable answer is Paper. Keep reading ## Guides that back this decision Material from the archive, written for a server in production. * [Forge or Fabric: which to choose A mod catalog against lightness, with the decision spelled out.](https://streethosting.com.br/en/guides/minecraft/forge-vs-fabric-minecraft-server) * [Mods and plugins together on the server What happens when you try to mix the two ecosystems.](https://streethosting.com.br/en/guides/minecraft/minecraft-mods-and-plugins-together) * [The spark profiler for finding lag How to read the report before installing an optimization mod.](https://streethosting.com.br/en/guides/minecraft/spark-profiler-minecraft) * [Updating the server version A procedure with backup and testing, useful at a version turnover.](https://streethosting.com.br/en/guides/minecraft/update-paper-minecraft-server) 4.7/5 on Trustpilot Money-back guarantee Activation in 60s Premium support Trusted by 2,500+ customers ## Coming from Paper without a scare * A map of your plugins to their mod equivalents, with a warning about what has no replacement. * World migration between loaders, with a backup before any conversion. * A plan change with no reinstall once the list grows. [See plans for Fabric](https://streethosting.com.br/en/minecraft-pro#plans) [Contact support](https://streethosting.com.br/en/contact) Fabric rewards whoever installs little and installs with judgement. Send us your mod list and we will check version compatibility before you open up to the community.