Bartłomiej Dach
388f6599e0
Add failing test for not attempting to upgrade non-legacy scores
...
This was a source of confusion for users previously, wondering why their
non-legacy (non-stable) scores weren't being converted in line with new
scoring changes, when it was never actually our intention to support
anything of the sort.
2024-01-08 22:10:09 +01:00
Bartłomiej Dach
67df7b33fb
Add failing test coverage for not attempting to upgrade custom ruleset scores
2024-01-08 22:10:08 +01:00
Bartłomiej Dach
9c8df4e6d1
Run score conversion for previously-imported scores
2023-12-18 22:27:51 +01:00
Dan Balasescu
b9ab4a2b7c
Update score conversion to consider legacy multiplier
2023-10-02 16:56:15 +09:00
Dean Herbert
b3e7416972
Rename new flag and update xmldoc to match
2023-08-21 19:36:22 +09:00
Dean Herbert
662073c472
Fix some incorrect comments / test step descriptions
...
Co-authored-by: Bartłomiej Dach <dach.bartlomiej@gmail.com>
2023-08-21 19:35:04 +09:00
Dean Herbert
235cb2d73f
Add test coverage of upgrade success for good measure
2023-07-26 16:28:38 +09:00
Dean Herbert
a2f1ced5a2
Add test coverage of failed-to-upgrade flag
2023-07-26 16:22:21 +09:00
Dean Herbert
c1ba8fe175
Rename BackgroundBeatmapProcessor to BackgroundDataStoreProcessor
2023-07-26 16:22:10 +09:00
