How to prevent "Conditional Branch; If Button Pressed" from just being held down?

[JJGreyKK]

I'm creating a battle system for my game and there's about a 15 frame window for you to land a powerful attack by pressing the down key (Probably going to change, but that's what it is for now)
It's all working perfectly fine EXCEPT for this small little tidbit, which kind of ruins the whole "action command" point. If I just hold down the "down" key, it does the same thing as timing it.
Is there a script or something I'd need instead of this? It would also be hard to fit in some more code, since the battle code is already very jam-packed with stuff already..
I can probably solve this with a ton of tinkering around but so far, nothing.

TL;DR: Conditional Branch, If button (Down in my case) held down, does the same thing as successfuly timing an attack in my "battle system" and how do I prevent

 

[Kaelan]

Can't you just add a buffer zone around those 15 frames, where the check always fails if the button is pressed? Like, if from when the attack starts you have:

attack starts => X frames (bad timing) => 15 frames (correct timing) => Y frames (bad timing) => attack resolves

Set the check to failed if the button is pressed during the X or Y frames. Only set it to succeeded during the middle 15 frames if it wasn't already set to failed. It would only ever pass if the player pressed the button during those 15 frames without pressing it too early or too late.

 

[JJGreyKK]

Well, uh, how do I have that be active during a move route..? It's made via events.

 

[standardplayer]

EDIT this is Ace, I can't remember if the solution is the same as MV. I lost my ACE product key and have emailed them a while back with no luck. Sorry ><

 

[Andar]

one way to do this would be to use a switch to detect changes.
Basically when the button is pressed, the switch is switched ON - and then all further loops skip the effect of button pressed, requiring the button to be released to reset the switch.

If done correctly only the first frame of button pressed will count.

 

[HexMozart88]

The way I'd do it would be to just do
Conditional Branch: Input.trigger?( :C)
Conditional Branch: timer variable is less than 15
Input.trigger? Checks if the button is pressed and not held.
Edit: Oops. It auto-corrected part of that to smiley face. I put a bit of a space there so that it doesn't but you can take it out after.

 

[JJGreyKK]

one way to do this would be to use a switch to detect changes.
Basically when the button is pressed, the switch is switched ON - and then all further loops skip the effect of button pressed, requiring the button to be released to reset the switch.

If done correctly only the first frame of button pressed will count.

Holy cow! I tried this for a bit to no avail, getting frustrated, then I changed one little thing;
Boom. Works perfectly.
I did it a bit differently, though..
This event of the battle itself is stuffed tight with tons of events, so I had to make a separate one.
Parallel process, If down, wait 20 frames (since 15 frame window) then set "attack failed" to ON. after 300 frames, set attack failed to OFF. If it's on between then, make a route that moves the player back as if they failed it.
Thanks, everyone that helped!
I'll update this if something goes wrong again, but probably not.

The way I'd do it would be to just do
Conditional Branch: Input.trigger?( :C)
Conditional Branch: timer variable is less than 15
Input.trigger? Checks if the button is pressed and not held.
Edit: Oops. It auto-corrected part of that to smiley face. I put a bit of a space there so that it doesn't but you can take it out after.

That could've worked, but I already solved it. Thanks, though!

 

[slimmmeiske2]

This thread is being closed, due to being solved. If for some reason you would like this thread re-opened, please report this post and leave a message why. Thank you.