#infinite frontend pulloffs can be cheesed slightly

1 messages · Page 1 of 1 (latest)

plain pendant
#

before playing a hopo, the player can "fake" a pull-off that isn't there, gaining free infinite frontend for the hopo.

this isn't a crazy exploit or anything, but it does make slow hopo/tap sections easier since you don't need timing to hit the note.

ms paint diagram of what im talking about:

plain pendant
#

to clarify, this is the default pull-off behavior, not any cheats

latent zodiac
#

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.

plain pendant
#

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

latent zodiac
plain pendant
#

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)

latent zodiac
#

I knew it could get as high as 20% sometimes but good to know it can get to 60%

plain pendant
#

intel integrated graphics moment

latent zodiac
#

lmao

gaunt wedge
#

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?

primal ravine
#

hold on a minute

#

something aint right here

latent zodiac
# primal ravine hold on a minute

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.

latent zodiac
primal ravine
#

should be 30 something

#

I like it ahead but not that far ahead

latent zodiac
#

Could you enable the hit window to be visible and have a look to see where it's positioned?

#

Only possibly way to hit a chord that far ahead and with the sustain cutting off not at the strikeline is if the hit window has been moved up to that position.