Gave melon slice item a name distinct from the melon block #158
Conversation
This file contains 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
I will add new 32*16 terrain.png file
Minecraft.yaml was cleaned up, so why not pocket.yaml? This update is better than texture update.
Absolutely perfect update for 0.8.0
Minecraft.yaml 1.8 general fixes
Will also send pull request updated terrain-pocket.png(tested)
|
To clarify, the current behavior is that when you reach for items.names['Melon'], you get either the melon slice or the melon block, chosen randomly (probably due to Python's per-process hash randomization). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I was surprised a bit when I tried to put a melon slice item in a chest and ended up with a melon block item. On investigation, they both used the name "Melon". This patch should allow them to be referenced separately.