After relogging twice it fixed the problem. I'm not sure why...
Have you tried looking at the spawned mob for more than 2 seconds? No, it doesn't work
I already had, and I also looked at multiple vidoes explaining how to do this.
Use this command yourself:
/summon Witch ~ ~1 ~ {AttributeModifiers:[{Name:generic.movementSpeed,Base:0.0}]}
This. Also, attributes doesnt work in 14w08a too, so you can only slow down/speed up mobs by the command /effect and throwing potions at them.
Can't use attributes on mobs in 14w08a
I would say it is fixed, because they did not release an .exe file for the newest version.
1.7.1, i could not join a server if i left and tried to join it again (unless i restarted).
In 1.7.2, instead of being unable to join a server, i now get kicked out more often while playing (io.netty.handler.timeout.ReadTimeoutException). So i would say its not fixed.
Sometimes, when i try to connect/ping, my internet hangs up for some strange reason for around 30 seconds. This also seems to sometimes give this error to my client log:
Client> java.net.ConnectException: Connection timed out: no further information: IP/IP:25565
Client> at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) ~[?:1.7.0_45]
Client> at sun.nio.ch.SocketChannelImpl.finishConnect(Unknown Source) ~[?:1.7.0_45]
Client> at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:191) ~[netty-all-4.0.10.Final.jar:?]
Client> at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:228) ~[netty-all-4.0.10.Final.jar:?]
Client> at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:497) ~[netty-all-4.0.10.Final.jar:?]
Client> at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:447) ~[netty-all-4.0.10.Final.jar:?]
Client> at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:341) ~[netty-all-4.0.10.Final.jar:?]
Client> at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:101) ~[netty-all-4.0.10.Final.jar:?]
Client> at java.lang.Thread.run(Unknown Source) ~[?:1.7.0_45]
Confirmed, not fixed
feature?
supported
Just play normal survival, you'll find it very quickly. I own a server and a lot of people have started noticing this.
Fixed in 13w24b
Force crashed and attached the report
Lost really good stuff because of this :/ Well, i guess i have to check on my armor frequently until the new snapshot comes out
Sorry, but how could i know that armor breaking caused it...
Yes, i did search for it 😛
If you set fire to explosives, what do you think would happen?
Taken from mojang.com :
"If you are updating from 14w26a or 14w26b, your saved world has corrupted blocks and it will be heavily damaged once you open it in 14w26c. Please use a world backup that was saved with a pre-14w26 version.
Never use snapshots without first making backups of your saved worlds."