This is currently a Vector3 property, shouldn’t it be Vector2 instead to save data, because this is used for Screen space, not world space?
Short answer: no.
Medium answer: no, because there’s practically no data saving.
Answer based on an assumption: sending raw input information to the server is bad.
Long answer: no, because the data saved by not sending a single extra 0 is so small it basically doesn’t save anything, not to mention that InputObject uses Vector3 for Position as well, so changing Delta to Vector2 would mean that InputObject isn’t being consistent with itself.
Sometimes the ZIndex is used for things like triggers, etc. so it has to remain a Vector3. I don’t quite understand why this is a problem other than an immediate “wait, it’s a Vector3?” which is quickly dispelled.