[deleted as part of purging my old post history]
as you said yourself, most issues mentioned are fixable. displayed bpm is not an issue unless in extreme cases such as variable timing maps, and nightcore being a mod shouldn't be taken in account for the same reason that we don't disqualify for offscreen objects in easy mode. if the player wants to add a modification, then it's on them, not on the mapper.4n3c wrote:
bpm affects multiple things, some are more important than others: slider velocity (can be fixed in most cases), slider tick rate, nightcore pulses, displayed bpm in song selction, millesecond timing shift errors (can also be fixed), and possibly more i'm not remembering.
Objects must be snapped to timeline ticks. If objects cannot be snapped using the editor’s supported beat snap divisors, a change in BPM may be used to accommodate for it. If a section of music requires an unsupported time signature not included in this chart however (1/5, 1/7, etc.), a map's objects can be unsnapped so long as they align with the intended time signature.
Objects must be snapped to timeline ticks. If objects cannot be snapped using the editor’s supported beat snap divisors, a change in BPM may be used to accommodate for it. If a section of music requires an unsupported time signature not included in this chart however (1/5, 1/7, etc.), a map's objects can be unsnapped so long as they align with the intended time signature.Seems really reasonable to me, it's a lot better than the current rule because for songs that change between divisors extensively (Handmade Cities has changes from 1/4 to 1/6 to 1/5 in single beats) due to sv and it's just tedious to deal with all the BPM changes and math.
pishifat wrote:
with the way you're suggesting, there's room for people to place objects in weird timeline positions because they have inaccurate timing, which shouldn't be allowed and isn't reasonable to regulate
4n3c wrote:
fundamentally the goal is to allow mappers to not change bpm cause bpm effects a bunch of stuff, time sig included
4n3c wrote:
for example, an object offset 10ms from the first blue tick at 180 bpm could be said to be snapped to the 7th 1/25 tick of an unsupported snap divisor.
Objects must be snapped to timeline ticks. If objects cannot be snapped using the editor’s supported beat snap divisors, a change in BPM may be used to accommodate for it. If a section of music requires an unsupported beat snap divisor however (1/5, 1/7, etc.), a map's objects can be unsnapped so long as they align with the intended beat snap divisor.
