64-bit_dragon
-
Posts
16 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by 64-bit_dragon
-
-
No problem! I thought it may have had something to do with the other things but wasn't sure.
-
1
-
-
I had a "destroy bomber cave" mission but it triggered the complete signal after 4 of 5. Possibly two hives exactly underneath each other but then they should've been destroyed at the same time @4:05 / 4:06 in
-
1
-
-
I think I missed it then, I just tested it in 0.6.1 and it is indeed fixed. Also if they destroy each other
-
1
-
-
Yeah because placing two bombs next to each other only makes the explosion of the first which is a lot less destructive. You need multiple bombs to blow up a single hive right now but you can't have them within five blocks of each other or so.
-
It would be good if the bombs would stack, as it is now you can only use a single bomb in a region. The bombs now blow each other up without triggering the other explosion, which isn't realistic and isn't something you want if you make a bombing drone.
-
pssst... The edit should be 0.3.2 by now.
-
1
-
-
ok thank you then it's not a bug
-
1
-
-
even if objects aren't clipping or have long wires. I had this especially with drones using decouplers.
as shown @6:10 in this video:
-
1
-
-
I had this as well I wondered if there was something there, but currently just a mystery...
-
I meant that the impulse giver automatically starts, which you may not want for a long sequence. From what I understand from your reply you mean a delay gate, which is also a good logic gate to have, but not the thing I meant. I hope you understand what I mean. Maybe an example will make it more clear: Wait 1.1 seconds Active time 2.3 seconds delay 0.2 seconds. So at the beginning of the level, it will wait 1.1 seconds after that it will continuously go active for 2.3 seconds and delay for 0.2 seconds (like it is now). This was what I meant with the second logic gate:
The BUFFER Gate is an Automation Building that outputs Active when its input is Active, and momentarily continues to output Active when its input enters Standby. It is connected to other buildings via Automation Wire.
The amount of time the BUFFER Gate remains Active can be adjusted by the player, and can range from 0.1 - 200 seconds. When the input becomes Active again, the timer resets to the designated amount, and does not add to the current remaining time (if any). This Was copied from: https://oxygennotincluded.gamepedia.com/BUFFER_Gate they have a lot of good logic gates as well.
-
2
-
-
I don't think it's the correct thing to do though. Maybe later on, but in the beginning, I will just keep it to text.
-
On 11/14/2017 at 1:41 PM, OsoMoore said:
One possible approach to logic programming is to have a separate "logic connection mode". Instead of showing structural connections, logic mode shows signal input and output connections between parts. Then you can create and manipulate signals via mouse drags and clicks, instead of assigning dozens of keys.
Did you get that idea from Oxygen not included? They use it and it works, almost, flawlessly. So yes that's a really good idea.
-
1
-
-
13 hours ago, STM said:
I like the idea! Let's make a BFG!
My only concern is that the thing probably has to be a quite slow firing sort of weapon for balancing reasons.
So this thing would need some good aiming which i usually lack...
At this stage in development, I don't think they should focus on balancing, at the moment you can beat the game with just shotguns, even without actually trying.
-
It's a good idea, although you can, kind of, do that already. I know it's a shameless ad, but I showed it in my latest video. The way I did is pretty hard to explain through text.
-
Sometimes you don't want to activate a signal right away or you want it to keep going even after the key has been released by the user. Which, to my knowledge, isn't possible at the moment.
For the first, I would suggest an optional input key for the current "impulse giver"
And for the second I would suggest a new logic gate.
-
3
-
Game changing my rocket inputs... randomly?
in Bugs
Posted
That's what I thought as well but from Ookami-sama's picture I don't think that was the case here otherwise half would've been a and half d but they said all were A apart from the single thruster.