2.2.10 API re-packaged

Note for all modders relying on BuildCraft API – there has been a packaging issue between 2.2.8 and 2.2.10, where the API packaged in the releases was the 3.x API instead of the 2.x one. Since both APIs started to diverge and being incompatible, that means that including the “official” 2.2.x BuildCraft API in your mod would generate incompatibilities and crashes when installing BuildCraft along with it. I apologize for the mess here…

The BuildCraft 2.2.10 API has been re-packaged and should now include everything that is necessary. Let me know if there’s still any issue.

BTW – this API is now completely frozen. If you’re only including it in your mods, it will stay the exact same for the entire 2.2.x branch. Random API updates has been the source of a lot of frustrations, problems and incompatibilities lately, so I’m strengthening the policy. API changes are now completely forbidden from the Beta stage of a release onward.

Oh yeah – and merry Christmas to y’all!

14 thoughts on “2.2.10 API re-packaged”

Ok i want to know that WHENEVER I go into a diamond pipe in SMP I ALWAYS crash.. and the hotfixes from before i don’t know about.. im using 2.2.10..CAN you PLEASE tell me?

SpaceToad on December 25, 2011 at 10:42 am said:

I’m not able to reproduce any more diamond pipe diamond issue on the official SMP server (s15972928.onlinehome-server.info) – so I can’t tell. What I suggest is for you to connect there and try to reproduce. If the problem happens on this server, then I will be able to fix.
- kunkun on December 25, 2011 at 10:48 am said:
  
  so these are the things im using on my server tho.. just want to know if there are anything that is screwing it up then.. Plasmacraft..works fine and dandy..buildcraft 2.2.10…invasion mod..works fine…modloaderMP 1.0.1.. and mcforge 1.2.3 is there anything that causes it on servers? because everything works fine on SSP
  - kunkun on December 25, 2011 at 10:49 am said:
    
    it gives me a dirt screen and right after a black screen
    - kunkun on December 25, 2011 at 11:08 am said:
      
      OK im still crashing.. i found a random dudes house/cave..entered it.. SORRY and i crashed when i tried to enter a diamond pipe
    - SpaceToad on December 25, 2011 at 11:18 am said:
      
      You need to be a bit more specific man if you want me to be able to help here. So this is on the official server, right? By opening, you mean opening the interface, right?
      
      For the crash, can you follow the instruction given on http://www.minecraftforum.net/topic/184380-modding-tips-and-tricks/ ?
    - kunkun on December 25, 2011 at 11:31 am said:
      
      ok i fixed it.. just with buildcraft installed.. it still gave me the error.. i had to change it to a random other id that was of course below 255 i think.. the block id range
    - SpaceToad on December 25, 2011 at 11:43 am said:
      
      I still don’t understand any of this. Please open a thread on the forum, under the bug report section, and provide a trace and some more comprehensive data.
CovertJaguar on December 25, 2011 at 5:21 pm said:

Sounds like a net gui id conflict.

Minecraft became just unplayable since Forge 1.2.3 and the issue with Optifine.
I have no problem using MCPatcher instead, but for some reason, I get alot of GL Errors non stop, and it causes crazy lag.
I’m back to 2.2.7 and Forge 1.2.2.
Please try to fix that spacetoad.

SpaceToad on December 25, 2011 at 6:45 pm said:

You should be able to use Forge 1.2.2 with BuildCraft 2.2.10. I didn’t add any new dependencies.

The API now references and tries to import things from BuildCraftCore, which isn’t part of the API package.

SpaceToad on December 27, 2011 at 2:48 pm said:

Which class contains the incriminated reference?
SpaceToad on December 27, 2011 at 3:01 pm said:

The only reference I could find is FillerPattern. You can safely remove it from the API when you compile your sources, along with the FillerRegistry. To my knowledge, this is not used by anyone at the moment, so I may even remove it for 2.2.11.