#Input handling issue

1 messages · Page 2 of 1

vivid grail
#

Yessir I'm burnt out and I didn't manage to fix it!

#

I could seem to move correctly to 1 state at a time system

#

im going insane

abstract jetty
vivid grail
#

It might be...

vivid grail
#

What does white monster even taste like

sick drift
white karma
#

it tastes like white monster

vivid grail
marble willow
#

benchmarks

#

also about the thing

#

animation controller needs to parented to smt like at least replicated storage

#

otherwise ignored

#

I misremembered

#

so there are 2 hard checks

#

what do you guys think

#

is it worth reusing animation tracks

#

seems like it is

vivid grail
#

@marble willow i fixed the bug

#

but

#

i still havent moved to the 1 state at a time system

#

i figured that the bug happens because theres no set duration that a user holds block

#

so it means you can spam block every frame

marble willow
vivid grail
#

I added a 0.15 min duration

marble willow
vivid grail
#

so if you tap block

#

the block lasts for like 0.15

#

as a minimum duration

#

i mean it simple

#

and it works

#

so

#

great

#

i just have to move to single state machine

marble willow
#

be ready for like a lot of changes

#

cuz like doing it the way I showed comes with its own constraints

#

you need a wrapper for a lot of stuff

#

including animation, vfx and sounds

#

or the code gets messy real quick

#

also Im almost done refactoring animation manager

#

gonna release finally

vivid grail
#

Like, I was thinking of making it so

#

There are certain attributes such as blocking which would count as skilldebounce

#

So I basically wrap different states to a general state