Is it possible to change the parent of an instantiated prefab from another script?

[frankiwinnie]

Hello everyone,

I am trying to change the parent of an instantiated prefab from another script which does not contain the actual "Instantiate(prefab, parent) code. So in one script, I instantiate prefab into a parent and in another script I am trying to reach that instantiated prefab and change its parent. Is it possible?

When I try that, I am always having the error of “setting the parent of a transform which resides in a prefab asset is disabled to prevent data corruption”.

Thank you,

[Kurt-Dekker]

You’re attempting to change the prefab itself, not the instance that you made.

Instead, store a reference to what is returned by Instantiate() and change that.

If it’s in another script, the way you get it over is always this pattern:

Referencing variables, fields, methods (anything non-static) in other script instances:

Help creating function for changing vars in another script

Like all inter-script interaction, all you need is: Script A needs a reference to script B, which you will populate in the editor: // inside of ScriptA: public ScriptB myBScript; Script B needs to have something public that script A can change: // variable / field inside of ScriptB: public int myFooInteger; // function inside of ScriptB: public void DoStuff( string reason) { } Script A can then change it directly using the reference to B: // here is ScriptA accessing something in Scrip…

accessing a gameobject in different scene

within a class there are reference to gameobjects in the scene A, the same gameobjects are available in the scene B. i have dragged the gameobjects in scene A into inspector fields. now how to reference these gameobjects in the scene B via script into relevant fields in the inspector? please give me some idea. thanls.

REMEMBER: it isn’t always the best idea for everything to access everything else all over the place. For instance, it is BAD for the player to reach into an enemy and reduce his health.

Instead there should be a function you call on the enemy to reduce his health. All the same rules apply for the above steps: the function must be public AND you need a reference to the class instance.

That way the enemy (and only the enemy) has code to reduce his health and simultaneously do anything else, such as kill him or make him reel from the impact, and all that code is centralized in one place.