no particle
NoParticle blocks all particles by default, only shows whitelisted ones, supports /again hot-reload, /txt particle list export, and offers source-level interception plus Tinkers' Construct optimization.
About this Mod
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).
Hot‑reload command: Type /again to reload the whitelist instantly – no need to restart the game.
/txt command: Exports every encountered particle to config/particle_list.txt, making it easier to build your whitelist.
Tinkers' Construct optimization: Completely disable TConstruct’s particle generation via a config option (default: on, requires restart, and when enabled the whitelist is bypassed for TConstruct).
Server‑side benefits: Intercepts particle network packets and prevents particle objects from being created – saves bandwidth and reduces CPU load.
Dependency: Requires an external Mixin loader such as MixinBooter or FermiumBooter.
Performance boost: Drastically reduces unnecessary particle rendering, improving FPS – especially useful on low‑end machines or large modpacks.
Good news for players plagued by lag from TConstruct’s insane damage‑stacking particle spam!
Available Versions
How to Install no particle on Your Server
Order Server
Order a Minecraft Java server with at least 3 GB RAM (4 GB recommended).
Set forge Loader
In the panel under "Egg", select the forge loader and matching Minecraft version (1.12.2).
Install Mod
Open the mod browser in the dashboard and search for "no particle". Click "Install" – done! Alternatively, upload the .jar via SFTP to the /mods folder.
Compatibility
Mod Loaders
Minecraft Versions
1.12.2
Server-side
~ OptionalRecommended RAM
4 GB(min. 3 GB)Frequently Asked Questions
no particle server crashes on startup – what to do?
Most common cause: wrong forge version or insufficient RAM. Check the server log (latest.log) for "OutOfMemoryError" or "Mixin" errors. With Mado Hosting: ensure at least 3 GB RAM is allocated and the loader matches the mod version (1.12.2). You can switch loaders with one click in the panel.
Is no particle compatible with forge?
no particle officially supports forge for Minecraft 1.12.2. The Mado dashboard automatically detects incompatible loader combinations.
Server lagging with no particle – how to optimize performance?
Recommended RAM: 4 GB (per 8 players). Use /spark profiler to check if no particle consumes the most tick time. Common fixes: reduce server view-distance to 8-10, install "performant" or "starlight" as supplementary mods on Forge. With Mado Hosting, your server runs on NVMe SSDs with dedicated CPU cores for minimal latency.
Similar Mods
Rent Modded Server
Install no particle with just one click on your server.