I can't solve the infinite Wall jump problem

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

public class Player : MonoBehaviour
{
    private Rigidbody2D rb;
  
    //Laufen:
    public float speed;
    private float moveInput;
    private bool FacingRight = true;

    //Jumping:
    public float jumpForce;
    private int extraJumps;
    public int extraJumpsValue;
    private float JumpTimeCounter;
    public float Jumptime;
    private bool isjumping;
    //Wallslide/jumping:
    private bool Wallsliding;
    public float Wallslidingspeed;
    private bool Walljumping;
    public float xWallForce;
    public float yWallForce;
    public float WallJumpTime;

    //Checking True/false:
    private bool isTouchingFront;
    public Transform frontCheck;
    private bool isgrounded;
    public Transform groundCheck;
    public float checkRadius;
    public LayerMask whatisGround;

    void Start()
    {
        rb = GetComponent<Rigidbody2D>();
        extraJumps = extraJumpsValue;
    }

    //Physics:
    void FixedUpdate()
    {
        //Movement:
        moveInput = Input.GetAxis("Horizontal");
        rb.velocity = new Vector2(moveInput * speed, rb.velocity.y);
        //Springen:
        isgrounded = Physics2D.OverlapCircle(groundCheck.position, checkRadius, whatisGround);


        //Richtungwechsel beim Laufen:
        if (FacingRight == false && moveInput > 0)
        {
            Flip();
        }
        else if(FacingRight == true && moveInput  < 0)
        {
            Flip();
        }
    }

    private void Update()
    {
        //Springen:
        if(isgrounded == true && Input.GetKeyDown(KeyCode.Space))
        {
            isjumping = true;
            extraJumps = extraJumpsValue;
            JumpTimeCounter = Jumptime;
        }

        if (Input.GetKeyDown(KeyCode.Space) && extraJumps > 0)
        {
            rb.velocity = Vector2.up * jumpForce;
            extraJumps--;
        }
        else if (Input.GetKeyDown(KeyCode.Space) && extraJumps == 0 && isgrounded == true)
        {
            rb.velocity = Vector2.up * jumpForce;
        }

        //Super Jump:
        if (Input.GetKey(KeyCode.Space) && isjumping == true) {
            if(JumpTimeCounter > 0)
            {
                rb.velocity = Vector2.up * jumpForce;
                JumpTimeCounter -= Time.deltaTime;
            }
            else
            {
                isjumping = false;
            }
        }
        if(Input.GetKeyUp(KeyCode.Space))
        {
            isjumping = false;
        }

        //Wallsliding/jumping:
        isTouchingFront = Physics2D.OverlapCircle(frontCheck.position, checkRadius, whatisGround);

        if (isTouchingFront == true && isgrounded == false)
        {
            Wallsliding = true;
            rb.velocity = new Vector2(rb.velocity.x, Mathf.Clamp(rb.velocity.y, -Wallslidingspeed, float.MaxValue));
        }
        else
        {
            Wallsliding = false;
        }
        if (Input.GetKeyDown(KeyCode.Space) && Wallsliding == true)
        {
            Walljumping = true;
            Invoke("SetWallJumpingToFalse", WallJumpTime);
          
        }

        if (Walljumping == true)
        {
            rb.velocity = new Vector2(xWallForce, yWallForce);
        }
    } 

    //Richtungswechsel beim laufen (Aktion):
    void Flip()
    {
        FacingRight = !FacingRight;
        Vector3 Scaler = transform.localScale;
        Scaler.x *= -1;
        transform.localScale = Scaler;
    }
    //Walljumping immer aus (Aktion):
    void SetWallJumpingToFalse()
    {
        Walljumping = false;
    }
  
}

I can’t find an easy way without completely rewrite my code to get rid of my infinitely Wall jump problem.
I’m really frustrated because even YouTube couldn’t help me at all. Pls help me, I’m Jung and dumb :slight_smile:

2

That’s a lot of very complicated if() statements with lots of different conditions.

I recommend untangling it a bit so that each if() statement (ideally) only checks one quantity.

Otherwise, time to start debugging! Wall-jumping code has to be debugged just like any other code.

Here is how you can begin your exciting new debugging adventures:

You must find a way to get the information you need in order to reason about what the problem is.

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

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 names of the GameObjects or Components involved?
  • 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.

Visit Google for how to see console output from builds. 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 for iOS: How To - Capturing Device Logs on iOS or this answer for Android: How To - Capturing Device Logs on Android

If you are working in VR, it might be useful to make your on onscreen log output, or integrate one from the asset store, so you can see what is happening as you operate your software.

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:

“When in doubt, print it out!™” - Kurt Dekker (and many others)

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

3

Thank you very, very much, it helped me a lot <3