Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a warning for redstone conditions not being met #8262

Open
wants to merge 2 commits into
base: 1.21.x
Choose a base branch
from

Conversation

bukowski912
Copy link

@bukowski912 bukowski912 commented Nov 22, 2024

Changes proposed in this pull request:

  • Make GuiInsetElement able to track warnings through a supplier
  • Use a separate texture for GuiInsetElement during a warning
  • Track the activation warning under GuiRedstoneControlTab
  • Add the corresponding lang entry to MekanismLangProvider
  • Synchronize activation (redstone) state of TileEntityMekanism

@bukowski912
Copy link
Author

bukowski912 commented Nov 22, 2024

Whups, I pushed a cache file. Is there a reason why it isn't in the .gitignore? I'll leave it for now - if this is a mistake, let me know and I will fix it right away. It seems to be already in the repository, at least on my end.

@bukowski912 bukowski912 reopened this Nov 22, 2024
@bukowski912
Copy link
Author

I hate GitHub mobile.

@pupnewfster
Copy link
Member

The cache file is so that you don't have to rewrite all the files to disk when you first checkout and run datagen.

- Make GuiInsetElement able to track warnings through a supplier
- Use a separate texture for GuiInsetElement during a warning
- Track the activation warning under GuiRedstoneControlTab
- Add the corresponding lang entry to MekanismLangProvider
- Synchronize activation (redstone) state of TileEntityMekanism
@bukowski912 bukowski912 changed the title Add a warning for machine inactivity due to redstone control Add a warning for redstone conditions not being met Nov 23, 2024
@bukowski912
Copy link
Author

Note that the special blending technique used for the warning overlay may have performance drawbacks, especially in light of previous optimization (e.g. 609b030). In addition, I renamed GuiSideHolder#draw() to drawHolder() as I thought that was much clearer. Let me know if that was an overstep.

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.

3 participants