Aspire compatibility

[khang06]

Obviously, lazer is never going to be able to fully support Aspire maps. That being said, I still think trying to support the ones that could reasonably work in lazer should at least be considered. The client not being as janky ironically makes some of these maps more playable (e.g. no auto-fail and properly scored concurrent sliders)

I don't expect all (or even any) of these behaviors to be fixed since it's undefined behavior, so this serves as more of a discussion about the feasibility of supporting these behaviors than an actual proposal.

Also, this list isn't exhaustive and only covers the most common issues, but fixing these would probably fix the majority of broken loved maps.

Workarounds for some of these are in my fork, albeit implemented in a very hacky manner.

---

• Invisible circles via zero-length sliders (Hide zero-length sliders #13139)
• Instantly completing long sliders via BPM over 10000 (Der Wald (Kors K Remix) [NiNo's Aspire], Grenade [Negative Infinity Fragmentation])
  • This really sucks for generating slider ticks/measure lines in other rulesets
• Sliders that go past the current parser coordinate limit (Lullaby [[2B] An Unexpected Adventure])
  • Clamping slider points to the coordinate limit would probably be fine for maps that want to do instant sliders, but clamping slider length would break the above map in a gameplay-related way
• Removing slider ticks via NaN slider velocity (XNOR XNOR XNOR [Moon], basically every map that uses Sliderator)
  • Fixed in Emulate osu!stable's NaN slider velocity behavior #19919