-
-
Notifications
You must be signed in to change notification settings - Fork 180
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
Refined Storage Auto-Processing cross-dimensionally seems to tweak out in 1.18.2 (at least for me) #3746
Comments
Are you sure that's the only constantan ingot pattern in your system? (check by removing it and seeing if the recipe is still available) Does it happen even if everything is in the overworld? Does it happen in a separate creative mode world? |
I don't get why the crafters suddenly decided to start acting up, since they were working properly last I played. Alongside the auto-processing issue, The storage also sometimes just completely ignore certain inventories I've put down, even with an external storage cable working next to it. It only starts registering once I break the external storage/inventory/controller itself. But it still randomly stops being recognized by the system, even though the external storage cable itself is. (i dont even care anymore i just want my cross-dimensional crafting/processing back😭) |
Does this also happen with processing between the overworld and the nether? My immediate thought is that maybe compact machines don't respect chunkloading |
Yep. says "Machine Not Found" in the Nether too. I can confirm both of them respect chunkloading btw |
UPDATE!!! Seems like any cross-dimensional shenanigans just completely tweak out the system in general. |
My theory is that the problem is less about cross-dimensional crafting/auto-processing, and more about the "cross-dimensional" part itself. idek anymore man im tired |
Describe the bug
I was playing Mechanical Mastery (made by the goated Ammonium) on 1.18.2, and the auto-processing seems to be messed up.
It was fine a few weeks ago (when I suddenly stopped playing for a while), but when I got back into the world yesterday, any and all auto processing requests stopped working, and kept saying that "No Machine Was Found.", Even though there is very obviously a machine.
This was the case for any machine, whether it be modded or vanilla.
Auto-crafting with the normal/ExtraStroage crafters seems to be working fine.
A Video Example.
Mechanical.Mastery._.A.1.18.modpack.by.Ammonium._.2025-01-06.21-27-26.mp4
Not sure if this is the appropriate "format"/"platform" to report a bug like this, especially when I'm playing on a modpack that has no correlation with RS itself. But this issue has been bugging me so goddamn much because of the amount of effort I've put into the world, and having it all go down because of a silly bug like this is soul-crushing.
Also, Yes, All chunks in the video example are are force-loaded, and everything is connected properly. I have tried destroying the crafters (this was happening to every single crafter that I used for auto-processing through machines btw), the controllers, the cables, the machines, pretty much every thing I could think of.
Unsure if this is a bug on RS' part, or if it's some other mod causing this, But I dont think so because everything was working perfectly fine last time I played.
(Also, I apologize again if I seem "uneducated" on where/how to report bugs like this, or if I'm not supposed to report bugs in big modpacks to the creators of RS themselves. I have absolutely zero clue what I'm doing.)
How can we reproduce this bug or crash?
As I said, I have absolutely zero clue how/why this happened. It was working normally, until it one day randomly stopped doing that...
What Minecraft version is this happening on?
Minecraft 1.18.2
What Forge version is this happening on?
40.3.0
What Refined Storage version is this happening on?
1.10.6
Relevant log output
Wasn't sure what would be considered as "relevant" to the issue, so I tried pasting the whole thing but it was too long. If there's any specific part of the log that I should write out to help, tell me.
The text was updated successfully, but these errors were encountered: