-
-
Notifications
You must be signed in to change notification settings - Fork 21.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add time scale property to Timer node #34544
Add time scale property to Timer node #34544
Conversation
19222e2
to
70a27e6
Compare
@wingedadventurer Is this still desired? If so, it needs to be rebased on the latest master branch. |
5be6004
to
376d441
Compare
376d441
to
3de51a3
Compare
3de51a3
to
d9b17a4
Compare
d9b17a4
to
cdbef37
Compare
cdbef37
to
c08dbd1
Compare
c08dbd1
to
5960f9e
Compare
I don't see a proposal attached to this pull request. Additionally, just using Timer::set_wait_time and multiplying that time for a scale value will result in exactly the same effect, for which adding an extra function looks of little use to me. I suggest closing it. |
This was discussed on Godot's RocketChat. The consensus is that this change is not necessary as it can be easily worked around, and therefore this PR is not desired. Closing. |
Not if you need to engage slow motion and then turn it off, and then on again with a different multiplier, while the timer is ticking. |
Adds time scale property to the Timer node, allowing it to tick faster/slower.
Useful if you are implementing slow motion mechanic, and want specific Timer nodes to behave accordingly (
Engine.time_scale
won't cut it as it is applied to every node). Think games like Superhot, where game timer can either tick in real-time or in slowmo-time.