I need help with my 2D movement

[Kurt-Dekker]

I wouldn’t use coroutines for cooldowns. I mean you can, but it has all kinds of weird edge cases if somehow two of them get started.

Just use a cooldown timer.

Cooldown timers, gun bullet intervals, shot spacing, rate of fire:

Fire Rate Issues

This is commonly called a "cooldown timer." You can google for examples and tutorials, but the simplest way is this: have a private float gunHeat; variable In Update(), if that variable is greater than zero, subtract Time.deltaTime from it (this cools down the gunHeat) if (gunHeat > 0) { gunHeat -= Time.deltaTime; } When you go to fire: --- A. only fire if that gunHeat variable is zero or less. --- B. set that variable to the time (in seconds) you want to have between shots. if (Us…

GunHeat (gunheat) spawning shooting rate of fire:

Spawning after amount of time without spamming

Don’t use a Timer… that’s super overkill. Instead, use just a float. I like to call my float “gunHeat.” private float gunHeat; private const float TimeBetweenShots = 0.25f; // seconds Now… in Update(): // cool the gun if (gunHeat > 0) { gunHeat -= Time.deltaTime; } // is the player asking to shoot? if (PlayerAskedToShoot) { // can we shoot yet? if (gunHeat <= 0) { // heat the gun up so we have to wait a bit before shooting again gunHeat = TimeBetweenShots; // DO…

Coroutines are NOT always an appropriate solution: know when to use them!

Things to check before starting a coroutine?

The main thing to check before calling / making a coroutine is to ask yourself, “Does this even need to be a coroutine?” Generally, if your design requires you to call StopCoroutine(), then don’t make it a coroutine. If you just need something to happen a bit later, this is a more-robust approach: https://gist.github.com/kurtdekker/0da9a9721c15bd3af1d2ced0a367e24e If you’re flipping from one value to another, such as fading in, fading out, changing speeds slowly, etc., coroutines are an AW…

Heartbeat courutine fx

There’s never a need. As @PraetorBlue pointed out in a recent post of his, nobody NEEDS coroutines. They do solve a certain class of problem nicely however, primarily problems of sequencing a set of data or events to happen. Coroutines CAN be interrupted and restarted but doing so exponentially increases your chance of a bug, negating a lot of their inherent benefits. A lot of human behaviors are good coroutines: “Go take a shower.” So that breaks down to: get undressed start the shower …