When the server is lagging and the worm has bCarve=true and they are continuing their way through the dirt (or whatever), they are carving all the time. For big lags, this gives some bad effects.
Not sure actually how to solve this. Perhaps we should make velocity=0 if there is no update after 0.1 second?
Or for remote worms carve only when the new position update arrives (a line between the old pos and the new pos + something in advance like in the simulation)?
Converted from SourceForge issue 2797471, submitted by albertzeyer
When the server is lagging and the worm has bCarve=true and they are continuing their way through the dirt (or whatever), they are carving all the time. For big lags, this gives some bad effects.
Not sure actually how to solve this. Perhaps we should make velocity=0 if there is no update after 0.1 second?