DO NOT REPORT AN ISSUE IF YOU HAVEN'T TESTED THE ISSUE WITH THE LATEST VERSION IN CURSEFORGE

Replication Version:

Titanium Version:

https://streamable.com/5cssin

The replicators on the left won't run, but the ones on the right will. I queued up a batch of 256 phantom membranes in parallel, so I'd expect all 32 replicators to be running the job.

I queued up 2 jobs next and they're split between all the replicators. So it seems like there's a limit of 16 replicators per job?

Yes that is correct, I had the idea to put the limit to have different things always crafting but at the end of the day now that I think of it you will get the stuff at the same time. It just in case you request a big number of items of something so you dont use all of the Replicators.

Alright. Fair enough. Not sure how feasible this would be, or if it would be better, but what if jobs were allowed to fill all available replicators, but they'd auto balance as jobs are added?

Example, I queue up 1k logs. This starts on all 32 replicators.

Next I request 1k prismarine. As soon as a replicator finishes whatever single item it is currently doing, it starts doing prismarine instead. Up to half would switch in this way.

If I add a third job, the replicators would be split roughly in thirds to cover all jobs at the same time. Etc. So I could have a total of 32 separate tasks going and still get a little output from each on each cycle.

This gives you the full speed benefit of having many replicators, but also allows you to get multiple jobs running simultaneously.