Some Questions and Suggestions

[CShisan]

I have a few questions:

1. Why is the minimum item transfer time set to 20 ticks? Many other mods achieve 1-tick transfers. In fact, every redstone do can transfer items in 1 tick as long as a redstone signal is input every tick. So why limit transfers to once per 20 ticks, forcing users who genuinely need this functionality to send an external redstone signal every tick?

2. Could you add a feature? When using input/output from/to each a, check each container a and only perform input/output for containers a that meet the condition, e.g., input/output to each a ifhas > 1 water (pseudocode). This requirement essentially involves looping through each a, which raises a question: why not design a for/while loop?

3. Could we add a feature? Implement an “input block” that receives a batch of items and simultaneously transfers them to a single machine. Simply put, I want to receive a batch of items from a crafting recipe issued by ae2 and send that batch to the same machine. Ideally, when there are 5 containers, it should split each item type in the batch into 5 separate transfers.

Finally, I absolutely love this mod. It simplifies tedious pipe connections, makes complex tasks straightforward, and improves layout aesthetics.

[TeamDman]

1. the original Steve's Factory Manager had the limitation and I kept it because I knew people would default to 1 tick where not necessary so I made people have to work a little for it

2. That grammar as you proposed would be ambiguous.
   There's proposals for something similar

• Add WHERE statements #155
• WHERE keyword for IO statements #158
  Loops involve variable binding and I haven't decided how best to do variables so it isn't a thing yet

3. Popular request, it's on the radar

• Bundles #472
• feat: exactly input/output #373
• transport multi items as unit for multi item recipe #281

[CShisan]

1. Have you considered relaxing the restrictions? I believe those who understand what they're doing will know when to use “1tick,” while those who don't won't cause serious consequences even if they use it.

2. Regarding the suggestion of input/output to each a if has > 1 water, I actually prefer having a loop statement. I'm just curious why a loop wasn't designed in the first place.

[TeamDman]

yeah I want to relax the restrictions, right now you can /sfm config edit server if you're op to change it without leaving the game but I'd like to make not require op at all.

it's tricky right now because I haven't made great progress on inspection tools for server operators to see a list of all managers and how laggy they are so I want to make sure that lag control for operators and to make sure that users have tools to right-size their programs

loops are blocked on deciding how variables should work, I want to do strong typing and haven't figured out a coherent design yet

[CShisan]

yeah I want to relax the restrictions, right now you can /sfm config edit server if you're op to change it without leaving the game but I'd like to make not require op at all.

it's tricky right now because I haven't made great progress on inspection tools for server operators to see a list of all managers and how laggy they are so I want to make sure that lag control for operators and to make sure that users have tools to right-size their programs

loops are blocked on deciding how variables should work, I want to do strong typing and haven't figured out a coherent design yet

Okay, I understand. Thank you for your reply.

[TeamDman]

Closing this as there is no actionable change at this time, further discussion is welcome at #158