Allow anonymous analytics?

Our cookieless analytics show us which features get used and store nothing on your device. We never sell your data or use it for advertising.

Privacy choices

Choose what ModDex may collect. You can change this anytime from Privacy choices in the footer.

Read the full privacy policy

Strictly necessary Required for the site to work: login sessions, security tokens, and abuse prevention. Always on and cannot be disabled. Always on
Analytics Cookieless analytics through PostHog's EU servers, used only to see which features get used. Nothing is stored on your device, and the anonymous visitor ID resets every day. Needs your consent because usage data goes to a third party. Never used for advertising or profiling. Off by default in the EU and UK.

Waterfall Particles

Quick rating

Community listing page, reviews may not be monitored by the author.

How listings work Are you the author?

Waterfall Particles

By ThirtyFangsOwner

No reviews yet

This datapack adds particles to waterfalls

Mod Loaders
Minecraft
26.3 26.2
Shockbyte server hosting: 35% off your first server with code MODDEX35 (opens in a new tab)

About

Description

What does it do

The waterfall particles are being displayed every 0.5 seconds on a 20 blocks radius around every players!

Is it advised on servers?

If your server has a good processor and doesn't use too many datapacks it should be ok! It could only causes client lag if several players are in the same area near a waterfall (waterfall at spawn for example) because each players would display particles to each others repeatidly in a similar area causing a massive amount of particles.

Can I use it on a singleplayer world?

It shouldn't be an issue if you have a not too old processor. When used in singleplayer, you may have a performance impact depending on how recent your computer is, because the main function has 18000 commands, but the lag comes from the task of running commands, not from the particles. The timer prevents lag from particles in singleplayer. FPS aren't impacted, only processor usage.

Possible console error

If you get error in the console regarding max commands allowed per tick, run /gamerule max_command_sequence_length 100000 or more (default to 65536). You will only get this error if you use other datapacks.