Search Unity

  1. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  2. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

How can I stop my string value from going mad?

Discussion in '2D' started by lordark3567, Jun 12, 2022.

  1. lordark3567

    lordark3567

    Joined:
    Jun 12, 2022
    Posts:
    1
    I try to make an enemy where if it dashes through you but I want to flip it and change the dash speed negative when we are behind the said enemy. but this code result in the "dash" value going from -20 to 20 (20 is the value I give it in the public menu) repeatedly and the character flipping nonstop. What can I do to prevent this?

    bool Detected = false;
    Vector2 Direction;

    public Animator animator;

    public Rigidbody2D rb;

    public bool detected;

    public BoxCollider2D box;

    public Transform player;

    public float dash;

    IEnumerator Flip()
    {

    yield return new WaitForSeconds(0.2f);
    animator.SetBool("Attack", false);
    rb.velocity = new Vector2(0f, 0f);


    }
    private void OnTriggerEnter2D(Collider2D collider)
    {
    if (collider.gameObject.CompareTag("RTE"))
    {

    detected = true;
    }

    if (detected = true)
    {


    GetComponent<BoxCollider2D>().enabled = false;


    animator.SetBool("Attack", true);

    rb.velocity = new Vector2(rb.velocity.x, 0f);
    rb.AddForce(new Vector2(dash, 0f), ForceMode2D.Impulse);

    detected = false;
    StartCoroutine(Flip());
    }
    }
    void FixedUpdate()
    {
    if (player.position.x - transform.position.x > 0)
    {
    dash = Mathf.Abs(dash);

    }

    if (player.position.x - transform.position.x < 0)
    {

    dash *= -1;
    Flipy();
    }


    }

    void Flipy()
    {

    transform.localScale = new Vector2(transform.localScale.x * -1, transform.localScale.y);

    }
     
  2. Kurt-Dekker

    Kurt-Dekker

    Joined:
    Mar 16, 2013
    Posts:
    38,522
    Steps to success:

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

    How to use code tags: https://forum.unity.com/threads/using-code-tags-properly.143875/

    You may edit your post above.

    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.

    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://forum.unity.com/threads/how-to-capturing-device-logs-on-ios.529920/ or this answer for Android: https://forum.unity.com/threads/how-to-capturing-device-logs-on-android.528680/

    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://forum.unity.com/threads/coroutine-missing-hint-and-error.1103197/#post-7100494