4.5
I’m mot sure on which one I should use for my project, and i’m also not sure what they do.
(I’m makimg my game on mobile, but I want any person with any gadget play my game, like pc or mobile.)
Is that mobile foward+ and compatibility thing only for me or it’s for people who will play my game?
And an off topic question, why is my timer overriding (or overwriting I don’t know.) itself? I thought one_shot stops that issue.
(This is off topic so you can choose not to answer this question.)
If affects both development and the final product.
About which one you should use:
Forward+ is for Desktop PCs with new hardware, if you want to use advanced rendering.
Mobile is kind of like Forward+ but for a variety of devices including mobile
Compatibility is the one-size-fits-all renderer that you use for everything else
What do you mean with “overriding itself”? Timer.one_shot stops the timer from restarting after it’s finished
So imagine this..
There’s a red button that starts a timer when pressed…
and then when the timer is finished, print something or whatever.
but the thing is that the timer isn’t finishing because the player keeps pressing the red button, so the timer is being overriden or something.
(Not sure if this even makes sense.)
Are you starting the timer in _process, like this?
if timer.button_pressed:
timer.start()
If so, it is probably better to use the signal pressed instead because that only fires once
I’m using Input.is_action_just_pressed
In my physics update( not physics process because I changed the name to physics update for my state machine.)
Edit:
Nevermind I was wrong. This problem is deeper than I thought, you can leave this reply if you want.
In your pressed function, just check if the timer is still running and don’t restart it if it is. That will solve your problem.
If the player presses the button five times before the time runs out, what do you want to happen? Do you want it to trigger five times? Or only trigger from the first push? Or the last?
Don’t worry! I fixed it already.
Just a note: a more articulate answer could have been useful, e.g.
I wanted to do <something>
using this <code>
but the result is <unwanted result>
@<username> answer helped/solved my problem, so now my code is
<working code>.
Timers are trivial (when you know how to use them), but it’s the principle that matters, imho.
I didn’t explain my issue properly, and I knew it was a simple issue so I just fixed it myself.
(I was making a dash cooldown timer, and when the timer is not active then you can dash I think, I forgot.)