Please help i dont know what i did wrong but my cooldown doesnt work

Unity Engine
,
1 
using System.Collections;
using System.Collections.Generic;
using UnityEngine;

public class treedown : MonoBehaviour
{
    public bool PlayerLooking;
    int TreeHealth = 5;
    float ChopCooldown = 5f;
    bool ChopReset = false;
    float ChopResetCooldown = 5f;
    public void Update()
    {
      
        if(PlayerLooking)
        {
            Debug.Log("TreeScript succesfully raycast");
        }
        if (PlayerLooking && Input.GetMouseButtonDown(0))
        {
            if (ChopReset)
            {
              

                if (Time.time > ChopResetCooldown)
                {
                    float ChopResetCooldown = Time.time + ChopCooldown;
                    TreeHealth -= 1;
                    ChopReset = false;
                    Debug.Log(ChopResetCooldown);
                    Debug.Log(Time.time);
                    Debug.Log("Tapped 1");
                }

              


            }
            if (Time.time > ChopResetCooldown)
            {
              
                ChopReset = true;
              
            }
        }
        if(TreeHealth == 0)
        {
            Destroy(gameObject);
        }
    }

when i play in the editor , even though time.time is less than chopresetcooldown the if function still plays

2

Can you please edit your post to use code-tags and not plain-text which is extremely hard to read.

I’d also suggest, in placement for asking others to try to debug your code remotely, it’s worth following this guide that tells you how to best debug stuff yourself; it’s an essential skill that’ll make your dev like so much easier. :slight_smile:

3

Welcome to debugging! Here is how to debug your code:

Look closer at your code, you are making a local variable with the same name as an instance variable. You should not do this. But since you failed to format your code I cannot even tell you what line it is on, alas.

If you post a code snippet, ALWAYS USE CODE TAGS:

How to use code tags: https://discussions.unity.com/t/481379

You may edit your post above.

If my guess isn’t correct, you must find a way to get the information you need in order to reason about what the problem is.

What is often happening in these cases is one of the following:

  • the code you think is executing is not actually executing at all
  • the code is executing far EARLIER or LATER than you think
  • the code is executing far LESS OFTEN than you think
  • the code is executing far MORE OFTEN than you think
  • the code is executing on another GameObject than you think it is
  • you’re getting an error or warning and you haven’t noticed it in the console window

To help gain more insight into your problem, I recommend liberally sprinkling Debug.Log() statements through your code to display information in realtime.

Doing this should help you answer these types of questions:

  • is this code even running? which parts are running? how often does it run? what order does it run in?
  • what are the values of the variables involved? Are they initialized? Are the values reasonable?
  • are you meeting ALL the requirements to receive callbacks such as triggers / colliders (review the documentation)

Knowing this information will help you reason about the behavior you are seeing.

You can also supply a second argument to Debug.Log() and when you click the message, it will highlight the object in scene, such as Debug.Log("Problem!",this);

If your problem would benefit from in-scene or in-game visualization, Debug.DrawRay() or Debug.DrawLine() can help you visualize things like rays (used in raycasting) or distances.

You can also call Debug.Break() to pause the Editor when certain interesting pieces of code run, and then study the scene manually, looking for all the parts, where they are, what scripts are on them, etc.

You can also call GameObject.CreatePrimitive() to emplace debug-marker-ish objects in the scene at runtime.

You could also just display various important quantities in UI Text elements to watch them change as you play the game.

If you are running a mobile device you can also view the console output. Google for how on your particular mobile target, such as this answer or iOS: https://discussions.unity.com/t/700551 or this answer for Android: https://discussions.unity.com/t/699654

Another useful approach is to temporarily strip out everything besides what is necessary to prove your issue. This can simplify and isolate compounding effects of other items in your scene or prefab.

Here’s an example of putting in a laser-focused Debug.Log() and how that can save you a TON of time wallowing around speculating what might be going wrong:

https://discussions.unity.com/t/839300/3

When in doubt, print it out!™

Note: the print() function is an alias for Debug.Log() provided by the MonoBehaviour class.

4

thanks

5

thanks you so much

6

Ah, now that you have line numbers, line 27 is declaring a brand-new shiny variable, NOT using the class one you think it is. Fix that.