Energy Acceptor does not accept Rotarycraft power #1013

Closed
gwalther opened this Issue Mar 12, 2015 · 11 comments

Comments

Projects
None yet
6 participants
@gwalther

Rotarycraft has recently updated its API, and it appears AE will no longer accept Rotarycraft power directly.

@BoboSims

This comment has been minimized.

Show comment
Hide comment
@BoboSims

BoboSims Mar 12, 2015

Should that not be posted with Rotarycraft?

Should that not be posted with Rotarycraft?

@thatsIch

This comment has been minimized.

Show comment
Hide comment
@thatsIch

thatsIch Mar 12, 2015

Member

mh, again?

Member

thatsIch commented Mar 12, 2015

mh, again?

@JCHollett

This comment has been minimized.

Show comment
Hide comment
@JCHollett

JCHollett Mar 13, 2015

@BoboSims

The issue is not rotarycraft. API is used to help other mods interface each other. If AE2 changes their API, they would have to adhere the new API, same for Rotarycraft's API, AE2 would have to adhere to their API. It's like building a car to use gasoline then suddenly saying, it has to use hydrogen now. Then blaming the car for not being able to use the thing it was made to work with.

@BoboSims

The issue is not rotarycraft. API is used to help other mods interface each other. If AE2 changes their API, they would have to adhere the new API, same for Rotarycraft's API, AE2 would have to adhere to their API. It's like building a car to use gasoline then suddenly saying, it has to use hydrogen now. Then blaming the car for not being able to use the thing it was made to work with.

@BoboSims

This comment has been minimized.

Show comment
Hide comment
@BoboSims

BoboSims Mar 13, 2015

I understand the logic, @gixbit. But were I to invoke logic, logic clearly dictates that if you live in a world with only petrol-driven vehicles and no hydrogen-driven vehicles whatsoever, and you then suddenly stop providing petrol in favor of hydrogen, then that is not the fault of the automobile industry! You changed your business out of the blue; you made your product incompatible with the established market!

Analogously (sp?), if the RotaryCraft team made an almost ad-hoc change that caused the incompatibility, then that isn't the AE2 team's fault. Perhaps they could have allowed for a bit more time for others to adjust. Or maybe they could have made it backward compatible for now. At the very least, though, they could have announced beforehand what they were doing; communicated with the community about the consequences of their new model.

I mean: they release a new API; something others need to adhere to, need to work with. You can't expect everyone to be up-to-date at a moment's notice. They could have given warning.

I understand the logic, @gixbit. But were I to invoke logic, logic clearly dictates that if you live in a world with only petrol-driven vehicles and no hydrogen-driven vehicles whatsoever, and you then suddenly stop providing petrol in favor of hydrogen, then that is not the fault of the automobile industry! You changed your business out of the blue; you made your product incompatible with the established market!

Analogously (sp?), if the RotaryCraft team made an almost ad-hoc change that caused the incompatibility, then that isn't the AE2 team's fault. Perhaps they could have allowed for a bit more time for others to adjust. Or maybe they could have made it backward compatible for now. At the very least, though, they could have announced beforehand what they were doing; communicated with the community about the consequences of their new model.

I mean: they release a new API; something others need to adhere to, need to work with. You can't expect everyone to be up-to-date at a moment's notice. They could have given warning.

@thatsIch

This comment has been minimized.

Show comment
Hide comment
@thatsIch

thatsIch Mar 13, 2015

Member

Its fine being posted here,
just would hear a heads-up from Reika himself,
so we know what its up

Member

thatsIch commented Mar 13, 2015

Its fine being posted here,
just would hear a heads-up from Reika himself,
so we know what its up

@JCHollett

This comment has been minimized.

Show comment
Hide comment
@JCHollett

JCHollett Mar 13, 2015

@BoboSims

There is no reason to start a flame war. Mod devs can do what they want, there is no agreement between authors to conduct their updates in the interests of anyone. And even if there is, they do not have to honor anything. Thats how it works I would imagine.

@BoboSims

There is no reason to start a flame war. Mod devs can do what they want, there is no agreement between authors to conduct their updates in the interests of anyone. And even if there is, they do not have to honor anything. Thats how it works I would imagine.

