That’s what I thought too, but the tooltip:
/**
* True when we should ignore server location difference checks for client error on this movement component
* This can be useful when character is moving at extreme speeds for a duration and you need it to look
* smooth on clients. Make sure to disable when done, as this would break this character's server-client
* movement correction.
*/
Seems it’s designed specifically for this scenario, just wish I could find more information on the specifics. May simply have to test it myself…
Come to think of it, it might actually be run on the server otherwise I don’t see how it would work. If you do two things simultaneously: Execute a displacement ability and disable the correction (passing through an end-time, of course), then technically the correction shouldn’t occur? Though I still don’t see why there wouldn’t be some snapping as it expires. You only really need it disabled in that very moment where the rubber banding occurs, maybe there’s some logic voodoo you can do with the latency.
Really just need to test it, I’ll do it as soon as I can which isn’t for a while.