Hizenhawer

Factories are super OP as the are. Aspactialy that you can keep all shared logic on your core. What I'd see more of a suggestion is to make factories use resources from the object they are connected to. Like you have to wait for x seconds for elements to produce, but then you have to fill all tanks and batteries. Right now it's super easy to make a swarming drone. My design with ^2 gain every 9 seconds. Game starts to lagg pretty quicly.

Right now if you want to overview logic of your drone you have to click element by element and memorize or write down logic connections between them. My suggestion: Add window that updates when you select a component. It would display all logic elements connected to this element. Not in a physical way but in logical. As of style I suggest, elements are dropdown buttons and under labels, they display their inputs and outputs. Like so: >Factory #1 (maybe custom names?) *click* \/Factory #1 Inputs Decuple: my_decuple Print: my_print Outputs Ready to print: when_ready From here there are many possibilities. For example, you could double-click tag to highlight or uses. Change the tag name in all elements at once and so on. With analogue signals, you could just display small expandable plots.

True, I only recently noticed them. xP

Please don't limit us like Besige did. Variables The amount of buttons on the keyboard is very limited. That limits component comunikation in drones. Single button clicks should only be reserved for player input, and components should comunicate with custom variables so that you're not limited in amount of different signals that you can use. Analog Signals Right now if you whant your drone to smothly approche something you need a lot of sensors. The closer you get the more sensors activates and the more engines activate to counter the momentum. With analog signals you only need one sensor and one engine. Thats how I would imagine it would be done: You activate "advanced control" setting and take, lets say distance sensor. First you diclare the variable that sensor uses. For example "distance_to_container". Than you choose "point zero", what I mean by that I'll explain in a sec. Let's take distnce 100 as your point zero. That's a distance that you would whant to keep your drone away from container. Than you choose what kind of function your signal should be. Let's take a slow growth of 0.01*x^2. That means for distance of 100 away from point zero you'd get a value of 100. For distacne of 1000, value of 10 000. You'd see a nice plot showing you the function. Now you take this value, hidden in you variable "distance_to_container" and send it to engines. But you engines now can take an analog signal. Let's say engine gives 100% of thrust when gets a value of 10 000 or above and 0% when 100 or below. In that way you could simply control your drone with way bigger precision and smoothnes than ever before. Well I can understand that analog signals is a lot of work for not that big amount of users, but variables? Oh come on. They're a must-have! Thank you for your time, cheers.