Conversation
|
This only really depends on the block type so I think BlockType is a more suitable place |
|
That’s a fair point, but I added it to BlockData because it directly mirrors Vanilla architecture ( |
|
@Lulu13022002 What do you think? Where should I put it? |
|
I think it can be on both if you really want it on BlockData, but it's fine to use the default block state (it wouldn't be the first method here). There is no need to fully mirror vanilla, the api is a bit inconsistent on where to place things here (some case using CraftBlock too). |
|
Sure, I added it also to BlockType. |
| } | ||
| // Paper end - hasCollision API | ||
|
|
||
| // Paper start - getInstrument API |
There was a problem hiding this comment.
This comments are only necesary in NMS
| * | ||
| * @return the associated instrument | ||
| */ | ||
| Instrument getInstrument(); |
|
Okay, I added anotation and removed comments. Should I do something about build failure with the previous commit, or is that ok? |
I rerun the build and all looks good by the moment. |
I added the missing getInstrument() method to the API as requested in issue #14228.
Changes: