Press fire button Glitch? Design?

[camelman]

+Player Presses fire 1
+Player is standing on ground
-Shoot bullet

This says "If the player PRESSES (not IS HOLDING) fire 1, and is standing on the ground, shoot a bullet."

HOWEVER, It's acting like "repeat while fire 1 is pressed" in that, if I hold fire button 1 while player control is ignored, then restored, the player shoots a bullet anyway.

"Press fire button" is an immediate condition so I'm kinda confused as to why it's working like this. Seems like a bug to me. I can't think of a workaround :\

[LB]

Player 1 presses fire button: Set value to 1

Value is 1 & Player is on ground & Only one action when event loops: Set value to 0, shoot bullet.

[Namida]

...
Couldn't you just put Only One Action When Event Loops into the original event?

[Zethell]

indeed.

[N64Mario]

+Player Presses fire 1
+Player is standing on ground
-Shoot bullet

This says "If the player PRESSES (not IS HOLDING) fire 1, and is standing on the ground, shoot a bullet."

HOWEVER, It's acting like "repeat while fire 1 is pressed" in that, if I hold fire button 1 while player control is ignored, then restored, the player shoots a bullet anyway.

"Press fire button" is an immediate condition so I'm kinda confused as to why it's working like this. Seems like a bug to me. I can't think of a workaround :\

Yea, I see what you mean.

I have tried everything ppl suggested on this thread, and this fire button glitch STILL happens.

I guess what's happening is, since the control is ignored, every control/button you press/hold down wont do anything.
So when the control is restored, the events then recognize the condition. So it assumes you have just pressed fire button instead of actually pressing it, not holding it down. X_X

Kind of hard to explain, though maybe one of the clickteam admins can take a look into it, and see if they can correct this misatke?


Other than that, the best method, or work around for this is to use a 'fake' ignore control function. In other words, always have control functions on, but disable/enable groups that have events with user control conditions.

[variant]

Maybe try this.

-Variant

[LB]

...
Couldn't you just put Only One Action When Event Loops into the original event?

Um, that would do nothing because it's an immediate event.

[dsilvers]

Are you using the "Shoot Object" function or the "Create Object" function? You get a lot more control over your projectiles with the "Create Object" function. Just use a direction variable on the bullet that determines which way it is being shot (0 for left, 1 for right, or the other way around if you so prefer).

My other suggestion if you can't get it to not repeatedly shoot bullets is to put a time limiter on it and treat it as if you can shoot repeatedly with the button held down, but adding in "Every 1 Second" or whatever will keep it nice and clean and limit how much the event loops. Plus it'll save you a whole buncha RAM problems in the end.

[Zethell]

...
Couldn't you just put Only One Action When Event Loops into the original event?

Um, that would do nothing because it's an immediate event.

One thing i know for sure about clickteam products, is that nothing makes sense.

And it would probably work.

[nivram]

After you use CT products for a while, everything will start making sense. Be patient and have fun.

Marv