GLITCH??? Property>gameObject>gameObject>gameObject>gameObject>GameObject

[QFGlenn]

What is this I don't even

[jeanfabre]

Hi,

 Can you explain where you clicked to get there?

bye,

 Jean

[Lane]

Hi,

 Can you explain where you clicked to get there?

bye,

 Jean

Its when you drag a GameObject into the Get/Set Property action and then click to choose which property.

If you're trying to get the GameObject its easier to use another action to store it in a variable. I don't know why it's got so many layers, I've run into a something like that on other scripts and components, I figured it had something to do with the action returning a bunch of possible results even though they may not make sense - much like when coding you can type whatever you want but it may not do anything cohesive. I could see something like a generic GameObject returning all sorts of stuff that it isn't necessarily using.

[QFGlenn]

Haha, well I thought you guys would enjoy it. I wonder what would happen if I used the highest layer gameobject...

[Alex Chouls]

Most likely, this is just a result of drilling into the property. There are lots of circular references in unity properties, e.g., MonoBehaviors have a reference to the gameObject that owns them; so for example if you drill into guiText you can find gameObject, which has a guiText, which has a gameObject etc.

But it's possible something else is going on. I'll double check that nothing funky is happening... And maybe try to catch these circular references and not display them...