You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 31, 2021. It is now read-only.
An immutable item API is necessary for us to replace bukkit's item api.
We should use inheritance, so items inherit from an abstract 'Item' class, avoiding the ItemMeta disaster.
With builders and withers, its an easy one-liner to construct them, even though they are immutable:
Tons of useful utility methods to make withering/building new itemstacks easy.
Also add enchantments.
In the future item _metadata_ may be mutable if we decide to.
Why is the server needed in the builder? I know plugin an just call Fountain.getServer, but why not do that in the constructor of the builder? What other server is possible?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
An immutable item API is necessary for us to replace bukkit's item api.
We should use inheritance, so items inherit from an abstract 'Item' class, avoiding the ItemMeta disaster.
With builders and withers, its an easy one-liner to construct them, even though they are immutable:
The text was updated successfully, but these errors were encountered: