CJ

Can confirm for 1.20.4

Thank you so much it worked!

No, so they have to have access to a bed to be able to switch?

I can provide a demo .mov file if someone will lift the 10 mb file upload restriction for attachments.

im having the same thing too, gamertag is TFA Ninjas

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.

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-51003 which was a big help.

Thanks for setting me on the right track FVbico, you're awesome!

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/

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.

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.

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.

Well, now the flickering is gone, but i cant use my second monitor.

Great.

I just checked, they are updated. I will look at that other ticket.

ran debug profiling, this is what i got.

another error log, this time the game crashed about 2 seconds after the world loaded

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?

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.

-------_________________---------
CONFIRMED TO BE INTENDED? WAT DA FAK?

?

?!
I freakin HATE this thing! it causes me so meny problems that I cannot figure out how to get around! and I've tried the halfslab thing and it does not do crap for me. how are pistons not working properly when they logically should intended?

? me not happy. I mean this whole argument was basically 1 side is happy with it this way and the other isn't, so both sides fighting for what will make them happy. but really, an up facing piston remaining down when a redstone block is place on top of it, the extended when powerd from something else, but not retracting when that smething else is turned off, because the redstone bloack is now powering it makes absolutely NO sence at all!

and you guys say these problems can be worked around? show me how! cause I have nor freak clue how to make stuff that should logically work, do so when because of this weird happening, don't. (again, tried halfslab, did freakin nothing)

sighs
remove this "bug" because that's what it is, a bug.
add a block update detector block, which I'm assuming this "bud block" people mention is.
everyone is happy.

those who use this bug, a single bluck for an update detector is far better than a strange pistons switch setup anyways. get rid of your piston and switchs and put in the detector block. big woop. "but my redston will break!" do as I just said and it will be fixed. to lazy to go and fix the redstone? then you didn't need it anyways.

basically all the people who have used this, don't want it to go cause they've used it.
those who haven't used it, don't want it because it's not helping them and is making it difficault or impossible to use redstone mechanisms they design as they should logically work but don't because of this bug.
makes more sence to get rid of it so redstone can work right than to keep it so a few guys and gals can be happy.