Update to Explosion Control 1.0.4 #1
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
RitzKid76
approved these changes
Dec 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New Additions:
Added a settings.yml file that auto-generates on next startup
Ability to enable/disable TNT chaining
TNT chaining has a configurable limit on how many TNT can explode in a set amount of time,
default is 20 TNT every 1000 ms
Added ability to prevent entire explosions if a single block was not on the whitelist, enabled by default
Added ability to config if you want the TNT whitelist to be enabled, enabled by default
Added ability to config if you want the TNT to not pop off blocks or spill liquids, enabled by default
Added a few more blocks to the TNT whitelist
Optimized the code slightly