aidancbrady

Hi! unpairedbracket, my co-dev, has just created a new branch specifically for 1.5. The bugs that have been mentioned on the forums here have all been fixed for 1.6, but now I have the means to do the same for the 1.5 bugs. I'll get a new 1.5 build out as soon as I can!

I hope you all have grown to love Mekanism's universal energy system, the ease of converting energy between systems with my Universal Cable and machine/generator power framework. I have throughly enjoyed integrating BuildCraft, and due to Krapht and many others' hard work, this implementation was rather easy. BuildCraft has seemed to be following along the lines of a proper open-source project, accepting PRs quickly and building upon what SpaceToad's idea was. I have been excited about 1.6 to see what all BuildCraft has to offer for it's supposedly revamped energy system by CovertJaguar. Looking on GitHub, there are some wonderful improvements - PowerProviders can now be side-based, allowing for easier, more realistic MJ-based mechanisms, and receiveEnergy() can now return rejected energy in order to prevent power loss. One minor catch, however. This update also finalizes the "PowerProvider" class, and removes "IPowerProvider" which previously was used for managing a complete BuildCraft power framework. This means there will be absolutely no flexibility when working with the system, and all power interactions will have to act exactly how CovertJaguar intends for them to work. CJ has always been a good friend of mine, he's open to suggestions and has helped me many times in the past. I wouldn't have sent two donations of $15 to him otherwise. I don't appreciate his strict closed-source development, but he still accepts input from the community. This change to the BuildCraft power system, however, does the mod no justice that I can see. Not only is he cutting off many possibilities for mods that could potentially integrate with BuildCraft's API, but he is also screwing over developers that already use BuildCraft significantly in their own mods. Mekanism uses custom PowerProviders for managing it's machines, generators, and Universal Cables, without these systems my support for the mod would literally fall apart. Not to mention my great friend King_Lemming's Thermal Expansion, which is entirely built upon the core of BuildCraft's power framework, who will most likely have to completely remodel the way his mod works. Why would he do such a thing and make it immensely difficult for us developers to work with the "open-source" BuildCraft API? There are several reasons that I can see. CovertJaguar intends for BuildCraft-integrated mods to serve primarily as addons. This was the case with IC2 for quite some time until Alblaka smartly loosened on his iron fist on his mod. CovertJaguar feels threatened by Thermal Expansion, and he does this major refactor knowing KL will be unable to integrate. CovertJaguar intends for BuildCraft to serve as a power network primarily working with his Railcraft and Sengir's Forestry, and he doesn't want to deal with the possible competition of other BC-based mods. These explanations are what immediately came to mind, and there are several others that I will not list. There's a chance that he actually has another plan in mind for a more flexible API, but this response over IRC when referencing the API kind of threw this aside: <Calclavia: lol, not very flexible> <CovertJaguar: its not supposed to be> What? APIs are not supposed to be flexible? Let's let him explain: <Calclavia: An API is not supposed to be flexible lol?> <CovertJaguar: and API is ment to provide an interface into a propriatary system, so that you can interact with that system on its terms> Ok, so he's basically saying that you can only integrate with BuildCraft if the integration meets his standards. In other words you cannot do complete integration unless you are CJ himself. Uh... Because of these ridiculous actions and statements I am withdrawing complete BuildCraft support from Mekanism for the next major update. No longer will my any of my content interact in any way with the BuildCraft API. There is some good news, however. King_Lemming is going to be creating his own, unique version of the BuildCraft power framework, and I have plans to add integration with this the day it is released. That is all. -*signature stolen by Signature Gnomes*

Yes, this is a little Mekanism easter egg, off by default in config. See if you can pick out MachineMuse's, mine, and Wylker's coworker's voice on the different clips Hehe

Are you using eclipse? If so it should give you the list of parameters along with their use. UniversalElectricity.register() is just used to initiate the API's hooks -- pretty much useless if called from a different mod.

I am an nigerian Prince, I am in a need to transfer 1 , 000, 000 ,000 to a bank. Pleas respond with your full bank information and social security , and you will get 25% of the transaction. Please also include phone cellular, also name. Have a good day.

Hi, I'm the dev of the Mekanism mod which features the Metallurgic Infuser. Good news! There are two ways around this. First would be to simply put redstone inside of the Infuser's electricity slot. Second would be to craft one of my Heat Generators, which would be a great way to originally generate electricity, due to it's simplicity and efficiency.

(Hopefully) fixed in next version

This is all on me, as mentioned on another post. Fixed in Mekanism 5.0.2

As the mod's developer, can confirm this is fixed in the now-released 5.0.2 update which should be put in the pack in the next few days.