Swiftykitty2K
- swiftykitty2k
- swiftykitty2k
- Europe/Stockholm
- Yes
- No
4 issues
Key
Summary
Status
Reporter
Assignee
Created
MC-4834
Changed Description:
Mobs commonly are unable to jump up/down to another block, they often get stuck at the edge of the block they are on and start to spin in circles. Is especially annoying whist herding animals.
EDIT:Made post public. Oops!
Added Attachments:
2013-01-29_10.44.02.png
Added Attachments:
Removed Attachments:
Added Attachments:
Added Attachments:
Added Attachments:
I couldn't find any other issues on this subject. I apologize if it has already been reported.
I think it may be a compatibility issue between the Minecraft applet and Apple's Java 6. I can confirm this too. This also doesn't happen on any of the Windows computers I have tested. It seems to be an Apple only bug.
Added some more screenshots with the debug screen open to show F:.
I would really like this fixed. All of the roads in my world are made of slabs and stairs, and pigs would make the journey so much quicker.
Force Updated minecraft, used an un-modded version of Minecraft 1.4.7, force crashed and added a crash report.
Updated LWJGL to the current version. Big performance increases, up to +20FPS than before, but the bug is still there.
Uploaded anouther screenshot from 13w06a
I have the exact same problem. People could connect to my server fine in updates 1.5.1 and before, but on 13w16a no one can connect! My server is run on OS X 10.8.3 with Apple Java 7. I tryed downgrading to Apple Java 6, but it didn't fix anything. I get the following messages in the server log:
Server log where NullPointerException is found.
I have narrowed the problem somewhat. The issue creating the end of stream in located in the world folder, something with loading pre1.5.1 worlds to 13w16a. To clear this up, my server world was created in weekly snapshot 12w38b and has used every single release, both official and snapshot, since that release, if it makes any difference.
I can confirm for 13w18b.
EDIT: I believe that the issue directly relates to the idcounts file in the resources folder. When I deleted the idcounts file in the resource folder in world, DIM1 and DIM-1 players can connect just fine.
EDIT2: This doesn't work for some people. More investigating is taking place.
Derp. I meant the idcounts in the DATA folder. Back up before you attempt, but it works for me when I delete [world name]>data>idcounts, [world name]>DIM1>data>idcounts and [world name]>DIM-1>data>idcounts. Sorry.
Has anyone been to the Nether or the End on your server? Just in case you didn't know, DIM1=Nether and DIM-1=End.
Odd. Well anyways, after backing up your world, try deleting the idcounts folder that you found and tell me if it fixes it! If it doesn't then I did something else that fixed it. :3
Performing more research. I shall inform you when I figure out the problem.
I can confirm for 13w18c.
The new LWJGL makes it worse. Whenever connecting to a server with it the screen spins until fullscreen mode is toggled (there are probably other ways to stop the spinning as well). However, since Minecraft is not fully compatible with the newest LWJGL, I wouldn't give Mojang a hard time with it. I can also confirm though that this occurs with the LWJGL that Minecraft is meant to use (force-updated to get the default LWJGL).
I use the Mac version of Minecraft and find horses. I believe you are either not in the correct biome
or are just having bad luck.
Though not an impact to the game's performance, I find this extremely irritating.
Can confirm on 13w24a.
13w25b confirmation. Baby Horses are a pain to look after in a pen due to them getting pushed into solid blocks and suffocating or just walking through fences/non-solid blocks. I really thought that Mojang would have fixed this by now.
Confirmed in 13w25c.
Is the server port-forwarded or does it use VPN software like Hamachi? It seems like it is an issue with your router, not Minecraft. When was the last time you restarted your router?
I can confirm this. Also, the surround-sound synchronizing is a bit odd. I'm running Minecraft on OS X 10.8.4 using Apple's Java 1.7[.]
My horse just duplicated yesterday in 1.6.2. I cannot reproduce it, but it happened. The horse was the same colour, had the same armour, same speed, jump and health, etc. I'm not sure how it happened, but a horse duplication bug still exists in 1.6.2.
This bug still exists in Minecraft 1.6.4/13w38c.
This is not a duplicate of
MC-1057. I urge you to reconsider. The Villagers are not despawning after getting too far away from them. After further testing the bug has occurred at a time where one goes to trade with a Villager, in this case a Fisherman, trading 1 Emerald and 6 Raw Fish for 6 Cooked Fish. Upon placing the Raw Fish into the Trading UI, the game crashes, and upon re-entering the server, a Shepherd is missing, yet all progess prior to crashing remains, and Villagers cured after the Shepherd remain. I have attached a crash report of the issue. Please reconsider closing this report.Yes, in the case of crashing when trading with a Villager it is a duplicate of
MC-45855, but that is not the main issue I am speaking of. The issue still remains where when a Zombie Villager is cured, and the world is restarted, they will sometimes despawn, regardless of it is intentionally shut down or closed via a crash, and regardless of how far away you are. In fact, the first time I encountered this problem I was standing right in front of a Villager. Restarted the game, and poof! he's gone, yet all progress is saved. Ignore the crashing when trading. That's out of the way. Please use discretion and notice that the post's focus isn't on the crash, it's on despawing Villagers.I also cannot reproduce in 14w10c.