-
Notifications
You must be signed in to change notification settings - Fork 316
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
Improving the Return Button for Crafting Input Bus/Buffer #18397
Comments
Continuation: Additional Feature for Cancelled Craft Returns I had another idea: what if we also implement an option to automatically return items to the ME system after cancelling a craft? For example, let's say you place an order for 100k steel ingots. Later, you place another order for 100k steel. Important note: the two crafts are not merged - they are processed as separate jobs. Now, in the buffer, you end up with 200k iron ready for crafting. If you cancel the first craft (let's assume the first one processed 1,000 steel so far), the system should return the remaining 99k iron to the ME network. The second craft would then continue using the iron left in the buffer. Why Keep This Option? If cancelling a craft isn't possible in some setups, this feature becomes even more valuable. It ensures the materials in the buffer aren’t wasted and can be properly returned to the main ME system for other uses. Combining Features
Whether you use a main network or subnets, these changes would bring much-needed flexibility and clarity to handling crafting cancellations and resource returns. |
Craft Priorities – Who Goes First? Alright, let's make it easier to manage crafting queues by adding priorities to the buffers. Each template (or item) already takes up its own slot, right? So, how about letting players set what should get crafted first and what can wait a bit? How it could work:
Why This Makes Sense Now, if you could set the gears to high priority, they’d jump to the front of the line, get crafted right away, and you’d be back to building your machines in no time. Meanwhile, the steel can just keep cranking in the background. This would be a lifesaver for players who juggle small, quick crafts with massive resource dumps. You could keep everything running smoothly without stressing over which craft is hogging the system. |
Your GTNH Discord Username
LeoGuys
Your Pack Version
2.7.0
Your Proposal
Let's make the "Return all internally stored items back to AE" button smarter and more flexible. Instead of returning everything at once, give players more control over what they want to send back - and how much of it. This change would be a lifesaver in situations where you need to cancel or adjust crafting tasks without losing track of important materials.
Your Goal
The goal is to improve usability for the "Crafting Input Bus (ME)" and "Crafting Input Buffer (ME)" interfaces. Right now, the "Return all" button is great, but it's all-or-nothing. If you're running multiple crafting tasks and decide to cancel just one - or realize you-re working with more materials than you need - you're forced to return everything, even stuff you’d prefer to keep. That's frustrating and inefficient.
Why This Matters
This small tweak would make managing complex crafting tasks much less stressful. It's especially useful for high-volume crafters, where mistakes or changes in plans are common. The current system works fine, but this improvement would make it great.
Your Vision
Here's how we can make this process better:
Shift + Click for Item Selection
Add a feature where holding Shift and left-clicking the "Return all" button opens a menu. In this menu, players can pick specific items they want to send back to AE.
Add Quantity Options
Inside the menu, allow players to specify how much of an item to return. For example, if you’re crafting a million steel and realize that’s too much, you can input the amount you want to keep (e.g., 10k). After confirming, the system sends the excess back to AE and leaves the rest in the buffer.
Final Checklist
The text was updated successfully, but these errors were encountered: