0.3

0.3.3

ROS implements assembly (as described in 0.3.1 changelog). Same caveats apply.

0.3.2

0.3.1

import is now limited to a default list of assemblies.

To get access to types in other assemblies (including other mods) access them through assembly.

For example: First name after “assembly” is the assembly name, followed by any namespaces or types.

assembly.UnityEngine.UnityEngine.Vector3

Note: For assembly names with non-word characters like “Assembly-CSharp” this does not work. You will see them listed in the possible completion results, but if you try to complete you will get something that looks to Lua like some sort of different operation. In the following case, for example, it looks like a subtraction operation: assembly.Assembly-CSharp. Also, it would treat assembly.System.Core (“System.Core” is an assembly name) as an attempt to find a namespace “Core” in an assembly called “System”. For names like this you can do assembly["Assembly-CSharp"].

However, it is still useful to use intellisense in order to see what the names are of the various assemblies. Intellisense will show you all the loaded assemblies when you type assembly.. If you have a mod you want to interact with, it will most likely have an assembly name very similar to the name of the mod. And you can use that in assembly["assemblyName"].

Intellisense won’t work directly on asssembly["assemblyName"]., but it will work after you’ve assigned the result to another variable.

i> a=assembly["assemblyName"]
r> void
i> a. -- this will show completions for the assembly named "assemblyName"

Right now “assembly” is not implemented in ROS because ROS is undergoing a redesign. When the redesign is finished features like these will be implemented quickly.

0.3.0

New Import System:

listtype=import.system.collections.generic.list. Using the import system you can interact with any loaded libraries (included loaded mods) written in C#. You should check out the licenses of those mods/libraries prior to writing any code that depends on them. However, many mods have very permissive licenses. This feature organizes all types in the namespace they are found in C#.

For import namespace/type accesses are case insensitive. This is to provide compatibility with ROS’s general case insensitive nature. In Lua, the returned type will still have its member accesss be case sensitive, but the type and namespace name in import is going to be case insensitive. so listtype=import.System.Collections.Generic.List works the same as listtype=import.system.collections.generic.list.

Import currently takes generic types like List<T> and sets their type parameters to typeof<object>. So import.system.collections.generic.list returns the Type List<object>. This may change in the future, or be implemented differently in ROS and Lua.

For ROS, import is named “reflect” so

var alist=new reflect.system.collections.generic.list
alist.add 1
alist[0]

For Lua, All of the C# classes that were in the CommonScriptAPI will only be available through the Import system. Most are in the default namespace “”. Example:

editor=import.EditorLogic.fetch
ship=editor.ship
partloader=import.PartLoader.Instance

KSP has a system for getting the instance of a class that sometimes involves “fetch” and sometimes uses “Instance”. You have to check which one works with a given class and use that.

Less Bad Autopilot.

Now works to some extent with control surfaces.

Also can set a relative direction consisting of a heading and pitch. Heading is degrees from north (clockwise), and pitch is degrees above the plane perpendicular to the vector connecting the vessel and the body. This is an easier way to specify the direction you want it to point. It is relative to the closest body.

ctrl=import.RedOnion.KSP.Autopilot.FlightControl.GetInstance()
ctrl.SetRel(90,20) -- Aims ship east with a 20 degree pitch above "horizon" (by horizon I mean the plane perpendicular to the vector connecting the vessel and the body rather than the point at which the sky meets the land.)

Better Lua Repl Interaction

Lua no longer requires or allows “=” at start to return a value to the repl. Will automatically return the value of a lone expression entered at the repl. Note: this only works for single expressions.

i> alist[0] -- works

i> alist=new(List)
alist[0] -- doesn't work

i> =alist[0] -- no longer works

Repl/Editor settings

Repl/Editor saves it’s position, Repl visibility status, and Editor visibility status.

Lua Constructor

Lua now has a function for constructing types into instances. Called new(). Can construct an instance of a class using a type imported using the new Import system.

i> List=import.System.Collections.Generic.List
r> void
i> alist=new(List)
r> void
i> alist.Add(1)
r> void
i> alist[0]
r> 1

Better Lua intellisense

Lua Intellisense now knows whether a reference is static or an instance variable, so it no longer lists all the instance members of a class in the context of a static class reference.

0.2:

0.2.1:

0.2.0:

General:

ROS:

Documentation:

Lua:

Scripts:

Videos: