I tried searching for a similar topic but had no luck (or I haven't tried looking hard enough) so please let me know if this has been requested already.
(I hope this belongs in Feature Requests since I don't exactly believe this is a bug and I don't know if there's any other subforum for smaller details like these...).
What I wouldn't mind seeing implemented is the possibility of placing sprites on more accurate X and Y coordinates. The way it works now is, you can move a sprite to, for example,
When initially declaring a sprite on starting coordinates. If the values are decimal, the sprite isn't even recognized by the editor and is just skipped.
To put it simply,
Now this might not seem like much of a difference, it's just a tiny little bit, nobody is ever going to notice that. It does, however, make a difference when trying to align several sprites alongside another object, may it be a background element or any other sprite.
A simple example:
This is a basic example of some audio spectrum bars moved to the edge of a background object. They look perfectly aligned.
Then, the beatmap is saved and the sprites re-position themselves to the rounded down values, resulting in this mess.
TL:DR Make the Move command and initial Sprite positioning support float values instead of being rounded down to integers.
(I hope this belongs in Feature Requests since I don't exactly believe this is a bug and I don't know if there's any other subforum for smaller details like these...).
What I wouldn't mind seeing implemented is the possibility of placing sprites on more accurate X and Y coordinates. The way it works now is, you can move a sprite to, for example,
M,0,0,,173.25302,251.675003and the sprite will stay on that exact position up until the point where you save your beatmap. What happens next is, the float values'll round down to integer values, resulting in
M,0,0,,173,251.
When initially declaring a sprite on starting coordinates. If the values are decimal, the sprite isn't even recognized by the editor and is just skipped.
To put it simply,
Sprite,Background,TopCentre,"sb/eq.png",173.25302,251.675003will cause the called sprite to be ignored by the editor (meaning it won't even show up), opposed to
Sprite,Background,TopCentre,"sb/eq.png",173,251where the sprite shows up normally (albeit misplaced due to rounded values).
Now this might not seem like much of a difference, it's just a tiny little bit, nobody is ever going to notice that. It does, however, make a difference when trying to align several sprites alongside another object, may it be a background element or any other sprite.
A simple example:
This is a basic example of some audio spectrum bars moved to the edge of a background object. They look perfectly aligned.
Then, the beatmap is saved and the sprites re-position themselves to the rounded down values, resulting in this mess.
TL:DR Make the Move command and initial Sprite positioning support float values instead of being rounded down to integers.