Vehicle help

Seriously, ins$$anonymous$$d of gessing like that, why don't you try reading the manual? This stuff is really, really basic- you should read through and absorb everything there is in the scripting reference, because there are code examples for everything you might want to do, and only come here when you have a question which isn't covered by that.

Aye, when it comes to program$$anonymous$$g, danger begins when you start guessing. :) It actually takes a lot of discipline to never make "guesses", especially when you become just a little experienced and code starts flowing more easily. But as a cardinal rule: You must never write code that you "guess" is right. You must always know exactly what something does, and preferably exactly WHEN it does it.

I would rather have a shoddy piece of code, poorly written and perfor$$anonymous$$g poorly, but written by $$anonymous$$E so I understand it, than a well-written, complex function that runs fast, but that I copy-pasted, so it might use mathematics I don't understand, or language features I've never heard of. Why? Because I can fix and improve something I understand. If something I do later on breaks the code I copy-pasted in, I'll be helpless to fix it.

Does that mean you should never take and use the code others have written? No, certainly not. But it means you should never take and use the code others have written WITHOUT UNDERSTANDING IT FIRST. That last part is key, because it's how all programmers learn; we study each other's code. :)