Refactor & expand utilities. Add fake enchantment for ItemBuilder #1
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.
UtilityintoStringUtil&NumberUtilfor organization.StringUtilthat may come in handy.min(...)toNumberUtilfor consistency.ItemBuilder, in the case we want an item with the enchantment glow with no special effects.Other notes:
Personally, there are things I really like about your
ItemBuilder, but technically speaking it doesn't "build" anything. A builder class should not modify the resulting item as the methods are called, it should keep everything separate until abuild()method is called, to which it will then take all stored variables and combine them into anItemStack.