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

Added Error Flag to Hellfire Forge #1993

Open
wants to merge 1 commit into
base: 1.20.1
Choose a base branch
from

Conversation

VT-14
Copy link
Collaborator

@VT-14 VT-14 commented Oct 11, 2023

Added an error flag to the Hellfire Forge that tells players when the recipe isn't working due to not having enough Demon Will on hand.

  • Added flag texture to the Hellfire Forge's GUI. Also saved the texture more efficiently, decreasing file size.
  • Added translation keys for tooltip text.
  • added a Boolean variable to the Tile, and a method to read it.
  • added the flag and tooltip to the Screen.

I also tweaked the TileSoulForge's operation. The || burnTime > 0 check caused a minor bug where a player could start the recipe going, then swap to a gem without enough will and it would look like it would keep going (though fail to craft when finished). It seems to work as I would expect without it.

I then could also remove two redundant if statements checking for the level being not client side, and having enough Will. the client side check was done earlier so was always true, and by removing the burnTime > 0 alternative the minimum souls check is also already done and always true.

Added an error flag to the Hellfire Forge that tells players when the recipe isn't working due to not having enough Demon Will on hand.

* Added flag texture to the Hellfire Forge's GUI.  Also saved the texture more efficiently, decreasing file size.
* Added translation keys for tooltip text.
* added a boolean variable to the Tile, and a method to read it.
* added the flag and tooltip to the Screen.

I also tweaked the TileSoulForge's operation.  The `|| burnTime > 0` check caused a minor bug where a player could start the recipe going, then swap to a gem without enough will and it would look like it would keep going.  It seems to work fine without it.

I also then could remove two if statements checking for the level being not client side, and having enough Will.  the client side check was done earlier so was always true, and by removing the `burnTime > 0` alternative the minimum souls check is also already done and always true.
@VT-14 VT-14 added the 1.20 label Oct 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant