Vector Thruster Missile Tutorial

[-Simply-ownage]

I realise my last few tutorials have been kinda stupid
and hard to understand,
ill try make this as simple as possible,
without offending anyone.

@name Vector Thruster Missile
@inputs Numpad
@outputs Vec:vector Mul Pos:vector
@persist T:entity Timer
runOnTick(1)

findByClass("player")
T = findResult(3)

# Finds T as the person who has been connected the longest, a target.

E = entity():isWeldedTo()

#Gets what you have welded the entity to, usually the rocket.

E:setMass(50)

#Sets the mass of the rocket a bit lower, just so that the mul actually makes a difference.

# Now you create a vector. A vector containts all 3 xyz co-ords for example
# Vec(x,y,z)

if (Timer > 300) {
Pos = (-T:pos() - -E:massCenter())
Vec = Pos*2 + $Pos*10}

# Adds a "Pos" so that you can use delta.
# Finds the Vector of the targets position, then removes it from the position of the Rocket.
# Now if there is a vec input on a vector thruster, how do you think this should be wired. Bare in mind, this is extremely simple and won't work very well.

if (Timer < 300) {
Pos=(-T:up()*500 - -E:massCenter())
Vec = Pos*2 + $Pos*8}

#Sends the rocket up into the air when activated.

if (Numpad) {Timer++}

#If you active the same numpad as the missile, then it will start the
#Timer, sending it up, then to its target.

if (!Numpad) {Timer = 0}

#If you turn the rocket off or it is destroyed, timer resets to 0.

if (Numpad) {
Mul = 20000}

#Sets the mul for the vector thruster.
#Experiment with this.

if (!Numpad) {Mul = 0}

Please dont critisize, i just see that some people wanna make some vector thruster missiles.

[Officer Tibbles]

Okay may I criticize? No? Okay I shall anyway.

You can't teach people through comments in the code. Do your tutorials, line by line, explaining thoroughly what each element does, and in the end, slap it together into a complete "Example" code.

For example...

I am going to be teaching you how to make a toggle switch!

Let's start off by pulling up your Expression 2 STool, found under "Control".

Start by adding an Input, let's call it "A", this is how your line should look.

@inputs A

Let's continue by adding an output, which will be our On / Off value. We shall call this, B.

@outputs B

Now for our code.

We will be using the operator, +=, which means, Increment Value C by D ammount. It looks like this.

C += D

Along with the increment, we will be using an If Then statement that follows the pattern of..

if(Input==E){Output=F}

Back to our project, let's apply these principles!

if(A) {B+=1}

What we just did is, If any input other than 0 is inputted (Remember, A is our input), then Increment B by 1.

Now for the reset.

if(B > 1) {B = 0}

If Value B is greater than 1, then it reset to 0.

Your code should look something like this.

@name Toggle
@inputs A
@outputs B
@persist

if(A){B+=1}
if(B>1){B=0}

This works by incrementing B until it is greater than 1, and resets it back to 0. Wire up a button to A (A non toggle button), and B to a screen.

As you press the button, the value changes to 1. If you press the button, it resets to 0 because it will have incremented to a value greater than 1.



^^ That is my tutorial.

[Milo]

Okay may I criticize? No? Okay I shall anyway.

You can't teach people through comments in the code. Do your tutorials, line by line, explaining thoroughly what each element does, and in the end, slap it together into a complete "Example" code.

For example...

yes your kinda rigth but, if somone uses this ingame it wuold be unconvinient to do this step by step... therefore commenting is a much greater way to stick it and use it and learn it.
Hard to do a tutorial changing between browser and gmod. ( little easyer by steams new webclient overlay) but it gets to tricky.
Thanks for your attension.

[eduardo]

thanks tibbles you're completely and totally correct 110% A+ EXCELLENT

as for milo......

[eurocracy]

Personally I think tutorials should contain both full code AND explanations :O

[singilli]

Like I do, I give full code and line by line explanation.

[Undomian]

Personally I think tutorials should contain both full code AND explanations :O

I'm against a tutorial giving the full code. If someone just comes in to copy the code at the end, they haven't learned anything, and all the time spend making that tutorial will have gone to waste.

[-Simply-ownage]

Is that better?