Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Also, the current size of the logic parts is a little big IMO and doesn't allow for complex things. Perhaps it would be easier for all of us if there were "computing blocks" that allow for up to 3 operations on the same variables. It'd save space on drones and might be easier to handle script-wise, although I'm not a programmer myself.
I like the game a lot and 'wasted' >3,5h on it the very second I found it. My projects can't understand how glad I feel about it though. Keep it up!
Related to the last idea from the original poster: I would like to see a logic piece that would work kind of like an IF piece, but the output goes to main key even if it's attached to a logic splitter. Also, another one that instead accepts input from main key.
More original suggestions from me would be:
- Fuel/battery sensors that can be set to check how many units or the percentage of the maximum available from the drone. This is mostly because I have the sneaking suspicion that our fuel and battery satellites are going to go away, and I'd like to be able to have a drone automatically switch from shields and weapons to just shields if the power gets too low for both.
- Let us turn that distance sensor from a thin line, to a circular sector, much like the directional sensor's tolerance.
- While the directional sensor is fresh on the mind, how about being able to sense what direction the sensor is moving in? Sensor moves right, ball thing on it moves to the right side. Sensor moves up, ball thing moves to the top.
- Another possibly useful thing for the directional sensor to sense would be the direction of the drone brain. Could use it to make a detachable ball of joy and destruction that comes back to its master at the flip of a switch.
- Why am I trying to move a slider to the exact pixel I want instead of just typing numbers in?
- Do you think you could just... let me unassign the drone brain's self-destruct button? In fact, maybe let me be able to unassign all of those key variables. I might just decide that I'd like to have a part or two not work for a bit for testing purposes, and I'd rather not have to delete it or find a key that isn't assigned to something else.
Thank you for your work so far. I wish you financial success with it.
EDIT: Also, being able to set the initial state of a dynamic thruster or a switch would be nice.
Also for drones it would ease the use of logic parts, if it was handled that way. you wouldn't need complicated constructions with AND pieces as you could just assign 2 keys that had to be pressed at the same time to a group.