Re: A new beginning for our SM community.
It's OK to use tough songs for the top, but the problem is that if you try to scale everything by a function of skill and performance, you may wind up with, say, every realistically-playable song only making it up to Difficulty 34 or something and then Chik Habit next in line all the way up at Difficulty 100 because it's just that much harder to do well on compared to everything else.
I think it's OK to include really tough songs as long as they aren't several standard deviations away in terms of difficulty, because then they force you to operate the rest of the game within really squished frames. Personally I think 100 should represent the hardest passable song. If a song is so hard that it can't be passed, it's hard to give it a difficulty on incomplete information which may be subject to huge variance swings.
And yeah you could pretty much plot # of steps over time and then assess local NPS figures as a sweeping X-second framework (so you'll be able to see, for instance, huge spikes if you've got an otherwise slow song but a few spots where you have high-NPS/high-BPM bursts/jacks/whatever). Would be worth implementing, assuming it could be done cleanly.
It's OK to use tough songs for the top, but the problem is that if you try to scale everything by a function of skill and performance, you may wind up with, say, every realistically-playable song only making it up to Difficulty 34 or something and then Chik Habit next in line all the way up at Difficulty 100 because it's just that much harder to do well on compared to everything else.
I think it's OK to include really tough songs as long as they aren't several standard deviations away in terms of difficulty, because then they force you to operate the rest of the game within really squished frames. Personally I think 100 should represent the hardest passable song. If a song is so hard that it can't be passed, it's hard to give it a difficulty on incomplete information which may be subject to huge variance swings.
And yeah you could pretty much plot # of steps over time and then assess local NPS figures as a sweeping X-second framework (so you'll be able to see, for instance, huge spikes if you've got an otherwise slow song but a few spots where you have high-NPS/high-BPM bursts/jacks/whatever). Would be worth implementing, assuming it could be done cleanly.



Comment