now that I look at it again, the only useful thing about this seems to be marathons or songs that heavily change their style.
yeah, especially for song compilations where there is a heavy change in bpm, the ability to change AR to that will be definitely useful.Blue Dragon wrote:
now that I look at it again, the only useful thing about this seems to be marathons or songs that heavily change their style.
We could set a rule where it's only allowed to use this for Compilations with at least four different songs. To prevent this being used in normal maps.Kibbleru wrote:
yeah, especially for song compilations where there is a heavy change in bpm, the ability to change AR to that will be definitely useful.Blue Dragon wrote:
now that I look at it again, the only useful thing about this seems to be marathons or songs that heavily change their style.
although, i CAN see people abusing this function though and there will need to be new set rules in order to prevent that.
4 different songs doesnt make sense, it should be min 2 different songs at a BPM difference that calls for different ARs. Or maybe just a high enough BPM change in one beatmap.Stefan wrote:
We could set a rule where it's only allowed to use this for Compilations with at least four different songs. To prevent this being used in normal maps.
That's actually common sense to notice a difference between 200-250 and 100-300 BPM so people probably won't change the AR every 30 seconds in case the song changes after 30 seconds.Granger wrote:
4 different songs doesnt make sense, it should be min 2 different songs at a BPM difference that calls for different ARs. Or maybe just a high enough BPM change in one beatmap.Stefan wrote:
We could set a rule where it's only allowed to use this for Compilations with at least four different songs. To prevent this being used in normal maps.
Imagine a "compilation" with one 100 BPM song and one 300 BPM song, on the other hand, 4 different songs all within the 200-250 bpm range probably dont need different ARs.
Right, however thats not the point i want to make, i am saying that your rule wording wouldnt allow a compilation with 100/300 BPM and 2 songs to use this, while this is one of the few things where different ARs would be usefull.Stefan wrote:
That's actually common sense to notice a difference between 200-250 and 100-300 BPM so people probably won't change the AR every 30 seconds in case the song changes after 30 seconds.Granger wrote:
4 different songs doesnt make sense, it should be min 2 different songs at a BPM difference that calls for different ARs. Or maybe just a high enough BPM change in one beatmap.
Imagine a "compilation" with one 100 BPM song and one 300 BPM song, on the other hand, 4 different songs all within the 200-250 bpm range probably dont need different ARs.
Dont forget that some songs may have really extreme bpm jumps by themselves.Stefan wrote:
We could set a rule where it's only allowed to use this for Compilations with at least four different songs. To prevent this being used in normal maps.
Mania players get along fine with it.Kitsunemimi wrote:
No because if we had this, it would be totally disorienting and unnecessary.
Lolwut?laishiou wrote:
the way i see it is people make ar the way they want it for a reason when making their map, you dont really need to edit ar for standard osu and ctb mods like that, i think only in mania currently changing ar is something that should remain, this in other modes would be like taking the difficulty out of a map where as in mania its just for different playstyles honestly two ways i belive it should go is either this gets implemented and you get score deduction for using lower ar maybe even a higher score for higher ar or this doesnt get implemented and you can simply edit a song and make it unranked quickly
formi wrote:
This will make sight-reading nearly impossible,
please don't make standard maps even more weird!
...but as a player...EvilElvis wrote:
honestly it will be interesting, but with that thing RC should be changed(deeply changed immo), moreover, it's a huge chance of overusing or inappropriate using of that. Also player should be warned about ar change for sure (some kind of flashy effect for example) what can be a reason of fps drop and blame
well, as player i'd say no, but as mapper... it will be really cool gear to emphazising things
Why should the multiplier change if the mapper decides to use different ARs in a map? Whats the point?BlackMidKnight wrote:
But I guess when the AR is changed, if implemented, the score multiplier must be also. Just like changing the keys on o!m (4K, 5K, 6K...)
Youre not mapping a song to make it difficult. You map a song because you probably like the music and would like to create something that you can share with other players. If a song is calm/slow at a section, then that section is not meant to be fucking hard. If it was, then the artist wouldnt have made it calm. Easy as that.HK_ wrote:
Why the heck would you want to make easier something thats supposed to be hard? If you make something hard easy its not hard anymore and that makes no sense at all. Its the best the way it is.
Make that a ranking criteria, if neccessary. Give the possibility to go all the way through, I'd love to see gimmick maps with heavy AR changes.- Lumi - wrote:
The AR change would be from only 1 point or 1,5 maximum !
Like you're having a slider ar8 and the next one has a higher sv (ex. 1,50x) then create an ar9 or 9,5 for this said slider.
Hope you see my point of view.