Search Issue Tracker

Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.




Found in







Issue ID




A warning is thrown in the Console window when a non-MonoBehaviour script is added to the project with a name of a component



How to reproduce:
1. Create and open a new project
2. Drag and drop the attached 'Transform.cs' script into the Project window
3. Observe the Console window

Expected result: no warnings are thrown
Actual result: a warning is thrown (even though the script is not a MonoBehavior)

Reproducible with: 2017.4.37f1, 2018.4.18f1, 2019.3.4f1, 2020.1.0a26, 2020.2.0a1

Full warning:
Script 'Transform' has the same name as built-in Unity component.
AddComponent and GetComponent will not work with this script.
UnityEditorInternal.InternalEditorUtility:ProjectWindowDrag(HierarchyProperty, Boolean)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr, Boolean&)

  1. Resolution Note (2020.2.X):

    Hi, we decided to revert the previous fix as it turns out it requires a change which would take around a month or so of work. As this is relatively low user-pain and there are workarounds around this. In the meantime, we will close the bug and add it to our backlog to be implemented while the necessary changes (which are planned to land sometime in the future) will be implemented first. Hope you understand our decision!

Comments (1)

  1. Edy

    Mar 22, 2024 13:19

    Please fix this. It's really annoying as we can't use a lot of names that are commonly used when developing libraries.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.