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

Possible exploity behaviour of energy conduits #540

Closed
Belgabor opened this issue Mar 8, 2014 · 2 comments
Closed

Possible exploity behaviour of energy conduits #540

Belgabor opened this issue Mar 8, 2014 · 2 comments
Labels

Comments

@Belgabor
Copy link

Belgabor commented Mar 8, 2014

For a long time I though the energy limits on RF conduits works kinda like IC2 (not exploding, but limiting how much energy can be transported). Only recently I stumbled across a post by KingLemming in which he clarified that conduits within themselves can transfer basically unlimited energy, the limit applies to how much RF/t can be transfered in and out of the conduit per connection face.
Now this opens the door to exploits as you could basically run your transfer lines on cheap low tier conduits and only use high tier conduits to connect to machines/generators/storage. In TE there is no issue as different tier conduits do not connect to each-other. While I haven't read this, I strongly suspect this is intentional for exact that reason.
In Ender IO different tiers do connect to each-other. I like this feature and as long as I still had the misconception about how it works I designed my energy lines according to it (high tier backlines with low tier branches where not that much energy is needed).

I'm not sure this can be fixed (if it isn't even considered intended behavior) in a a performant way while keeping inter-tier connectivity, but I think it should at least be given a thought.

@CrazyPants CrazyPants added the bug label Mar 17, 2014
@CrazyPants
Copy link
Member

This is behaviour is exactly as implemented at the moment, so in that sense it is intended behaviour, but I agree that it is not how it should work. It has always been my intention to limit the transfer rate between conduits of different types, but I still haven't implemented this yet.
If I am entirely truthful, this is partially due due to the fact it seems most people make the same assumption as you and use them as they should be anyway. I have just quietly failed to correct people on this assumption when I have seen it ;)
I am not sure if I will make this change in 1.64 as I am planning on doing a bit or a revamp of the conduit internals for 1.7 anyway (I almost know what I am doing now..)

@CrazyPants CrazyPants added the Code Complete Wait for the next release... label Sep 8, 2014
@CrazyPants
Copy link
Member

There is now a config option (in the 2.1 beta) to disable connection between conduits of different tiers.

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

No branches or pull requests

2 participants