| Type: | Bug | ||
| Reporter: | nyuszika7h | Assignee: | [Mojang] Searge (Michael Stoyke) |
| Resolution: | Fixed | Votes: | 12 |
| Labels: | beacon, drops | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| CHK: | |||||||||||||||||||||||||||||||||||||||||||||||||
| Confirmation Status: | Confirmed | ||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
Steps to reproduce: What I excepted to happen was: What happened instead: |
| Comments |
| Comment by [Mojang] Searge (Michael Stoyke) [ 23/Nov/15 ] |
|
Better fix in the next snapshot |
| Comment by Ampflower [ 30/Jul/15 ] |
|
In 15w31B |
| Comment by Ampflower [ 28/Jul/15 ] |
|
In 1.8.8 |
| Comment by [Mod] Torabi [ 12/Mar/15 ] |
|
searge tried to fix this by having the beacon eject the sacrifice item into the world when the player closes the beacon interface. The problem is that this incorrectly assumes that the only way for an item to get into the sacrifice slot is for a player to open the interface and put it there. Either hoppers and droppers need to be prevented from putting items in beacons, or the beacon blockentity needs to actually store the item in the slot. Currently, it's not saved, which is why destroying the beacon or reloading the world causes it to disappear. |
| Comment by Ampflower [ 09/Feb/15 ] |
|
Torabi: Putting in beacon through hopper. Not stacking, though it does only drop one item at a time per closing, which is still needs a fixing. |
| Comment by [Mod] Torabi [ 07/Feb/15 ] |
|
KJP12, does it occur if you only put one item in the beacon using a hopper, or are you |
| Comment by Ampflower [ 01/Feb/15 ] |
|
Searge, beacon still eats the item when hoppered in. 1.8.2-pre6 |
| Comment by Ampflower [ 18/Jan/15 ] |
|
In 1.8.2-pre4. |
| Comment by Chris [ 08/Aug/14 ] |
|
Confirmed for 14w32d (haven't tested a,b and c, but it's save to assume the bug exists in those versions as well.) Edit: confirmed for 14w33a Edit 2: Confirmed for 1.8 pre-release |
| Comment by Andrew Thomas [ 10/Jul/14 ] |
|
Confirmed for 14w28b |
| Comment by Chris [ 19/Jun/14 ] |
|
Confirmed for snapshot 14w25a, 14w25b, 14w26a and 14w26b Edit: Also confirmed for 14w27a and 14w27b Edit 2: Also confirmed for snapshot 14w28a and 14w28b Edit 3: Confirmed for snapshot 14w29a and 14w29b, 14w30a and 14w30b |
| Comment by Chris [ 15/May/14 ] |
|
Confirmed for snapshot 14w20b Edit: also comfirmed for snapshot 14w21a 14w21b |
| Comment by Chris [ 26/Apr/14 ] |
|
Confirmed for snapshot 14w17a. |
| Comment by Chris [ 16/Feb/14 ] |
|
This is still a concern in snapshot 14w07a. |
| Comment by [Mod] Ezekiel (ezfe) [ 22/Jan/14 ] |
|
Is this still a concern in the latest Minecraft version 14w03b? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. |
| Comment by Avstar98 [ 19/Aug/13 ] |
|
Items in the beacon are also lost upon closing a world and re-opening it. |
| Comment by Kumasasa [ 12/Dec/12 ] |
|
Confirmed |
| Comment by [Mod] Torabi [ 20/Nov/12 ] |
|
To clarify: You put the item in the beacon's gui slot, but do not click the check box to consume the item and activate the beacon. The item remains in the gui slot, but if you break the beacon, the item is lost instead of being expelled. |
| Comment by Charlotte Buff [ 16/Nov/12 ] |
|
But you haven't paid anything with it. You just put it into the beacon and destroyed the beacon. |
| Comment by Chalmes (Jon) [ 07/Nov/12 ] |
|
The item you placed in the beacon is a form of payment, so isn't intended to be returned to you. |