mirror of
https://github.com/ppy/osu.git
synced 2026-05-16 14:23:22 +08:00
Bartłomiej Dach
6afdf99df8
The quirks in question being that lazer's hit windows in mania preceding this change are used in stable *if and only if* Score V2 is active. If Score V2 is *not* active, stable has two disparate other sets of hit window ranges, dependent on whether the beatmap is a convert or not. With this commit, those hit windows are used in lazer when the Classic mod is active. Open points for discussion would be: - What does this mean for plays already set on lazer using the Classic mod? Are there even enough of them to care about? Also, on `master` the Classic mod does precisely nothing, so maybe such scores should just have Classic mod stripped from them? - What does this mean for the mod multiplier of Classic in mania? (I don't expect an answer to this one.)
16 lines
666 B
C#
16 lines
666 B
C#
// Copyright (c) ppy Pty Ltd <contact@ppy.sh>. Licensed under the MIT Licence.
|
|
// See the LICENCE file in the repository root for full licence text.
|
|
|
|
using osu.Game.Rulesets.Mods;
|
|
|
|
namespace osu.Game.Rulesets.Mania.Mods
|
|
{
|
|
public class ManiaModDoubleTime : ModDoubleTime, IManiaRateAdjustmentMod
|
|
{
|
|
// For now, all rate-increasing mods should be given a 1x multiplier in mania because it doesn't always
|
|
// make the map harder and is more of a personal preference.
|
|
// In the future, we can consider adjusting this by experimenting with not applying the hitwindow leniency.
|
|
public override double ScoreMultiplier => 1;
|
|
}
|
|
}
|