@BoboSims

This comment has been minimized.

Show comment
Hide comment
@BoboSims

BoboSims Mar 14, 2015

@gixbit I'm not starting a flame war. I didn't call anyone any names, nor did I curse or bear anyone any ill will. I show no anger, and even didn't - and still don't - show any emotion at all. I'm just stating facts and my honest opinion. And I used logic to counter your own somewhat flawed analogy. That's all I did.

As you can see, @thatsIch at least agrees that he would have appreciated some note from Reika too. So, maybe I'm not even unreasonable.

I'll even throw in a similar example: recently, TeamCoFH changed something about their mods too, and as a result, their wrenches no longer work on certain blocks from other mods. I didn't blame those other mods, because the change was initiated by TeamCoFH. So that is where I went to report the incompatibility. Same kind of situation, same kind of logic. They gave me a reasonable and convincing explanation, so I'm satisfied. Even though the incompatibility has not been reversed.

You're right about one thing: they aren't required to communicate with anyone at all!
However, if you don't communicate, then there's no compatibility whatsoever, and not one mod would work together with any other mod. But if they want their API to be the standard - the method that others adhere to - then they indeed MUST communicate with others. Because cooperation always wins out over competition.

@gixbit I'm not starting a flame war. I didn't call anyone any names, nor did I curse or bear anyone any ill will. I show no anger, and even didn't - and still don't - show any emotion at all. I'm just stating facts and my honest opinion. And I used logic to counter your own somewhat flawed analogy. That's all I did.

As you can see, @thatsIch at least agrees that he would have appreciated some note from Reika too. So, maybe I'm not even unreasonable.

I'll even throw in a similar example: recently, TeamCoFH changed something about their mods too, and as a result, their wrenches no longer work on certain blocks from other mods. I didn't blame those other mods, because the change was initiated by TeamCoFH. So that is where I went to report the incompatibility. Same kind of situation, same kind of logic. They gave me a reasonable and convincing explanation, so I'm satisfied. Even though the incompatibility has not been reversed.

You're right about one thing: they aren't required to communicate with anyone at all!
However, if you don't communicate, then there's no compatibility whatsoever, and not one mod would work together with any other mod. But if they want their API to be the standard - the method that others adhere to - then they indeed MUST communicate with others. Because cooperation always wins out over competition.

@Cisien

This comment has been minimized.

Show comment
Hide comment
@Cisien

Cisien Mar 14, 2015

Contributor

What it boils down to is that the API changed. If we still want to support the mod, then the issue is on us to fix. Can we stop debating this now?

Contributor

Cisien commented Mar 14, 2015

What it boils down to is that the API changed. If we still want to support the mod, then the issue is on us to fix. Can we stop debating this now?

@thatsIch

This comment has been minimized.

Show comment
Hide comment
@thatsIch

thatsIch Mar 26, 2015

Member

Can somebody here test the build of #1103 ?

I have no clue how RtC works, so...

Member

thatsIch commented Mar 26, 2015

Can somebody here test the build of #1103 ?

I have no clue how RtC works, so...

@thatsIch thatsIch added this to the rv2 milestone Mar 26, 2015

@thatsIch thatsIch self-assigned this Mar 26, 2015

@ruifung

This comment has been minimized.

Show comment
Hide comment
@ruifung

ruifung Mar 27, 2015

Just hook up a creative industrial coil to test. it can only be found in creative inv. Ill test it later if it still needs to be.

ruifung commented Mar 27, 2015

Just hook up a creative industrial coil to test. it can only be found in creative inv. Ill test it later if it still needs to be.

@thatsIch

This comment has been minimized.

Show comment
Hide comment
@thatsIch

thatsIch Mar 28, 2015

Member

Seems to work

2015-03-28_07 48 17

Member

thatsIch commented Mar 28, 2015

Seems to work

2015-03-28_07 48 17

@thatsIch thatsIch closed this in 22b965e Mar 28, 2015

thatsIch added a commit that referenced this issue Mar 28, 2015

Merge pull request #1103 from thatsIch/b-1013-rotarycraft-power
Fixes #1013 Energy acceptor can receive RotaryCraft Power again
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment