CJ
- Classic
- classic
- Europe/Stockholm
- Yes
- No
MC-85986Creating a Custom Villager to do some item trades. Trying to set up a Villager to accept damaged items and give new items as replacement.
Was expecting that, not adding any type of item damage value for the item tag would allow a trade for that item on the Villager, and as long as the added information matched, the trade would be OK. No, the Villager checks for the item damage by default.
Changed the item tag info, and included Damage:0 and also tried Damge:-1... tried Damage:0s and Damage:-1s as well, just tried a whole lot of random trying to disable the check for item durability... nothing works.
It would be nice if when Mojang added features into the game, they would also add a value to null out the action as well, so it can completely be bypassed.
So now, instead of having a nice Villager in the game, handling everything, I also have to build a huge Command Block contraption and make this two part since Mojang Dev's seem to have no foresight.
Please fix so we may bypass what we do not wish to check for. Or make a damage RANGE.
A "Locked" trapped chest will power redstone, whether the "key" item is used to open the chest or not.
This is not the previous behavior of how locked trapped chests worked. They would never power redstone UNLESS the key item was used to open them.
Could Mojang please fix instead of giving a "this is working as intended." Thanks!
— removed —
pls close
How is a game feature, as in, something you are allowed to do in the game without any kind of modding, not supported? If it is in the game, which is provided by Mojang, it is supported. You do understand how ridiculous that is right? But, that is the laziest way out of fixing something I guess.
Well that's interesting... I see no Skeleton/Zombie horse in the summon auto-complete... so I would guess those are unsupported, but guess what, Giant is listed in the list of objects able to be summoned, which Minecraft by default tells me I can. Amazing some something not supported pops up on the list along with all the supported items... is there an official 'Not Supported' list I can look at from Mojang?
Huh? Why would it pull other items if something doesn't match? I'm pretty sure this is bugged.
Also, it only does this on the first entry. If you have 10 items on the NPC, only the first entry bugs out like this.
*edit*
You are correct about the offer being given matching the first trade available for that item... however, why does this only happen in the first entry for the Villager... it just, doesn't seem right... but if that's how it works, I guess that's how it works.
How exactly would a "non-mod" copy command blocks? A regular player not only does not have access to command blocks, but they also cannot enter code into command blocks. I don't understand your response.
My server, my security. Thanks for the thought, but I would like to have this option, without Mojang dictating exactly what is in my best interest.
Kumasasa, you sure handle issues very cleverly. Take valid points about broken features and just mark them as resolved. Seriously, it shows how much you actually care about this game.
Since you are directing me to Reddit tho, I guess I will tell it how it is over there, about the constant incompetence of Mojang Dev's and crew handling such issues as these.
https://www.reddit.com/r/minecraftsuggestions/comments/45vdp7/at_war_again_only_ops_may_use/
Ok, it was missing Value. Name was not needed. Took me a moment to look that up, and I ran across a similar ticket here:
MC-51003which was a big help.Thanks for setting me on the right track FVbico, you're awesome!
Game tells me otherwise when it auto-completes the command for mobs which can be summoned. Yes, this is in the default game. If sheeps break, do they become unsupported mobs at that point too? It is obviously broken, since it's in the game. If it's unsupported, it should not be there and accessible like any other summon.