Search Unity

Question How to fix "The name 'transform' does not exist in the current context" error in my code

Discussion in 'Getting Started' started by unity_006662, Aug 24, 2023.

  1. unity_006662


    Aug 23, 2023
    So I'm new to Unity coding, and I have an error in my enemy code which says (what's in the title), that "The name 'transform' does not exist in the current context".

    Here's the whole code:
    Code (CSharp):
    1. using System.Collections;
    2. using System.Collections.Generic;
    3. using UnityEngine;
    5. public class Bat : Idamage
    7. {
    8.     Animator animator;
    10.     public Transform target;
    11.     public float chaseRadius;
    12.     public float attackRadius;
    13.     public Transform homePosition;
    14.     public float moveSpeed;
    16.     Rigidbody2D rb;
    18.     bool isAlive = true;
    20.     public float Health
    21.     {
    22.         set
    23.         {
    24.             if(value < _health)
    25.             {
    26.                 animator.SetTrigger("Hit");
    27.             }
    29.             _health = value;
    30.             print(value);
    32.             if (_health <= 0)
    33.             {
    34.                 animator.SetBool("isAlive", false);
    35.             }
    36.         }
    37.         get
    38.         {
    39.             return _health;
    40.         }
    41.     }
    43.     public float _health = 3;
    45.     void Start()
    46.     {
    47.         target = GameObject.FindWithTag("Player").transform;
    48.         animator = GetComponent<Animator>();
    49.         animator.SetBool("isAlive", isAlive);
    50.         rb = GetComponent<Rigidbody2D>();
    51.     }
    53.     void Update()
    54.     {
    55.         CheckDistance();
    56.     }
    58.     void CheckDistance()
    59.     {
    60.         if(Vector3.Distance(target.position,
    61.                             transform.position) <= chaseRadius
    62.             && Vector3.Distance(target.position,
    63.                                 transform.position) > attackRadius)
    64.         {
    65.             transform.position = Vector3.MoveTowards(transform.position, target.position, moveSpeed * Time.deltaTime);
    66.         }
    67.     }
    70.     public void OnHit(float damage, Vector2 knockback)
    71.     {
    72.         Health -= damage;
    73.         rb.AddForce(knockback);
    74.         Debug.Log("Force" + knockback);
    75.     }
    77.     public void OnHit(float damage)
    78.     {
    79.         Health -= damage;
    80.     }
    81. }
    The error is in line 65
    Code (CSharp):
    1.             transform.position = Vector3.MoveTowards(transform.position, target.position, moveSpeed * Time.deltaTime);
    I don't really see where the error is. I have tried restarting Unity, but it didn't fix anything. I had this line of code for a while, and the error didn't come up until now. Sorry! I'm new to this kind of thing.
  2. tleylan


    Jun 17, 2020
    This isn't a "restart" sort of issue. That transform reference isn't declared anywhere. It is a property of "something" so you need to start by referencing it, e.g. myObject.transform.position. I'll also suggest expressly setting private properties to "private" and _health should not be public if you have a getter/setter for it which is public.
  3. Kurt-Dekker


    Mar 16, 2013
    Always start with the docs.

    From the docs you'll see the .transform property is a shortcut of MonoBehaviour.

    Your script is not inheriting from that base class, just the Idamage interface, whatever that is.

    If you're gonna follow tutorials, make sure you're not wasting your time by doing it blindly:

    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.

    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.

    When you have an ACTUAL error rather than simply not following directions...

    How to report your problem productively in the Unity3D forums:

    This is the bare minimum of information to report:

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

    The purpose of YOU providing links is to make our job easier, while simultaneously showing us that you actually put effort into the process. If you haven't put effort into finding the documentation, why should we bother putting effort into replying?

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

    How to use code tags:

    - Do not TALK about code without posting it.
    - Do NOT post unformatted code.
    - Do NOT retype code. Use copy/paste properly using code tags.
    - Do NOT post screenshots of code.
    - Do NOT post photographs of code.
    - ONLY post the relevant code, and then refer to it in your discussion.
    bugfinders likes this.
  4. unity_006662


    Aug 23, 2023
    Thanks! I've gone through the code and found the error, and thank you for the tips, I'll keep them in mind!
  5. MelvMay


    Unity Technologies

    May 24, 2013
    Please don't use the 2D forum for scripting/typo/learning issues. Please use it for 2D specific issues.

    I'll move your post to the Getting Started forum.