for a girl to cultivate within herself invincible summer days.
Bit of a long one, I'm afraid. Parts probably belong somewhere else but you'll live. This all concerns fully auto mode as that's the only part of the game I'm interested in.
How does one find resources in fully autonomous mode? Short of some sort of 'blind hen' logic the size of quarter of a planet.
What's the reason for enormous container floating just out of reach of ground contraptions and smack bellow mothership? We need to include logic for landing procedure to avoid it, anything that wants to deposit needs thrusters anyway plus entrance is from above. Not to mention avoiding its thrusters. So another fairly elaborate logic to 'park' and then get out unscathed. Would it be really so bad if a) it was 10x smaller and on the ground or b) reasonable proximity to mothership would empty resource container?
Ability to name parts. All the code is already there; used in add/change tag. Just needs a click event on default part name in its properties window. Somewhere somebody mentioned advanced programming of drone(s). Words like Python and LUA were heard. How exactly do you envision doing that w/o parts having unique IDs? I mean, they already have unique IDs, they have to. A label would be next logical step, no?
Speaking of properties window, so much space, so little content 😋 Orange buttons could be half the size, that makes room for 3rd button that would display green part when needed and applicable and make room for many things that one wished were there but are not.
For instance, Inverse checkbox for logic gates. NOT gate is just inverted IF gate, AND gate with both inputs inverted makes a NAND gate, etc.
Any reason impulses, buffers and delays are limited to 10 seconds? Surely it's not for fear of slider becoming to sensitive as there exists long impulse giver.
I'm an amateur at logic circuits on the best of my days but isn't a counter a basic block of said devices? Sure, we can build one, one switch and one gate for every number.
So one would think is a simple splitter; one output, two outputs. Preferably more outputs. Implementing 4. and adding blue portion I'd say 6 would easily fit.
Debug. I mean do I even need to explain this? For starters simple log file would go a long way. Granted 3. needs to be implemented first or it makes no sense. Going on a limb, clock is 60 Hz, hopefully not tied to framerate. Add simple onStateChange event, err it's already there just needs another listener, and we're looking at 100ish short lines per second? Which is peanuts. Roasted but not salted.
Before going full on programming interface maybe a part that works akin to Factory in that it takes say 4 inputs, can accommodate dozen or so logic parts and has 2 outputs. In editor one would simply tie all logic to it and define inputs/outputs but when drone is launched all that is 'hidden' and only chip is visible. Disabled it in competitive as I believe Factory is if you wish. There could also be a limit on how many one core can handle, or maybe soft cap based on energy.
There's a whole section almost like this on mechanical side but maybe next time.