Describe the bug:
Ok, this one's a strange one...
Instead of getting leaf piles, I get other random objects. If I have other mods installed I get their blocks there. If not I get charred fence gates.
Only happens when running on a server. Same mods, works fine in SP.

Versions: (BEFORE SUBMITTING A BUG REPORT, make sure you have the most up-to-date versions of Immersive Weathering, Moonlight Lib and Supplementaries)
Minecraft version: 1.19.2
Immersive Weathering version: 1.1.4
Moonlight Lib version: 2.1.4
Fabric API / QSL / Forge version: 0.14.9

Other mods:
- automodpack 2.4.1
- bookshelf 16.1.11
- collective-fabric 5.14
- creativecore 2.8.5
- fabric-api 0.64.0+1.19.2
- fabric-language-kotlin 1.8.5+kotlin.1.7.20
- forgeconfigapiport 4.2.6
- iceberg 1.0.46
- immersive_weathering 1.19.2-1.1.4
- moonlight 1.19.2-2.1.4
- Prism 0.5.5-1.19.2
- puzzleslib 4.3.12
- yungsapi 1.19.2-Fabric-3.8.2

Logs:
latest.log

To Reproduce:
Steps to reproduce the behavior. Format it as a numbered list of steps.

1. Install these mods on a server and connect?

Expected behavior:
leaf piles spawning under trees, not random items

Screenshots:

Additional info:
I've been in the process of finding what causes this issue all day. I've stripped my mods back to singleplayer mods. I'll keep testing to see if it's a conflict with one of the libs/apis I have installed

Also, the piles (and random things) seem to spawn super fast.

OMG, I finally found the issue. I thought it had to be server side as it was spawning blocks that I could interact with, however, I noticed the issue only happened when I was using my client-side only modpack. Turns out that I had a non client-side mod in that pack (Advancement Frames). I guess the issue was only happening client side, and not actually on the server at all. After installed Advancement Frames mod on the server as well, everything seems to be back to normal

I was mistaken, it's happening again now that I have readded my mods (and am running no addition mods on the client).
Here's a log from my client
latest.log

automodpack is the cause, which I would have never guessed seeing as it's a mod updater. I thought it 'should' do nothing to the actual game to affect mods. But I have tested (also with others) for over a day now and automodpack was the cause.