#infinite frontend pulloffs can be cheesed slightly
1 messages · Page 1 of 1 (latest)
video demonstration
to clarify, this is the default pull-off behavior, not any cheats
This is intended behaviour. Infinite frontend for hammer ons is disabled by default but is available for pull offs. This is specifically for sections like the ttfaf intro where the pull offs can become a little bit frustrating if there was in infinite frontend.
So by default, a frontend only exists for pull offs and bot hammer ons since hammer ons can be more easily timed compared to pull offs in fast sections.
This is basically how we’ve balanced the gameplay to still feel good without a frontend available for hammer ons.
i know pull-offs are supposed to have infinite frontend. the problem here is the notes are hammer-ons.
the question is specifically whether ghosted pull-offs (not actually charted as pull-offs) are supposed to have infinite frontend
Yes this is intended. Now may make a small difference in Classic, it won't help at all in Quickplay since the score system will be weighted based on accuracy. So if you abuse any infinite frontend logic in Quickplay, you'll see yourself getting only 10% of the score.
ok! that's all i wanted to know. (although depending on your framerate it's not necessarily going to be a 10% -- in the video i get as high as 60% using infinite frontend)
When we get quickplay going, I'll be investigating a way around this. Right now it's just a number below the frets so small issues like such doesn't quite matter as much in the current state.
I knew it could get as high as 20% sometimes but good to know it can get to 60%
intel integrated graphics moment
lmao
What if pull offs had a front end that was fairly wide, but not infinite?
E.g 1 second or maybe even 0.5 seconds?
Looks like your video offset has the hit window moved pretty far ahead and that since you had no combo, you've skipped to the chord since those were the matching frets when strumming. Letting go of the green fret has cut off the sustain and the position of where you see it cut off is where the middle of your hit window currently exists.
its not that far ahead
May I ask what your video offset is set to?