Alow changing the level of logical blocks in schedule
Moderator: ickputzdirwech
Alow changing the level of logical blocks in schedule
The current system leads to situations like viewtopic.php?t=129566 where the only way to get the desired logic is to duplicate most of the behavior. This could be fixed by allowing you to change the level that and and or blocks are at, so you can do this
Last edited by its a me on Thu Jun 26, 2025 6:02 am, edited 1 time in total.
-
- Burner Inserter
- Posts: 12
- Joined: Mon Aug 19, 2024 9:56 pm
- Contact:
Re: Alow resizeing the area that logical blocks cover in schedule
Yes! You end up with contortions that are probably CPU eaters because we have no parenthesis.
-
- Fast Inserter
- Posts: 130
- Joined: Tue May 24, 2016 1:55 pm
- Contact:
Re: Alow resizeing the area that logical blocks cover in schedule
Agrea. It's the same with decider combinators.
Re: Alow changing the level of logical blocks in schedule
I achieve this goal by moving most of the Platform’s logic into a Combinator Contraption, next to the Platform Hub. I use a lot of different signals depending upon the Platform’s purpose, but generally the logic is “head to (Planet) when running low of (resource)-”. The resulting signal for “next destination Planet” is presented to the Hub using one of the Virtual Signals (the letter “P”), and then an Interrupt detects the Value (eg, Nauvis is “100”; Vulcanus is “200”; Gleba is “300”, etc…) to trigger the Platform’s schedule.