Describe the bug you're experiencing

Minecraft Version: 1.20.1
Forge Version: 47.3.0
Mod Verion: betterchunkloading-1.20.1-5.3.jar

Modlist: https://1drv.ms/u/s!AvHk7krLNwvthIpwwBk_XGORplOkpg?e=0qhstM

Note: I don't think the log is particularly relevant to this issue, but I've shared it below anyway.

To summarize, machines that remove water source blocks (in this case, the mechanical pump from Create) will halt when chunkloading with /forceload or a chunkloader from Create: Powerloaders because the water source block will not be replaced.

Expected behavior: water in forceloaded chunks should not rely on randomtick and will still create water source blocks when players are not nearby.

Bug: water will not flow, even when a player comes into render distance of the block, and it must be updated manually with a bucket or block.

Reproducability

Place a create steam engine or other fluid voiding block and create a pipeline entering it powered by a mechanical pump facing into a water source block. Surround it with how ever many water source blocks you want horizontally (I didn't test surrounding it entirely), /forceload add ~ ~ ~, and then go out of render distance for 2-5 minutes (ensure testing is not done is spawn chunks). Return to find the pipeline inactive and the water below it in a flowing state.
I assume this works with other mods that pull water source blocks, such as Embers: Rekindles pumps, but I did not test them: Create is the most popular mod that folks will be using when they encounter this bug.

Mod up to date

• Before submitting this issue I updated to the newest version and reproduced it

Minecraft version

1.20.1

Modloader version

Forge

Logs

https://1drv.ms/u/s!AvHk7krLNwvthIpyK8gVEtfyKze5AQ?e=kcbD3q

It's just occurred to me that there's probably a task in the config I could turn off to prevent this bug. I value the optimizations that this mod provides, so I'm loathe to, but I also adore easy fixes. If that's a possibility, is there a process within the config I can disable to prevent this? (such as enableSmartPostProcessing)

ye smartPostProcessing is interfacing with water, it moves the postprocessing from directly on chunk gen to a later point after surrounding chunks got loaded, to avoid loading those on demand.

The new fluid optimization is pretty simple, its just caching the gamerule, might be that it needs the initial state earlier, gonna check that

uploaded version 5.4, with that + create I couldnt reproduce your error^^
If it still happens on that version for you it might be another mod entirely(performance mods often alter chunk ticking stuff) or a compat issue between betterchunkloading and another mod in that pack