Modrinth · Fabric

Scalable on your Minecraft server

Scalable runs on Minecraft servers with Fabric. Order your server, set the loader in the panel and install the mod with one click in the mod browser.

Get the most out of your hardware. Scalable optimises and puts the most important things first

Downloads
1.8K
Author
raderth
Loader
Fabric
Minecraft
1.21.11 – 26.3
Updated
–

Screenshots

What Scalable looks like

Images: Scalable on Modrinth, published by the project team.

Setup

Install Scalable on your server

The server and players need the same loader and Minecraft version. Back up the world before adding or updating mods.

  1. 01

    Configure

    4 GB of RAM is preselected. You choose the term and add-ons and pay by credit card or PayPal.

  2. 02

    Set the loader

    In the panel, set the server software to Fabric and choose the matching Minecraft version, for example 26.3.

  3. 03

    Install the mod

    Search the mod browser for “Scalable” and install the release for your loader. Alternatively, upload the .jar to the mods folder via SFTP. Required dependencies are listed on the project page.

  4. 04

    Connect

    Scalable is not needed on the client. Players connect using the server address from the panel.

On the server
Required
On the client
Not needed
Loader
Fabric
Minecraft
26.3, 26.1.2, 26.1.1 +2 more
License
MIT License

The panel

Install mods, find errors.

Real screenshots from the Mado panel. Both come with every Minecraft server.

Mod browser

Modrinth and CurseForge, right in the panel.

The browser filters by your Minecraft version. Install mods with one click, without uploading .jar files.

Browser in the Mado panel with search, a CurseForge or Modrinth source switch and install buttons.

AI crash analysis

When a mod crashes, the analyzer reads the log.

Mods often fail on a wrong loader version, Java version or missing dependency. The analyzer names a likely cause and suggests a fix.

Optimization page in the Mado panel with the AI Log Analyzer enabled and a “Server Crashed” notice with an “Analyze Now” button.

Releases

Published releases

Pick the file that matches your server’s loader and Minecraft version. The server and players need the same release.

Scalable · Modrinth
Original description by the project author

A header image with a logo and the word scalable


A lightweight server-side optimization mod for Fabric that keeps your server running smoothly under load by intelligently budgeting work.

Scalable naturally "scales" the server performance. It works great for large servers or a low budget.

The result is a server that stays responsive even when it's struggling.

Unlike similar mods, vanilla mechanics stay intact and the mod wont be noticed by even the most observant players under normal conditions.

Installation

Requires the latest version of Fabric Loader and Fabric API. Drop the .jar into your mods folder. No client installation required.

Please let me know if you have issues on github by making an issue: https://github.com/raderth/Scalable/issues


What does Scalable actually do?

At the start of every server tick, Scalable starts a timer. Chunk ticking and entity ticking proceed normally. But if the budget runs out mid tick, remaining work is deferred to the next tick rather than causing the entire tick to overrun.

Scalable sets a time limit and stops when it's hit. The unprocessed remainder is picked back up next tick. Under normal load, everything is ticked every tick as usual. Under heavy load, less important things (far away chunks, distant entities) are delayed, but the things closest to players stay responsive.


Chunk ticking

Chunks are sorted and processed in this order each tick:

  1. Deferred chunks from the previous tick (carried over work gets priority)
  2. Priority chunks those loaded by portals, ender pearls.
  3. Player-assigned chunks remaining chunks are distributed across players using a round-robin scheduler, with each player's queue sorted by proximity to their projected future position (based on their current velocity).
  4. Unclaimed chunks any ticking chunks not assigned to a specific player

If the budget runs out before all chunks are processed, the leftovers are deferred.

Entity ticking

Entities are also budget-aware and player-assigned:

  1. Players are always ticked first (priority queue)
  2. Other entities are assigned to their nearest player and ticked in round-robin order
  3. If the budget runs out, remaining entities are simply skipped for that tick

This means that even under heavy load, players and their immediate surroundings are always prioritized. You can still open inventories, interact with the world, and move around smoothly. Similar to how mods like TT20 keep the server interactive even when it's overloaded. The advantage here is that the game is actually still running in a broader sense.


Configuration

Config file is at config/scalable.json and is created automatically on first run.

{
  "budget_ms": 40,
  "max_deferred": 2048
}
Field Default Description
budget_ms 40 Milliseconds per tick available for chunk and entity ticking. Set to -1 for automatic mode (also 40ms).
max_deferred 2048 Maximum number of chunks that can be held in the deferred queue at once. Excess entries are dropped (oldest first).
passive_collision_interval 5 Each mob still runs the pass once every 5 ticks
In-game commands

All commands require operator.

Command Description
/scalable budget auto Switch to automatic budget mode (40ms)
/scalable budget <ms> Set a fixed budget in milliseconds (1–50)
/scalable profile Show current budget mode, MSPT, and TPS
/scalable deferred <max> Set the max deferred chunk queue size (0–65536)
/scalable collisions off|always|adaptive Set how often entity collisions are handled

Changes made via commands are saved to scalable.json immediately.


Limitations

Note: Scalable smooths out lag spikes and buys your server breathing room. It won't eliminate lag caused by something consistently eating your entire tick budget (e.g. extreme entity counts), but it will make things significantly more bearable while you address the root cause.

  • Entities are not deferred between ticks if the budget runs out mid-entity-loop, those entities simply don't tick that frame. Deferred entity carry-over is not yet implemented.
  • Consistent heavy lag from entities or other non-chunk sources may still cause TPS drops until those sources are addressed.

FAQ

Scalable questions

Question not listed? Ask our team.

Scalable server crashes on startup – what to do?

Common causes: the loader or Minecraft version does not match the mod file, a dependency is missing, or RAM is too low. Check the log (latest.log) for “OutOfMemoryError”, “Mixin” or missing mods. At Mado, the AI crash analysis reads the log and suggests a cause. You can change the loader and version in the panel.

Which loader does Scalable run on?

According to Modrinth, Scalable supports Fabric for Minecraft 26.3, 26.1.2, 26.1.1.

How much RAM does a server with Scalable need?

As guidance, 3–4 GB for a server with this mod. This is an estimate, not a measured minimum. More mods, many players and long view distances need more. The spark profiler shows whether a mod is costing tick time.

Ready for your server with Scalable?

4 GB of RAM from €8.00 per month. 35% off your first month with MADO35.

Order server