Attack 2 enabled collider appears before Attack 1 disabled collider Causes Attack 2 collider Enable to be missing

[chen90166]

I’m making is a 3D act game

I have a question as in the title

when Attack 2 Enable Collider Immediately Attack 1 Disable Collider

The result is that Attack 2 collider is not enabled correctly, causing the attack to fail.

How to solve this problem

This is my C script

public void EnableWeaponCollider(int isEnable)
    {
        //
        if (weapon != null)
        {
            var col = weapon.GetComponent<Collider>();

            // 
            if (col != null)
            {
                if (isEnable == 1)
                {
                    col.enabled = true;

                    // 
                    if (disableColliderCoroutine != null)
                    {
                        StopCoroutine(disableColliderCoroutine);
                    }
                }
                else
                {
                    // 
                    disableColliderCoroutine = StartCoroutine(DisableColliderAfterDelay(col, 1f));
                }
            }
        }
    }

[Kurt-Dekker]

@chen90166

How to solve this problem

By debugging!

Sounds like you wrote a bug… and that means… time to start debugging!

By debugging you can find out exactly what your program is doing so you can fix it.

Unity - Manual: Debug C# code in Unity

Use the above techniques to get the information you need in order to reason about what the problem is.

You can also use Debug.Log(...); statements to find out if any of your code is even running. Don’t assume it is.

Once you understand what the problem is, you may begin to reason about a solution to the problem.

Remember with Unity the code is only a tiny fraction of the problem space. Everything asset- and scene- wise must also be set up correctly to match the associated code and its assumptions.

My first guess would be inappropriate use of coroutines.

Is this just a cooldown timer? Then make it 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 (User…

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

Again I would not reach for coroutines here. The reason: you can go below the critical health, then go up, then go back down, and every single point in there is a chance to screw up how many coroutines are actually running. Coroutines are great but they are the wrong solution for this problem. Instead, make a heartbeat script and have a variable to count if it is time yet: private float heartBeatYet; In your Update() function, calculate the desired rate of heartbeat based on health: float …

“Why not simply stop having so many coroutines ffs.” - orionsyndrome on Unity3D forums

[chen90166]

No this is not cooldown timer

Maybe I should describe my project more accurately

This is my project

https://www.youtube.com/watch?v=LL5_9uegJJw

Attack 1 → Attack2 (or 3 )

Probabilistic missing collider enabled

The reason is like the picture in my post

How to solve the problems caused by this sequence

[Kurt-Dekker]

@chen90166

How to solve the problems caused by this sequence

Again, by debugging. See above.