Developing for the Kinect is easier than you'd think.
The kinect provides us with a number of vectors representing specific bones. These are encoded into the usercommand (in the same way that mouse buttons and view angles are) and are available on the player object serverside, and in multiplayer - for prediction purposes - clientside.
To access these points you can call
Note that these positions aren't in world coordinates - so you will have to multiply them to get them to a usable size.
To access specific bones you can use these enums:
The motionsensor offers direct access to the sensor clientside, and a few utility functions sharedside.
This table contains subtables of bone ids allowing you to iterate it and draw bones.
Clientside - will return true if we have detected that there's a kinect connected to the PC.
Clientside - will return true if a kinect is connected - and active (ie - Start has been called).
Clientside - this starts access to the kinect sensor. Note that this usually freezes the game for a couple of seconds.