Skip to content

Conversation

@Intybyte
Copy link
Member

@Intybyte Intybyte commented Dec 20, 2025

Progress:

  • Fluid Limiter code
  • Fluid Limiter recipe
  • Fluid Limiter name, lore and translatables

  • Fluid Accumulator code
  • Fluid Accumulator recipe
  • Fluid Accumulator name, lore and translatables

  • Translatables for new gui

Most of the display entities were always done by idra, so gonna delegate that thing to him, maybe in another PR

@Intybyte Intybyte marked this pull request as ready for review December 21, 2025 16:53
@Intybyte Intybyte requested review from a team and LordIdra and removed request for a team and LordIdra December 30, 2025 11:29
@Intybyte
Copy link
Member Author

Forgot it had to wait till idra changed some fluid code, mb

@LordIdra
Copy link
Contributor

Ok, you should be able to update this now since the fluid valve changes are in master. Let me know if you need any help or context on this. I am also happy to make the relevant changes if you prefer just lmk

@Intybyte Intybyte requested a review from a team December 30, 2025 14:23
Copy link
Contributor

@LordIdra LordIdra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2 things rq

1 - this can be removed in both

Preconditions.checkState(context instanceof BlockCreateContext.PlayerPlace, "Fluid filter can only be placed by a player");
        Player player = ((BlockCreateContext.PlayerPlace) context).getPlayer();

2 - this should be yeeted and just replaced with a 1000 mb buffer

// a bit of a hack - treat capacity as effectively infinite and override
        // fluidAmountRequested to control how much fluid comes in
        setCapacity(1.0e9);

Copy link
Contributor

@LordIdra LordIdra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some more stuff

event.setUseInteractedBlock(Event.Result.DENY);
event.setUseItemInHand(Event.Result.DENY);

Window.single()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should use PylonGuiBlock here

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no because it doesn't allow me to add close/open handlers

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You won't need them after swapping to FluidThresholdButton as I mentioned in my next comment

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would remove this, rebase off my latest PR (even-more-cargo-block), and do what I did with FluidThresholdButton in CargoFluidAccumulator. It's really simple and you can basically just copy paste it. It's a lot more convenient to just have 1 button with 4 controls (and maintains consistency)

event.setUseInteractedBlock(Event.Result.DENY);
event.setUseItemInHand(Event.Result.DENY);

Window.single()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should use PylonGuiBlock

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same reason as above

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fluid limiter Fluid accumulator

3 participants