Dean Herbert e53c8518de Don't output beatmap parse failures in a visible manner ... The user can't do much about this. When a user reports a beatmap issue, the logs will still contain this useful information. Should be fine I think. As mentioned in https://github.com/ppy/osu/discussions/18426 https://github.com/ppy/osu/issues/750 https://github.com/ppy/osu/issues/18372 etc.		2022-05-27 19:18:38 +09:00
..
Decoder.cs	Disallow registering a null RulesetStore	2022-02-18 16:52:34 +09:00
IHasComboColours.cs
IHasCustomColours.cs
JsonBeatmapDecoder.cs	Copy BaseDifficulty to Beatmap<T> and move all write operations across	2021-10-06 15:10:45 +09:00
LegacyBeatmapDecoder.cs	Fix slider velocity wrongly decoded as scrolling speed in osu!catch	2022-05-08 21:49:42 +09:00
LegacyBeatmapEncoder.cs	Don't merge adjacent legacy Catmull segments	2022-05-18 17:16:24 +09:00
LegacyDecoder.cs	Don't output beatmap parse failures in a visible manner	2022-05-27 19:18:38 +09:00
LegacyDifficultyCalculatorBeatmapDecoder.cs
LegacyStoryboardDecoder.cs	Apply batch fixing of built-in types using var	2021-10-27 13:04:41 +09:00
Parsing.cs	Apply batch fixing of built-in types using var	2021-10-27 13:04:41 +09:00