Blocking the flow of fluids once and for all. Is it even possible?

[SkenonS]

EDIT: Not Possible(At least in 1.12.2), consider this closed

 

Here is what I need: Chunk claiming system, blocking all block updates between claimed and unclaimed chunks so to speak. Specifically here, fluid flow over some chunk borders. Everything is server-side.

 

What I tried:

 - BlockEvent.FluidPlaceBlockEvent, canceling it even completely does nothing in this case, it blocks cobble and obsidian creation, so still useful.

 - BlockEvent.NeighborNotifyEvent, canceling it even completely again, does nothing for this. It does prevent fluids from clearing up after the source is removed... But not the other way around.

 - FluidEvent. *, seems to be for containers, some kind of a fluid API? Non the less not applicable to this.

 

I tried this in SpongeForge and got somewhere but, in short,  some bizarre and buggy behavior made more problems than it solved...

**So my question is:** Is this even possible in Forge? I saw that you can manipulate source block merging and block creation from a liquid, this leads me to believe that forge can do this.

 

Version: 1.12.2 recommended

 

ps. it would be amazing if @diesieben07 could roast my ass, this is my first post. And reading his(I presume) sarcasm filled icy cold buckets of replies to dumb questions made my day so many times

Edited February 25, 2019 by SkenonS

[SkenonS]

Doesn't even need to be "will be", if there is a way for me to know which block "placed" which, like that event for cobble and obsidian but for liquid blocks, I can just immediately return it to air.  

I already did that by some method.

 

Only then I would need to block further block updates from originating from that replacement. I have not managed to do that, not even close, any ideas?

[Draco18s]

You can't. The best I ever managed was a block that, when placed, stored a record of what it could see around it. Then, every tick, it reverted any changes (ignoring certain things, like doors opening, redstone, etc). 

 

Water flow was a notorious problem. 

[SkenonS]

Damn... Anyway, thanks guys!

[Cadiboo]

You might want to look at WorldEventListeners, they aren’t cancelable, and don’t have write access to a world, but you can probably do an instanceof WorldServer and cast. You need to be efficient if you use this method, as it is called every BlockState change.

You can see an example in WorldRenderer/RenderGlobal and at https://github.com/Cadiboo/NoCubes/blob/396d3e731da4c3f7f6b8dd3107877ea442f09fe0/src/main/java/io/github/cadiboo/nocubes/world/ModWorldEventListener.java#L26. My code increases the chunk update distance when a block is placed from 1 block to 2 blocks to remove seams that form in my world caused by outdated meshes. 

Edited February 25, 2019 by Cadiboo

[SkenonS]

2 minutes ago, Cadiboo said:

You might want to look at WorldEventListeners, they aren’t cancelable, and don’t have write access to a world, but you can probably do an instanceof WorldServer and cast. You need to be efficient if you use this method, as it is called every BlockState change.

I'm obsessed with efficiency so that's fine, but still, that only gives me knowledge of when the block was placed, it would be up to me to return that block to air, and without a way to block further updates that would start the process all over again , with many of these blocks in the world constantly trying to "break through" that would destroy my tick time. Did I understand that correctly?

[Cadiboo]

The event fires every time a block is placed. I believe you could check if that block is liquid (cheap), if it is also a source (cheap) and is a flowing block (cheap) set it to stationary water. If the block isn’t a source set it to air (cheap) and optionally find the source and set it to air (potentially expensive).

Setting a BlockState will likely call your listener again, so be careful.

Edited February 25, 2019 by Cadiboo

[SkenonS]

4 minutes ago, Cadiboo said:

The event fires every time a block is placed. I believe you could check if that block is liquid (cheap), if it is also a source (cheap) and is a flowing block (cheap) set it to stationary water. If the block isn’t a source set it to air.

That would remove all flowing water everywhere?

I just need to block it on some chunk borders, if it's flowing between/ inside chunks of the same territory I want it to behave naturally.

[Laike_Endaril]

2 hours ago, SkenonS said:

That would remove all flowing water everywhere?

I just need to block it on some chunk borders, if it's flowing between/ inside chunks of the same territory I want it to behave naturally.

Depends on how you program it.  If you filter using the block position correctly, you can have it apply only to blocks on borders.  I'll probably be playing with this idea before too long since I'm rolling my own protection for something as well (and have everything working except fluids and falling blocks iirc).

 

