Waiting for feedback for a long time now.
Cleanup -> Closed
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
May 11 2021
Apr 19 2019
Area triggers now trigger most logic blocks. They do not work with NOT and can only toggle T-Flip-flops into a high state. I'm not sure if this is an intended behavior or if they should only function with buttons and activators. I know personally I had this break some of my circuits as the area triggers started to toggle blocks they were never intended to.
Jan 22 2019
Jun 28 2018
-QA Testing-
Jun 26 2018
Jun 6 2018
Mar 18 2018
I dont know if that is a separate Issue or belonging to this Issue, but if a Gravity Unit is toggled by a Trigger Area Controller, it will toggle Gravity for EVERYONE on the Ship/Station and not just the Person who went through the Area Controller (ofcourse Multiplayer). I will make a separate Bug Report for it just in case.
Mar 15 2018
The actual issue is that only activation modules trigger gravity modules.
If you set up a trigger area controller the activation module that you send its output to can trigger a gravity module with no issue.
Mar 13 2018
Dec 8 2017
Nov 13 2017
-QA Testing-
Nov 6 2017
issue due to slaved weapon systems being excluded from power consumption
Oct 14 2017
Jul 20 2017
Activation no longer appears to interact with rail docker at all.
Jul 19 2017
Now any other logic block connections with wireless module are invisible in both directions, not only wireless-wireless connections. Is it supposed to be like that?
Jul 7 2017
Jun 29 2017
-QA Testing-
-QA Testing-
-QA Testing-
Jun 28 2017
Jun 27 2017
Jun 7 2017
Hm thanks, adding a blocking task to this one then.
Jun 6 2017
May 23 2017
May 13 2017
Behavior has changed, the NOT gate no longer changes rail orientation on any state change.
Apr 28 2017
Apr 24 2017
Apr 5 2017
Apr 3 2017
Apr 1 2017
Mar 29 2017
Mar 27 2017
Mar 24 2017
Mar 23 2017
Issue returned.