I was messing with item sorters,hoppers and came along weird bug that emeralds act different then glowstone,diamond,iron or lapis maybe even more (these were the only ones that i tested). It seems like hoppers wont detect emerald unless it is placed directly on top of it, other wise it will just skip it and go to misc chest. There is a way to fix this but it would require way more resources and would be bigger. This is design from ac-tennis, just simplified, and bugged. - vilhardo
Attachments
Comments 8
Well if this wont get fixed it will be in 1.5 and if there is option to add future version, why shouldn't i put it there? take it away then if its that big of a deal >.<
People have access to mark their bugs as unreleased version. Then why there is an option to do that?
Daniel, ask that from Atlassian. Basically, there is a single list of "versions" that can be selected items from in any place where one or more versions are asked.
Consider also that JIRA is meant not only for end users but for the developers themselves, too. (Or more typically, JIRA is used for the developers only, and users need to get through customer service, which adds new issues when necessary). Developers might see that they will not be able to fix an issue in e.g. next release, so they can mark immediately that release/version to be affected.
Its not a bug, and your "sorter" is not an item sorter. There are no priority for items to be sucked out from the bottom, instead it will be random depending on the location you put the hoppers. Ergo, if you put a hopper in the center pointing to left, and another hopper under it, the hopper will pick whether to send it to the left or below based on the location. An actual sorter will require droppers at the top. View MinecraftPG5 for a vid on an actual sorter. Also, no offense.
Please do not mark unreleased versions as affected. You do not have access to this yet.