if any issues from this site please contact @ twitter id- http://twitter.com/dinezhdotcom

When you put a word in square brackets before a type, variable, or method declaration, that’s called an Attribute.

Attributes are special classes that annotate the declaration with metadata and can be used via reflection as hints for code generation, serialization, or drawing appropriate controls in Inspector UI. For example, when you write [Range(0, 1)] over a public or serialized float variable, that signals to the Unity inspector to draw that field as a slider instead of just a numeric input box. The RangeAttribute class is the one that stores this metadata about the field.

When you write [Button] above a method, the compiler is going to look for a class named Button or ButtonAttribute that can be used as an attribute to annotate that method. It searches the namespaces you’ve imported with your using statements at the top of the file.

In this case, the only Button it can find is UnityEngine.UI.Button, and that’s descended from UnityEngine.Component, not System.Attribute. So the compiler is telling you that you cannot use this class as though it were an attribute, when it isn’t one.

Maybe you meant to refer to a different thing also named Button? If so, it’s likely that it’s in a different namespace, and you need to import that namespace with using Somenamespace; or specify the exact path to it, like [SomeNamespace.Button] instead of the unqualified [Button] each time you use it.

If you go the using route, you may need to disambiguate, something like…

using UIButton = UnityEngine.UI.Button;
using InspectorButton = Somenamespace.ButtonAttribute;

…ensuring you can unambiguously refer to the two similarly-named types with distinct names of your choosing.

Or these attributes might have been added in error. Maybe you copied them from an example where someone was using a library similar to this one to add clickable buttons in the Inspector for the component, but that library is not a part of your project at the moment. If you want this functionality, you’ll need to include the library and update your references to its namespace/attributes as above.

Or, if you don’t want this functionality, you can simply delete the [Button] lines to clear this error.

Credit goes to the respective owner!

Leave a Reply

Your email address will not be published. Required fields are marked *