9 Commits

• 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.

  Bartłomiej Dach · 2024-01-08 22:10:09 +01:00
  388f6599e0
• Add failing test coverage for not attempting to upgrade custom ruleset scores
  Bartłomiej Dach · 2024-01-08 22:10:08 +01:00
  67df7b33fb
• Run score conversion for previously-imported scores
  Bartłomiej Dach · 2023-12-18 22:27:51 +01:00
  9c8df4e6d1
• Update score conversion to consider legacy multiplier
  Dan Balasescu · 2023-10-02 16:56:15 +09:00
  b9ab4a2b7c
• Rename new flag and update xmldoc to match
  Dean Herbert · 2023-08-21 19:36:22 +09:00
  b3e7416972
• Fix some incorrect comments / test step descriptions

  Co-authored-by: Bartłomiej Dach <dach.bartlomiej@gmail.com>

  Dean Herbert · 2023-08-21 19:35:04 +09:00
  662073c472
• Add test coverage of upgrade success for good measure
  Dean Herbert · 2023-07-26 16:28:38 +09:00
  235cb2d73f
• Add test coverage of failed-to-upgrade flag
  Dean Herbert · 2023-07-26 16:22:21 +09:00
  a2f1ced5a2
• Rename BackgroundBeatmapProcessor to BackgroundDataStoreProcessor
  Dean Herbert · 2023-07-26 16:22:10 +09:00
  c1ba8fe175