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

1.20.1 ENDER IO Energy cable not working #189

Open
MUHAKLorTheDorfTrottel4Github opened this issue Aug 24, 2023 · 6 comments
Open

1.20.1 ENDER IO Energy cable not working #189

MUHAKLorTheDorfTrottel4Github opened this issue Aug 24, 2023 · 6 comments

Comments

@MUHAKLorTheDorfTrottel4Github

1.20.1-forge-47.1.44
mcjtylib-1.20-8.0.2
rftoolsutility-1.20-6.0.1
rftoolsbase-1.20-5.0.1
xnet-1.20-6.0.
EnderIO-1.20.1-6.0.18-alpha

placing Dim cell connect to e.g BUILDER by ENDER-IO Energy conduit,
no power on Quarry

ok with xnet, ok when cell sie on side

i guess, this is an ENDER-IO issue, so this may be just an info

regards

@McJty
Copy link
Collaborator

McJty commented Aug 24, 2023

Show a screenshot of your setup

@MUHAKLorTheDorfTrottel4Github
Copy link
Author

please
enderio.pdf

@McJty
Copy link
Collaborator

McJty commented Aug 24, 2023

I really do hope EnderIO didn't make the mistake of extracting energy. That doesn't work. Forge Energy is a push system. Cables should NEVER extract energy from something. I would report it to them (with this remark) because it if they are extracting energy with their cables then that's a huge problem

@MUHAKLorTheDorfTrottel4Github
Copy link
Author

next setup, energizedpower-1.20.1-2.0.0 cables
same behavour
power.pdf

as workaround i use XNET, that works well.
But its a pain to setup a seperate XNET just for 2-3 machines
in this case i huse for ever machine a seperate dimcell

@McJty
Copy link
Collaborator

McJty commented Aug 24, 2023

Then they are doing the same thing wrong

@MUHAKLorTheDorfTrottel4Github
Copy link
Author

found a workaround for me
dimcell feeds batbox, cables (even enderio ) to machines
much easier than xnet

workaround

you may close this issue

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

No branches or pull requests

2 participants