Joshua Flack
Assigned
Reported
Comments
You're missing the point
This never use to happen it is only recently that it is happening with the new update
it has became extremely annoying to play on servers because of this. Whenever you mine blocks without instant break the player is moved back for the item to drop. I believe this is unnecessary. Why should the player be in the same location as the item dropping?
It doesn't happen with instant break so something switches over. It is a change with how they fixed the lack of ghost blocks.
It isn't reasonable to just play on a server hosted closer to me because most of the servers are hosted in either europe or the USA.
And I believe this would classify as something that is worthy of getting fixed as it use to work fine on all the other versions. It was only changed in the update to 1.15
This doesn't just effect me this effects everyone with that ping, even people from the USA connecting to Europe in small cases, though sometimes it's ok.
I'm in Australia and the server is in Germany
It happens with servers that aren't in Australia
The connection to the server is extremely stable
There is never any issues with loading chunks
Never sections when the ping jumps
The ping would be at a constant 250-300
The only issue is when you start mining blocks without instant break
If you have instant break then this isn't a problem
This never use to be an issue
Other people are having the same issue
and the connection is stable
anyone with like 200ms+ ping experiences this
Its because there isn't any lag on the server
it's a change from 1.14 to 1.15 i think
There is no .zip in the file location for the server
nor in the minecraft folder.
It is just the .txt
I have uploaded the debug report
I'll give this a go but I believe this will be a client issue.
The same sort of thing happens when you have spawn protection, and you don't have permission to break blocks
if you just punch a block you get teleported back, it stops you in your track.
I will do those debug things, but remember that it is only recreated on a server when you have about 300ms ping
Just tried it on a server running 1.14.4 in the exact same circumstances and the issue isn't present at all