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

Something wrong with ME Storage Bus when build A sub network #8018

Closed
FwFeiVan opened this issue Jul 8, 2024 · 2 comments · Fixed by #8095
Closed

Something wrong with ME Storage Bus when build A sub network #8018

FwFeiVan opened this issue Jul 8, 2024 · 2 comments · Fixed by #8095
Labels
bug Self explanatory?

Comments

@FwFeiVan
Copy link

FwFeiVan commented Jul 8, 2024

Describe the bug

If I use multiple ME storage bus to access the main network's item, there's only one ME storage bus working. Other ME storage buses will be ignored.

How to reproduce the bug

First build A main network and put in several different items;
Then place ME interface on main network, build A sub network like this and place multiple ME storage buses;
Finally set the mode to "extract only" and add different item filterings.
And you can see only one of them can be viewed in sub network's terminal.
For example, I build the sub network like this but I can only see brown concrete in sub network's terminal.
But I have both brown and white concrete in main network
Uploading f37dee26462cfa2133940d9e044f3703.png…
Uploading 1bbeed370b7a3466c3f3dbe5186ad203.png…
Uploading 5976905438d5aabf5ae8bc0323c2785d.png…
Uploading 719747ec9fe3cecdf96daf557c3a194b.png…
Uploading 516907178360091af9f474ba3a1821d1.png…

Expected behavior

like the sub network I build above, I expect to see white concrete and brown concrete in terminal.
all ME storage buses should work. And if whitelist and blacklist both exists, the bus's priority determines.

Additional details

only main network can identify multiple storage buses that the IO mode is extract only. Sub network cannot identify multiple buses even if they are accessing different networks. In fact I'm not sure it's a bug or a mechanism. If it's a bug pleeeeeeeease fix it soon, and if it's a mechanism, a larger ME storage bus is necessary, espacially for Gregtech.
Uploading a837cc54feb479a25bbee4587263d207.png…

Which minecraft version are you using?

1.20

On which mod loaders does it happen?

Forge

Crash log

No crash report need

@FwFeiVan FwFeiVan added the bug Self explanatory? label Jul 8, 2024
@FwFeiVan
Copy link
Author

FwFeiVan commented Jul 8, 2024

f37dee26462cfa2133940d9e044f3703
1bbeed370b7a3466c3f3dbe5186ad203
5976905438d5aabf5ae8bc0323c2785d
719747ec9fe3cecdf96daf557c3a194b
516907178360091af9f474ba3a1821d1

a837cc54feb479a25bbee4587263d207
oops there's something wrong with picture and here are the supplement.

@shartte
Copy link
Member

shartte commented Aug 2, 2024

So, this is how AE2 was originally designed with the goal of preventing over-reporting of the main networks storage (if you didn't have mutually exclusive filters).

We're changing that behavior.

If you now use multiple storage buses without filtering, it will over-report the storage, but that is the same behavior as with chests.

shartte added a commit that referenced this issue Aug 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Self explanatory?
Projects
None yet
2 participants