V2.6.1 - Hotfix

~ Fixed a compilation issue due to Keen changing Lists to point to MemorySafeLists (See https://support.keenswh.com/spaceengineers/pc/topic/47788-list-resolving-to-memorysafelist-when-no-alternative-is-found )

V 2.6 - Light and Console Implementation

+ Added support for lights. They function by detecting if there is any movement alongside their respective axis. IsFlipped controls whether the block starts lit (true) or unlit (false).
+ Added a more informative description in the pb's echo out. It should help during setup by making sure your components are labeled and configured.



~~~~~~~~~~~~~~~~

Looking ahead:
Its been a while since the last update, but man has this thing got a lot of support! I appreciate that you guys are enjoying the script so far and I'm happy to tell you that there will be some major feature implementations coming down the line once I bug fix wheels for good, so stay tuned! (And please, reminder that if you are enjoying the script and wish to see full support in multiplayer, go upvote the support site request that's linked on the main page here in the workshop.)

V 2.5.5 - Hotfix

Fixed an egregious logic error which prevented more than one block group from being controlled at a time. Wasn't resetting one of my linked lists.

You will also notice there is code in place for wheels. Please understand that this is a WIP and not ready for public use. But if you still want to dick around with them, go right ahead.

I will be planning on doing some string parsing improvements and output information so users can understand whats being controlled better during use. It could help reduce debugging attempts and let players know if somethings amiss.

V2.5

Added the ability to now use mouse movements for all other supported block types. It follows the same custom data format as before, this time the new names used are "pit", "yaw", and "rol".

V2.4

Changes:
+Optimized the code to significantly reduce the performance hit when rebuilding lists should blocks be removed during use.=D

V2.3
I am really, REALLY, glad i took some time redesigning this.

Optimizations
+ Removed some lists and deleted some old outdated code/moved to junkyard which should lower memory footprint
+ Script will now work even if you grids are sustaining damage. Delete a block? No problem. Script will recompile lists upon broken block.

Additions:
+ If you are sitting in a cockpit marked as the main cockpit, you are granted access to argument controls which allow you change groupings without having to recompile! Ideal if you are playing alone and your grid has multiple things it can control. To use this feature, simply pass the number matching the group value you wish to control either through terminal or as an argument sitting on the toolbar.

V2.2

Like i said, with the new design I can add new block types MUCH faster. Code now supports gravity generators and projectors, with projectors getting the bonus of rotation controls from a users mouse! =D

V.2 - The thrustening.

Hey again my dudes! Appreciate you all for using the script. I got wonderful news! Thruster support is now available!
Thanks to a reorganization in my code, I can add new blocks and respective WASD actions in much faster times! I was able to code thruster support in mere 20 minutes!

That being said, if there are some other block you would like me to support, like doors or lights, let me know. Although ill probably add those controls sometime later.

Fixes:
+Rectified thrusters and rotors constantly being turned on/off creating annoying whooshing sounds.

Changes:
+Added thruster support.
~Begun work on tag usage. This uses both the new and old versions but expected stable behavior is to append "[tcj5]" at the front of items custom data.
~Reconfigured code which should allow me to add new block types faster.

This code is not 100% stable yet for dedicated server multiplayer due to code dependent on MoveIndicators. If you would like to have this script work flawlessly on dedicated servers, go support the feature request found here![support.keenswh.com]

TODO:
~Begin migration to new tag usage for use in larger scale projects.
~Look into developing controls for wheels.
~Reduce code footprint and clean up logic.

V.1

Notes covered in description