Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Annoying Lockout #37

Open
Sqrlmonger opened this issue Feb 24, 2025 · 0 comments
Open

Annoying Lockout #37

Sqrlmonger opened this issue Feb 24, 2025 · 0 comments

Comments

@Sqrlmonger
Copy link

Describe the feature/addition!

When you configure a request the thing is very eager to be about the business of crafting as asked. Which in and of itself is not a problem. The problem is that once its off and cooking it doesn't allow you to modify the request settings.

Given that batch size is 2nd there have been many times where I set the thing to keep 100k+ of something in stock and it either gets stuck flickering (small batch sizes cause this) such that its a pain to change the batch size or just locks me out for long periods (large batch size causes this).

This is all made worse by the toggle not really seeming to work properly which is a bug I assume on its own.

It would just be a huge help if the request settings could be edited even while its running a batch. I don't care if behind the scenes you are just holding onto them until the lock ends and applying them in the couple of ticks where the thing is unlocked or if you find a way to modify it on the fly.

An alternative solution would be to allow for changing the inter-batch request delay. As each batch kicking off in rapid succession is fine once a requester is set up, but I'd really like it to wait 5-10 seconds (configurable in the interface would be ideal) between batches while I am configuring it still.

IDK - there are a lot of ways to approach mitigating the issue and I'm not married to any specific solution.

Why would like to see this feature/addition?

It would massively streamline the configuration of ME Requesters. I was excited to use them at first but have limited their use quite a bit because of the pain of dealing with their issues. To be fair I concede the issues CAN be avoided by setting the stock amount to less than your current stock, configuring the batch size, and then raising the stock amount but this is the reverse order the fields appear in the interface to begin with.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant