Andrew McCluskey
- duckofduckness
- duckofduckness
- Europe/Copenhagen
- Yes
- No
@Andrew McCluskey: It's the server still saving the world files while the client tries to delete the files:
[00:19:42] [Server thread/INFO]: Saving chunks for level 'Flatworld6'/Overworld [00:19:42] [Client thread/INFO]: Deleting level Flatworld6 [00:19:42] [Client thread/INFO]: Attempt 1... [00:19:42] [Client thread/WARN]: Couldn't delete file C:\Users\User\AppData\Roaming\.minecraft\saves\Flatworld6\region\r.-1.0.mca [00:19:42] [Client thread/WARN]: Couldn't delete directory C:\Users\User\AppData\Roaming\.minecraft\saves\Flatworld6\region [00:19:42] [Client thread/WARN]: Unsuccessful in deleting contents. [00:19:42] [Server thread/INFO]: Saving chunks for level 'Flatworld6'/Nether [00:19:42] [Server thread/INFO]: Saving chunks for level 'Flatworld6'/The End [00:19:43] [Client thread/INFO]: Attempt 2... [00:19:43] [Client thread/WARN]: Couldn't delete file C:\Users\User\AppData\Roaming\.minecraft\saves\Flatworld6\region\r.-1.0.mca [00:19:43] [Client thread/WARN]: Couldn't delete directory C:\Users\User\AppData\Roaming\.minecraft\saves\Flatworld6\region [00:19:43] [Client thread/WARN]: Unsuccessful in deleting contents. [00:19:43] [Client thread/INFO]: Attempt 3... [00:19:43] [Client thread/WARN]: Couldn't delete file C:\Users\User\AppData\Roaming\.minecraft\saves\Flatworld6\region\r.-1.0.mca [00:19:43] [Client thread/WARN]: Couldn't delete directory C:\Users\User\AppData\Roaming\.minecraft\saves\Flatworld6\region [00:19:43] [Client thread/WARN]: Unsuccessful in deleting contents. [00:19:44] [Client thread/INFO]: Attempt 4... [00:19:44] [Client thread/WARN]: Couldn't delete file C:\Users\User\AppData\Roaming\.minecraft\saves\Flatworld6\region\r.-1.0.mca [00:19:44] [Client thread/WARN]: Couldn't delete directory C:\Users\User\AppData\Roaming\.minecraft\saves\Flatworld6\region [00:19:44] [Client thread/WARN]: Unsuccessful in deleting contents. [00:19:44] [Client thread/INFO]: Attempt 5... [00:19:44] [Client thread/WARN]: Couldn't delete file C:\Users\User\AppData\Roaming\.minecraft\saves\Flatworld6\region\r.-1.0.mca [00:19:44] [Client thread/WARN]: Couldn't delete directory C:\Users\User\AppData\Roaming\.minecraft\saves\Flatworld6\region [00:19:44] [Client thread/WARN]: Unsuccessful in deleting contents. [00:19:57] [Server thread/INFO]: Starting integrated minecraft server version 14w29b
This can also happen if you have recently deleted a world with the same name as your newly created one. The game hasn't deleted all the old world files and some chunks from the old world are put in the new world.
I am also experiencing this issue in 1.6.2.
Same outcome as HiFolksImAdam, the Development Console in the launcher shows the error messages in SP, but there's no noticeable performance loss.
Starting an MP server with the map works perfectly until a player logs in. The error messages are then printed to the console and memory usage then climbs to the max and the server crashes.
For me this bug only occurs if I am moving. Blocks are broken/placed/changed without problems as long as I am standing still.
And I had VSync turned off when I discovered this issue, so turning that off is definitely not a fix.
Confirmed for 14w29a and b.
It happens even if you're not crouching and the line now appears above instead of in front as the picture is showing.
Duplicate of MC-4490?
Confirmed for 14w29a and b.
Cannot confirm. I think this one could probably be closed...
Maybe someone who had this issue could test again? With the new fishing mechanics it's now easier to see if you should have caught something.
Confirmed for 14w29a and b.
Hence why I added the question mark. While MC-4490 specifically mentions crouching, I do not see any difference between crouching and not-crouching. Just being in 3rd person or looking at another player fishing produces this.
Confirmed for 14w29a and b.
So the problem is actually with the world/chunk generation and not old files not being deleted properly?
Confirmed for 14w30b and Windows 7.
It is also worth noting that the first teleport will be at a slightly wrong coordinate.
In one of the test I did, I ran the teleport command "/tp [my name] ~ ~100 ~" at Y = 77.16581 (this is while falling).
The first teleport placed me at Y = 171.82968. I then fell until I was at Y = 116.70684 at which point I was teleported to Y = 177.16581.
Chat only says I was teleported once, to Y = 177.16581.
X and Z coordinates are unaffected by this.