____SAURON____

If you did do something, thank you!

@Chris Miceli

It worked this time. Are you a dev; did you do something?

Update: I was able to get into MC feedback, BUT I had to use a completely different email for it to set up a completely new account. The old one will never work, and I believe that as soon as this one is signed out one way or another it is also never getting signed back in.

I have the same issue. Instantly logs out; I will attach video.

No matter what I try, whether it is using a different browser, or Tor, or a VPN, and I tried to log in on my phone, literally nothing works. MC feedback is completely and utterly inaccessible to me, and I believe it will remain so given that this particular bug report has received almost no recognition whatsoever with 4 votes including mine. AND, this issue is WAY older than April 2026! No action whatsoever, as if it’s either not important or not real.

I’m pretty sure the issue here is that Minecraft doesn’t recognize that the tripwire hook detaches from the tripwire when you break the tripwire, which means that it uses the “tripwire_hook_attached_on” model when the tripwire powers on as you break the tripwire. It should use “tripwire_hook_on” when you break the tripwire, since the hook should no longer be attached to the string (because you broke it), but it instead uses “tripwire_hook_attached_on” before reverting to “tripwire_hook”. The issue is not with the blockstate or the model, but with the fact that minecraft doesn’t issue a “attached: false” tag to the tripwire hook when the tripwire hook turns on as a result of you breaking the string.

P.S. you can still get the “tripwire_hook_on” model in your world through use of a debug stick. Here is what all the tripwire hooks look like with a texture pack, the last one being “tripwire_hook_on”:

I understand that this may be good for datapacks and stuff, but it’s actually kind of detrimental if you are making a texture pack, since the head is kind of hard to see clearly without invisibility. If this is good for datapacks, there should be an option to add an attribute that would separate the head and the shell so that they can be affected or unaffected by invisibility.

Implementing such a feature could go as follows:

/summon shulker ~ ~ ~ {shell_invis_affected:1b, head_invis_affected:0b}

This command would summon a shulker whose shell would be affected by invisibility, while the head would not be affected (this would be the default circumstance, but you can change that with the command).

Also having floating shulker heads is kinda cool and fun ig, which is why I want them back…