Search Unity

Bug Help my code isn't working

Discussion in 'Scripting' started by yukaizeng61, Nov 28, 2022.

  1. yukaizeng61

    yukaizeng61

    Joined:
    Nov 28, 2022
    Posts:
    2
    using System.Collections;
    using System.Collections.Generic;
    using UnityEngine;
    using UnityStandardAssets.CrossPlatformInput;

    public class player : MonoBehaviour
    {

    [SerializeField] float runSpeed = 10f;
    [SerializeField] float jumpSpeed = 10f;
    [SerializeField] float climbSpeed = 10f;

    RigidBody2D myRigidBody;
    Collider2D myCollider2D;
    Animator myAnimator;


    // Start is called before the first frame update
    void Start()
    {
    myRigidBody = GetComponent<RigidBody2D>();
    }


    // Update is called once per frame
    void Update()
    {
    Run();
    FlipSprite();
    Jump();
    ClimbLadder();
    }

    private void Run()
    {
    float controlThrow = CrossPlatformInputManager.GetAxis("Horizontal"); // value is between -1 to +1
    Vector2 playerVelocity = new Vector2(controlThrow * runSpeed, myRigidBody.velocity.y);
    myRigidbody.velocity = playerVelocity;

    myAnimator = GetComponent<Animator>();
    bool playerHasHorizontalSpeed = Mathf.Abs(myRigidbody.velocity.x) > Mathf.Epsilon;
    myAnimator.SetBool("Running", playerHasHorizontalSpeed);
    myAnimator.SetBool("Running", true);
    }
    private void ClimbLadder()
    {
    if (!myCollider2D.IsTouchingLayers(LayerMask.GetMask("Climbing"))) { return; }
    {
    myAnimator.SetBool("Climbing", false);
    myRigidbody.gravityscale = gravityScaleAtStart;
    return;
    }


    float controlThrow = CrossPlatformInputManager.GetAxis("Vertical");
    Vector2 climbVelocity = new Vector2(myRigidBody.velocity.x, controlThrow * climbSpeed);
    myRigidBody.velocity = climbVelocity;
    myRigidBody.gravityScale = 0f;

    bool playerHasVerticalSpeed = Mathf.Abs(myRigidBody.velocity.y) > Mathf.Epsilon;
    myAnimator.SetBool("Climbing", playerHasVerticalSpeed);

    }
    private void Jump()
    {
    if (CrossPlatformInputManager.GetButtonDown("Jump"))
    {
    Vector2 jumpVelocityToAdd = new Vector2(0f, jumpSpeed);
    myRigidBody.velocity += jumpVelocityToAdd;
    }


    myCollider2D = GetComponent<Collider2D>();

    if (!myCollider2D.IsTouchingLayers(LayerMask.GetMask("Ground"))) { return; }
    }

    private void FlipSprite()
    {
    bool playerHasHorizontalSpeed = Mathf.Abs(myRigidbody.velocity.x) > Mathf.Epsilon;
    if (playerHasHorizontalSpeed)
    {
    transform.localScale = new Vector2(Mathf.Sign(myRigidbody.velocity.x), 1f);
    }
    }
    }

    http://assets/Scripts/player.cs(13,... a using directive or an assembly reference?) idk what this error is helpp
     
  2. Kurt-Dekker

    Kurt-Dekker

    Joined:
    Mar 16, 2013
    Posts:
    38,697
    How to report your problem productively in the Unity3D forums:

    http://plbm.com/?p=220

    This is the bare minimum of information to report:

    - what you want
    - what you tried
    - what you expected to happen
    - what actually happened, especially any errors you see
    - links to documentation you used to cross-check your work (CRITICAL!!!)

    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.

    If you got this from a tutorial, go back because you made a mistake!

    Tutorials and example code are great, but keep this in mind to maximize your success and minimize your frustration:

    How to do tutorials properly, two (2) simple steps to success:

    Step 1. Follow the tutorial and do every single step of the tutorial 100% precisely the way it is shown. Even the slightest deviation (even a single character!) generally ends in disaster. That's how software engineering works. Every step must be taken, every single letter must be spelled, capitalized, punctuated and spaced (or not spaced) properly, literally NOTHING can be omitted or skipped.

    Fortunately this is the easiest part to get right: Be a robot. Don't make any mistakes.
    BE PERFECT IN EVERYTHING YOU DO HERE!!


    If you get any errors, learn how to read the error code and fix your error. Google is your friend here. Do NOT continue until you fix your error. Your error will probably be somewhere near the parenthesis numbers (line and character position) in the file. It is almost CERTAINLY your typo causing the error, so look again and fix it.

    Step 2. Go back and work through every part of the tutorial again, and this time explain it to your doggie. See how I am doing that in my avatar picture? If you have no dog, explain it to your house plant. If you are unable to explain any part of it, STOP. DO NOT PROCEED. Now go learn how that part works. Read the documentation on the functions involved. Go back to the tutorial and try to figure out WHY they did that. This is the part that takes a LOT of time when you are new. It might take days or weeks to work through a single 5-minute tutorial. Stick with it. You will learn.

    Step 2 is the part everybody seems to miss. Without Step 2 you are simply a code-typing monkey and outside of the specific tutorial you did, you will be completely lost. If you want to learn, you MUST do Step 2.

    Of course, all this presupposes no errors in the tutorial. For certain tutorial makers (like Unity, Brackeys, Imphenzia, Sebastian Lague) this is usually the case. For some other less-well-known content creators, this is less true. Read the comments on the video: did anyone have issues like you did? If there's an error, you will NEVER be the first guy to find it.

    Beyond that, Step 3, 4, 5 and 6 become easy because you already understand!

    Finally, when you have errors, don't post here... just go fix your errors! Here's how:

    Remember: NOBODY here memorizes error codes. That's not a thing. The error code is absolutely the least useful part of the error. It serves no purpose at all. Forget the error code. Put it out of your mind.

    The complete error message contains everything you need to know to fix the error yourself.

    The important parts of the error message are:

    - the description of the error itself (google this; you are NEVER the first one!)
    - the file it occurred in (critical!)
    - the line number and character position (the two numbers in parentheses)
    - also possibly useful is the stack trace (all the lines of text in the lower console window)

    Always start with the FIRST error in the console window, as sometimes that error causes or compounds some or all of the subsequent errors. Often the error will be immediately prior to the indicated line, so make sure to check there as well.

    Look in the documentation. Every API you attempt to use is probably documented somewhere. Are you using it correctly? Are you spelling it correctly?

    All of that information is in the actual error message and you must pay attention to it. Learn how to identify it instantly so you don't have to stop your progress and fiddle around with the forum.
     
    yukaizeng61 likes this.
  3. MelvMay

    MelvMay

    Unity Technologies

    Joined:
    May 24, 2013
    Posts:
    11,459
    Please edit your post to use code-tags. Also, please try to explain the problem and post the error in the forum. A wall of plain-text and saying it isn't working could mean anything. Your link is broken too.

    From what I can see, let me introduce you to the docs on the line it's telling you:

    Rigidbody2D

    See how it's spelled? See how you typed it.
     
  4. yukaizeng61

    yukaizeng61

    Joined:
    Nov 28, 2022
    Posts:
    2
    someone help me plz im autistic
     
  5. MelvMay

    MelvMay

    Unity Technologies

    Joined:
    May 24, 2013
    Posts:
    11,459
    I did help you above and told you what you spelled wrong.
     
    Kurt-Dekker likes this.
  6. Kurt-Dekker

    Kurt-Dekker

    Joined:
    Mar 16, 2013
    Posts:
    38,697
    What I wrote above has nothing to do with you or your condition and is entirely a function of how software engineering works.

    If you are able to follow the simple two-step process above, you might have success at software engineering.

    If you are unable to follow the simple two step process above, nothing anyone types here is going to help you.

    Also, where did you get this code? It has a lot of questionable things. For instance, this snippet:

    Code (csharp):
    1. if (!myCollider2D.IsTouchingLayers(LayerMask.GetMask("Ground"))) { return; }
    2. }
    Is actually useless, as it is at the end of a function that is going to return anyway.

    I suggest you check out some quality tutorial makers... and 100% of what I wrote above applies.

    Imphenzia / imphenzia - super-basic Unity tutorial:



    Jason Weimann:



    Brackeys super-basic Unity Tutorial series:



    Sebastian Lague Intro to Game Development with Unity and C#:



    Imphenzia: How Did I Learn To Make Games:



    Basics of Unity GameObjects and Components:

    https://youtu.be/9Nf2_ds5y8c