-
Notifications
You must be signed in to change notification settings - Fork 436
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
Reading description instead of NBT data #1019
Comments
... Database upgrades exist... |
And many ad suggested items already have special converters. |
I agree with this, however, the description string is client side and as On Sun, 5 Apr 2015 7:01 pm Vexatos notifications@github.com wrote:
|
Well, all of the arguments against this I immediately thought of were already mentioned. Just wanna expand on those points a bit more:
|
I understand the error proneness of the string parsing, but this was the best I could think of. The converters I haven't seen before, is there somewhere I can find more information on them? The problem I had with using a database to sort the items was that a database can only compare to known items, which severely limits the uses when trying to automate breeding processes. |
Example using Java in case you're unfamiliar with Scala. As you see, it's quite simple to make one. |
I think what they were referring to is how to access the converters lua On Tue, 7 Apr 2015 7:22 pm fnuecke notifications@github.com wrote:
|
@LordTy I hope you know that there is a special converter for Bees so automating bee breeding already is easily possible. |
Ah, well that's automatic - given some callback returns the converted type. Such as the |
I have seen a few request for the reading of NBT data, which are understandably denied.
However, I think a way to allow us to still sort items based on NBT data that is visible to the player (eg safari nets, seeds, bees) would be to expose the description string of the item.
Then it is up to the programmer to correctly parse this string and it allows the mod-makers to decide which data is visible.
The text was updated successfully, but these errors were encountered: