The Beginning of a Script

Tells my program about what cool stuff is about to go down.

Part 1 - Literally Making a Script.

Head into your ./paths/ folder (which should already be there). Here, I would suggest just copy-pasting one of the existing scripts there, and naming it whatever you'd like.

Then, go ahead and open it in Your Favorite Text Editor T.M.

I suggest VSCode, Atom, Sublime Text, or Notepad++ for writing these scripts. I plan to make a plugin sometime in the future that will give auto-complete functionality to VSCode or Atom, but that's a problem for another day.

Part 2 - The Properties of a Script.

So, if you followed the last step, you should already have 3 lines at the top of your script:

name: MyPath1
desc: A cool example path to teach how to use Creator's Camera.
versionMadeFor: 0.3

This part is pretty straight-forward.

Name: You can put whatever you want the name of your script to show up as in the program (it doesn't need to be the same as the filename).

Desc: This is where you can describe what this camera path does, so if you in 20 years is trying to use this script again, you'll have a slight idea of what in the world it was supposed to do.

VersionMadeFor: This just defines what version of the program this was made for, and the user will get a small warning if they try to run a new script on an old version of the program. So, if you're using v0.3, you just put 0.3. If you're using v2.9, you'd put 2.9. Simple enough.

capital letters are completely optional throughout the entire script. You're also free to use newlines wherever

you'd like.

If you want to leave notes that are ignored by the code, just put // in front of it. Ex:

//This line is ignored by the code.

(There's actually a bug at the moment where it doesn't always ignore the line)

Head onto the next page, where we'll make our script actually do something useful.