Back to mods
Perfomant Boom project artwork

CurseForge · Minecraft mod

Perfomant Boom

Schedule large explosions across server ticks, with a shared terrain engine.

Choose a version Pick your version below, then grab the matching file.

Quick answer

Which Perfomant Boom release should I use?

Updated last month
Latest stable file Perfomant Boom 1.1.3 - fabric 1.20.1
Game version 1.20.1
Loader Fabric

Perfomant Boom 1.1.3 - fabric 1.20.1 targets 1.20.1 with Fabric. The project page does not say whether this file belongs on the client, dedicated server, or both. All 2 required mods have matching files.

Where it goes

Is Perfomant Boom required on the client, server, or both?

The project page does not say whether this file belongs on the client, dedicated server, or both.

Client Source doesn’t say
Dedicated server Source doesn’t say
Loader for this release Fabric
Required install it here Optional supported, not mandatory Not supported do not install here Source doesn’t say do not assume

The source does not explicitly classify this release as client-only or server-only.

What else does Perfomant Boom 1.1.3 - fabric 1.20.1 need?

Perfomant Boom 1.1.3 - fabric 1.20.1. Change the file and its required mods may change too.

All 2 required mods have matching files

Install Fabric API, Architectury API first. We found matching files for this game-version and loader setup.

Fabric API Needed by Perfomant Boom 1.1.3 - fabric 1.20.1
required
Matching file found Matched file: [1.20.1] Fabric API 0.92.12+1.20.1
Architectury API Needed by Perfomant Boom 1.1.3 - fabric 1.20.1
required
Matching file found Matched file: [Fabric 1.20(.1)] v9.2.14

We only count dependency files that match this setup. A file for another loader does not fill the gap.

Before you install it

Add Perfomant Boom without breaking your instance.

Built for Perfomant Boom 1.1.3 - fabric 1.20.1. Pick another file and the loader, install side or required mods may change.

  1. 01

    Stick to this file

    Use Perfomant Boom 1.1.3 - fabric 1.20.1. It targets 1.20.1 with Fabric; another release may have different loader, side or dependency requirements.

  2. 02

    Bring the mods it needs

    Install Fabric API, Architectury API first. We found matching files for this game-version and loader setup.

  3. 03

    Put it on the correct side

    The project page does not say whether this file belongs on the client, dedicated server, or both.

  4. 04

    Pick the file you checked

    Use the “Get this file” button beside Perfomant Boom 1.1.3 - fabric 1.20.1. It opens that exact file at the source.

About this project

What does Perfomant Boom add?

Perfomant Boom

Large explosions, scheduled across server ticks—and a shared terrain engine for mod integrations.

Perfomant Boom provides an administrator explosion command and reusable terrain operations. Its scheduler spreads calculation and block changes across ticks to avoid doing the entire scheduled explosion in one burst.

Features

  • Queue explosions with the operator command /boom <power>.
  • Spread explosion work across server ticks while keeping live-world access on the server thread.
  • Support terrain clearing, fluid cleanup, and boundary repair for mods that use the shared API.
  • Integrate the Java API into your own mod while retaining control of effects, damage, timing and saved progress.

Performance vs vanilla

Perfomant Boom v1.1.3 real-game benchmark against vanilla: active explosion time, heaviest server tick, server-thread CPU work and memory allocations on Fabric and Forge 1.20.1.

Measured on 30 September 2026 using real Minecraft 1.20.1 Fabric and Forge dedicated servers and graphical clients, with power-10 explosions and drops disabled for both engines. Each loader used three warmup pairs and five measured pairs, matching seeds and alternating order. Exact crater, client block/light state, clean shutdown and save/reload checks passed.

In this fixture, Boom reduced the median heaviest server tick by 81–85% and server-thread memory allocations by 28–31%. These results describe this workload and machine; they are not a universal speedup or FPS claim.

Lower bars are better. The black whiskers show the middle 50% of measured results, not the minimum and maximum. CPU and memory measurements include observed server ticks and aftermath work. Memory allocations are cumulative bytes created, not peak RAM usage. This Windows host's CPU counter reports coarse 15.625 ms increments: matching CPU readings would not prove identical usage, and this chart cannot establish precise CPU savings.

v1.1.3 reduces repeated position allocations and chunk lookups. Median allocations were 11–14% below the archived v1.1.2 runs in this fixture; the separate sessions do not establish a controlled version-to-version timing gain.

See the benchmark data and reproduction steps for machine details, raw samples and measurement scope.

Try it

In a disposable test world with cheats enabled, run:

/boom 4

The explosion is queued at the command's execution position. Power accepts 1–500, including decimal values. Power is explosion strength, not a guaranteed crater radius; resistant blocks and the surrounding terrain affect the result. Start small.

The command requires game-master/operator permission. Command blocks or /execute positioned can supply a different execution position.

Installation

Choose the file matching your exact Minecraft version and loader.

Minecraft Loader Required mods Java
1.20.1 Fabric Fabric API, Architectury API 9.2.14+ 17
1.20.1 Forge Architectury API 9.2.14+ 17
1.21.1 Fabric Fabric API 21
1.21.1 NeoForge None 21
26.1.2 NeoForge None 25

Fabric targets require Fabric Loader 0.18.4 or newer. For integrations, follow the consuming mod's client/server requirements and install its additional dependencies. Boom's command works independently.

What to expect

Ordinary TNT, creeper, and other Minecraft explosions are not automatically replaced. Boom processes its command and integrations that explicitly use its engine.

This is not a promise of lag-free explosions or a universal speed multiplier. Chunk loading, lighting, and block callbacks can still take time. General vanilla explosion loot behavior is not reproduced, and custom explosion hooks or protection mods may behave differently. Use backups before destructive commands; Boom is not a protection system.

Queued ordinary Boom explosions are not resumed after a server restart. Completed block changes persist through normal saves. Integrations manage their own saved progress separately.

Help and feedback

Source and documentation · Report a problem

Include Minecraft and loader versions, Boom version, command power, installed integrations, and the crash report or latest log. For performance reports, describe the terrain and separate server tick delays from client rendering problems.

Created by NsTut. Licensed under the MIT License.

Project description from CurseForge.

Pick your setup

Perfomant Boom by Minecraft version and loader

Choose the version and loader you play, then open the matching release.

5 available setups

Check the dependencies, then try the file in a copied instance before changing a world you care about.

Recent files

Perfomant Boom versions and loaders

20 of 20 releases match

Looking for an older file? The official CurseForge project page is in Resources.