NullReferenceException when transform.Find(string) STILL

It's hard or impossible to tell, from what you've provided (I did watch the video), what the problem is. I think it either has something to do with other code you're running, or you misspelled something. The reason the latter is a possibility, is that you're basing your code on strings. Not only does that make for less efficient code, but it also allows for errors to occur, that won't be picked up as errors, until you actually use the strings in-game.

I don't understand what "isShooter" is, so I'm leaving that out. I'll leave it up to you to verify that it isn't causing a problem.

var Gems : Rigidbody[]; // Resize and populate this array in the Inspector. var force : Vector3; private var whichGemIGot : Rigidbody;

function Start () { CreateGem(); }

function Update () { if (Input.GetButtonDown("Jump")) { whichGemIGot.AddRelativeForce(force, ForceMode.Impulse); } }

function CreateGem () { whichGemIGot = Instantiate(Gems[Random.Range(0, Gems.Length)], transform.position, transform.rotation) as Rigidbody; whichGemIGot.transform.parent = transform; }

Any time you find yourself imagining a numbered list of variables, it's a good bet that an array is a better way of storing and using the data. For Gems, It doesn't matter what you store them as, because Unity will reference the whole prefab. Everything has a Transform, so using Rigidbody[] is just a way to ensure that they all have that component. (If I were to use code like this in a project of my own, I would make "Gem" into a class that stored both a Rigidbody and a Transform, but this isn't necessary. It would just make the code use fewer CPU cycles.)

I changed your ForceMode to Impulse, because the default, ForceMode.Force, is designed to be applied over time, not instantaneously. (Multiplying what you'd use, if you kept it as ForceMode.Force, by Time.fixedDeltaTime, yields the number that makes sense.)

I would try to apply this different, array-based and string-less method, instead of trying to hunt down errors in your more verbose and complex code. If you still have null reference errors after doing so, it's probably best to edit this question until we can get this fixed for you.