Client-side glides from movement (managed using glide_size) are very pretty, and make life for us a lot easier

That said, the limitation of only being able to glide across 1 turf's worth of movement is extremely troublesome.

I've had to give up on features like multiple sources of movement being applied at once because they just looked like garbage as soon as you hit the like 1/20 chance of them both applying in the same tick.

It also makes faster then a turf per tick movement basically unfeasible.

I realize that we need a way to tell the difference between a glide and a jump, but some form of configurable glide_step_size or something would make so many effects possible, and make my life a lot easier.