Save and reload truncates all hit object coordinates

[OliBomby]

Type

Game behaviour

Bug description

Saving and reloading a beatmap in the osu! standard editor truncates all decimal object coordinates. This behaviour matches stable but for beatmaps fully made in lazer its preferrable to preserve decimal precision. I suppose this was previously implemented for compatbility with stable but since the addition of the compatibility export feature its no longer necessary to do truncation in the beatmap encoding.
The legacy beatmap decoder should still truncate coordinates for beatmaps below file format V128 for compatibility, but skip truncation for V128 beatmaps.

Screenshots or videos

osu._4dr6a2oOaJ.mp4

Version

2024.731.0-lazer

Logs

compressed-logs.zip

[smoogipoo]

I don't see anything in the encoder doing this, so I think this might be just because of the decoder:

osu/osu.Game/Rulesets/Objects/Legacy/ConvertHitObjectParser.cs

Line 51 in 8773c2f

Vector2 pos = new Vector2((int)Parsing.ParseFloat(split[0], Parsing.MAX_COORDINATE_VALUE), (int)Parsing.ParseFloat(split[1], Parsing.MAX_COORDINATE_VALUE));