Subscribe to download
transferCTRLs

Players Script: Ever wish cockpits movement could control things other than wheels and thrusters? How about those items on a subgrid? Wish no more, as with transferCTRLs you'll transfer your WASD and mouse control to a group of devices of your choosing!

That said, this script concerns itself with axial and gyroscopic movements and translating them to objects of user choice, which reduces controller hotbar configs and simplifies advanced control schemas such as cranes, welder arms, gravity drives, VTOLS, projection movement, etc.

IMPORTANT CHANGE:
Ill be migrating to custom data tag usage sometime in the future. As of right now, both the old and new way works (new way is appending [tcj5] to the front of the appropriate line in data), but its processing on spaces, not all whitespace characters. Please adjust any old builds accordingly until this can be fully addressed.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CUSTOM DATA INFO:
To define blocks as part of the script, give them the default label "[ctrl]" in their name.
Inside a block with the tag, define the following;

number, ("lr", "ud", "fb", "pit", "yaw", "rol"), true/false

1.) The number represents the group number of the item and which the controller and controlled will respond to.
This is required for all blocks as per system.
2.) The string expression refers to the control direction this object should listen to. For reference, lr refers to left\right, ud to up\down, fb to forward\back, pit to mouse pitch, yaw to mouse yaw, rol to mouse roll.
To be specific,
pit and yaw will be mouse controls.
All other input options are controlled via keyboard.
3.) True/False indicates whether user input should do an opposite action instead of default behavior. Play around with the controls to find whichever is more comfortable. Default is false.

So an example of acceptable input would be
1 ud true = this will set this object to respond to group 1 controls in the up/down direction (jump/duck) and flip the input streams (up becomes down, and down becomes up).
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Arguments:
While not entirely necessary, if you have a cockpit marked off as the main cockpit, you can pass numerical values to the script which will change the main cockpits group control to the value that you passed. Ideal if you are working with many groups from one cockpit.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Current support;
+Pistons (Make sure you set velocity!)
+Rotors (Make sure you set velocity and braking torque!)
+Thrusters!
+Projectors - Also includes mouse detection for rotational inputs!
+Gravity Generators!
+Lights!

Thruster support has been added! While this can allow for VTOL like capabilities, its no where near as sophisticated as whips script which I highly recommend checking out!

I will be looking into wheel support in the future. So enjoy what the script currently has to offer! Oh yeah, and if you would like to see this script fully functional in dedicated servers, go upvote this feature request![support.keenswh.com]

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Personal Notes:
Now I know what you may be thinking, but no, this will not work immediately for bipedal robots or other sophisticated motions. However this project serves as a basis for future projects revolving around item groups and movements that exhibit such behavior. Consider this script as the feet dipping.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
TROUBLESHOOTING:
Double check your names, and settings. Make sure you recompile after any configuration changes. If you are still having issues, use the following test platform to help troubleshoot your issue. It is a fully working instance of a crane controlled with your normal movement which I presume most people are using this script for anyways.