I haven't gotten around to playing with it yet, but you might be able to do something like this:
1. Find the block being placed
2. Find the block which is placing it
3. Check if their positions lie in 2 different chunks, and if so, take whatever actions you plan to take to prevent it
 

My boundaries don't lie on chunk boundaries, so I can't use this method of comparison, but I'll be trying something along the same lines when I get to it.

Also, there is a whole series of fluid-related events that may be useful.  I haven't gone through them yet, so I can't say for sure, but for now, here's a list:
~SNIP~ Just saw you already tried these events, so nvm about the events.
 

If you experiment with it, maybe you can post your findings...so I can use them for reference when I get around to this again XD

Edited February 25, 2019 by Laike_Endaril

[SkenonS]

3 minutes ago, Laike_Endaril said:

I haven't gotten around to playing with it yet, but you might be able to do something like this:
1. Find the block being placed
2. Find the block which is placing it
3. Check if their positions lie in 2 different chunks, and if so, take whatever actions you plan to take to prevent it

 

That part is easy, I did that, the problem lies in those "whatever actions", because you can't prevent that block from trying to flow again in a few ticks. And if I need to constantly delete fluid blocks that go over the line, well, then that's a very vulnerable system, isn't it? Anybody with a hill and a bucket can overwhelm my block updates for all eternity.

 

3 hours ago, SkenonS said:

- FluidEvent. *, seems to be for containers, some kind of a fluid API? Non the less not applicable to this.

Draining, filling, motion and spilled are all subevents of this.

 

As @diesieben07 and @Draco18s said, forge can't do this, at least not on larger scales. And as it turns out, SpongeForge might not either.

[Laike_Endaril]

Good point.

The only approaches I can think which would bypass that issue are...
1. Preventing the flow using actual blockstate properties, but I haven't delved into that concept yet and it's probably chock full of caveats.
2. Preventing the flow by altering the behavior of fluids directly.  Getting this to work right with all modded fluids would probably be a nightmare unless you find a neat trick.

[SkenonS]

Exactly!

1. Forge doesn't have that capability, at least not yet

2. Very possible, but as far as I know that constitutes as a requirement for a core mod, and I am not very willing to do that

 

I'm experimenting with SpongeForge right now, there is hope. I'll report back, maybe you could port your mod to Sponge, It's almost a must-have for Forge servers, so optimized

Edited February 26, 2019 by SkenonS

[Cadiboo]

47 minutes ago, SkenonS said:

you can't prevent that block from trying to flow again in a few ticks

Yes you can. Fluids have a non-flowing Block that doesn’t update by default. 

 

27 minutes ago, SkenonS said:

core mod

Not necessary

[SkenonS]

10 minutes ago, Cadiboo said:

Yes you can. Fluids have a non-flowing Block that doesn’t update by default. 

Isn't that non-flowing variant only a "full" block of liquid? What I mean if the lowest level of let's say water tries to flow over, wouldn't this change it to a full block of water?

 

Also when that water tries to drain, would that stationary block prevent that, be "undrainable"?

[Cadiboo]

You could wrap fluids in the registry and override their method that makes them flow into an area

[SkenonS]

Yes, I was hoping for something like that, can you please tell me does that also require a client-side mod? I was under the impression that any tampering with the registry requires that?

[Cadiboo]

Adding stuff to the registry requires it be on both sides. If your only replacing server-side logic, then it’s not required on the sever side

[SkenonS]

And how would I go about doing that?

[Laike_Endaril]

Well, for timing, if the registry event is used, setting priority to lowest should *usually* catch all fluids...but if some other mod adds a fluid using lowest priority and comes after your mod alphabetically then that could be an issue.  Even with post init and lowest priority, I wouldn't be surprised if some things ended up getting added after it (depending on the name), as some mods add fluids dynamically based on ores loaded.  I think tinkers construct might do this, but I'm not sure (also not sure what timing it's using if so).

 

The ForgeRegistries#register() method has a callback that might be useful for catching things as they are registered, but I haven't dug deep enough to see what it's actually being used for, so I don't know if trying to hook into that will screw something up or not.  Maybe there's a better way?  I haven't tried intercepting registry entries as they're added before.

[SkenonS]

Well, that's a whole lot of info  Thanks!