ModsFinder

no particle

by f19882350305

No Particle hides most particle effects in Forge 1.12.2 games, letting players keep only the particles listed in a whitelist file.

ForgeClient or server, optionalMIT LicenseOpen source1.12.2

What it does

Particles are disabled as soon as a player enters the game. Only particle IDs named in the config file particleinterceptor.cfg remain visible, such as minecraft:flame or minecraft:explosion, and particles added by other mods appear only when their IDs are added to the list. Typing a command reloads the whitelist without a restart, although changes to the mod's core settings still need a restart of the game.

A further default option completely disables particle generation from one specific building-tool mod, with a bypass for whitelisted particles. On a server, interception happens at the network packet level, so particle objects are never created and the bandwidth spent on them is saved. The mod depends on a separate Mixin loader to run. Files are published for Forge 1.12.2 under the MIT License, and the source code is public.

Key features

  1. Whitelist of particle IDs

    A config file lists the particle IDs that remain visible, and every other particle is hidden.

  2. Hot-reload command

    Entering a command reloads the whitelist immediately, so the list can be tested in play.

  3. Single-mod particle filter

    An option turns off particle generation from one building-tool mod entirely, which removes its damage-stacking particle spam.

  4. Server-side interception

    Particle network packets are stopped before particle objects are created, which saves bandwidth and reduces CPU load.

Compatibility

Latest build for each game version and loader.

1.12.21.4
ReleaseBetaAlphaNot available

Only full game releases are shown. This mod publishes no snapshot builds.

Use cases

Low-end machines

Players with weaker hardware can remove unneeded particle rendering to improve frame rate in large modpacks.

Modpack servers

Server owners can cut the bandwidth and CPU cost of particles for every connected player.

Who it’s for: Players running large Forge 1.12.2 modpacks on modest hardware, and server owners who want to reduce particle traffic.

Questions

Does No Particle need a Mixin loader?

Yes. A separate Mixin loader must be installed alongside the mod for it to work.

Does a change to the whitelist need a restart?

No. Typing the reload command applies whitelist changes at once, but the game must be restarted for the mod's core settings to take effect.

Which side does No Particle need to run on?

It is optional on both sides: the client or the server can run it, and neither needs it. It targets only Forge 1.12.2.

In the catalog

no particle is one of 3,545 Optimization mods on ModsFinder, and one of 1,441 Optimization mods for Forge. 2,920 mods support Minecraft 1.12.2.

More from f19882350305

All projects

Similar mods

What the author says

Default behavior: All particles are disabled upon entering the game – no flame, smoke, or any mod‑added particles will appear. Whitelist system: Use the config file particleinterceptor.cfg to define allowed particle IDs (e.g., minecraft:flame, minecraft:explosion).
f19882350305, on the Modrinth page

Official listing

Owner
f19882350305
Published
2026-05-17
Updated on Modrinth
2026-05-31
Facts verified
2026-10-15

Tags