neogoo123

And the ability to use STATUS in if's or until's or other everythings.... I JUST WANNA "UNTIL STATUS = "LANDED" {BLAHBLAH}."

lol, them periods! Well I'm glad to hear it! I was just gunna hop into KSP and see if I could get something to work using what we've just learned..... Though now I feel challenged to create some automated re-entry craft.... I have Ferram's Aerospace Research downloaded as well as Deadly Re-entry.... this should be fun.... If I get it to work I will make a video.

@mushroomman Yea I was just thinking about that... welp, now we know, though it seems blatantly obvious now...

If you copied it directly, then it won't work, I just noticed that I wrote verticalspeed wrong on the second line, there can not be a space in between the vertical and speed, all one word... so: until verticalspeed = 0{ if verticalspeed > 10{ set tVal to tVal + 0.1. }. }.

It's because you don't have it in a loop. otherwise it will just go through the if statement once then go on its way. Do something like this: until verticalspeed = 0{ if vertical speed > 10{ set tVal to tVal + 0.1. }. }. If I'm not mistaken that should work, please correct if I'm wrong.

I'm not entirely sure if this has been brought up by anyone, but I think It hasn't been, but will you be adding a part for probes and 2.5 meter rockets?

I... Don't even know... Meh, guess I got into the routine of adding all the separate rotations from his tutorials... the word up in the language actually means directly away from the planet or object that has gravity. AKA, directly upwards from the center of the planet to and through the sky. It just makes it easier to modify your rotations. With out the UP you would have modify your steering every few seconds. If you just do LOCK STEERING TO R(0,0,90) while in orbit, then it will face it directly in that direction always. If you do LOCK STEERING TO UP + R(90,0,0) then You will face towards the north pole and will twist to face away from the planet at all times, it will rotate by itself... that type of thing... a better description is on the github page.

The first x is for the x-direction, the second is for the y-direction, and the third is for the z-direction. IF I'm not mistaken. It makes sense though. ex: Pointing a craft to the sky and towards the east at an approximate 70 degree's would require "LOCK STEERING TO UP + R(0,0,180) + R(0,-30,0)" again, that is if I'm not mistaken. v(x,x,x) means Vector in a certain direction. Ex: v(0,90,0) (I never use the v(x,x,x) so I don't know much about it.) r(x,x,x) I guess means radians. I don't know though, it could just mean roll. Ex: r(0,0,180)

Though I would love to see this put with the game intrinsically, not everyone wants to learn a new programming language, nor should they be forced upon it by put it in the base game... I would prefer it stay a mod, for everyone's benefit. Though I do hope programming in KSP becomes a wider thing, as I have only seen a few programming mods, and only one of which actually allowed you to program in-game... eh-hem... this one. So I would love to see this style of programming more, and in different languages so that all types of programmers, from newbies to pro's can enjoy the feeling of control from their own experience level. This is all personal feelings though, and take them with a grain of salt, as I am just a mere script kiddie in comparison to many others.

I don't know about anybody else, but I do not have this issue... Are you sure that you are putting the period at the end of each of the statements? Ex: set x to 3. until x < 0 { print x. if x = 0 { stage. }. set x to x - 1. }.

Wow, haven't seen anything DCPU-16 based in quite a while. I WAS waiting for the space ship control that would have been allowed if "0x10c" (the game made by notch) were going to come out, but now that that's just a thing on the ol' shelf my plans where dwindling. This has revitalized my enthusiasm for the DCPU-16, and If you need anybody to help with dev work, be it actual programming, ideas, or the like, please, contact me! Hope to see this go far!