Due to lots of issues on the previous world (griefing, dupe bug exploitation, seed errors) the BuildCraft server had to be re-initialized. You can access it as usual from:
s15972928.onlinehome-server.info
Note that the old world is still accessible. I plan on keeping it live as long as a reasonable amount of people are using it. You can access it from:
s15972928.onlinehome-server.info:25566
Here comes a minor BuildCraft release, 2.2.11. You shouldn’t have to upgrade except if you are having troubles with server, in particular for migration between your 1.8.1 worlds and your 1.0.0 ones, where a major issue has been fixed. Here’s the changelog:
#25 items can’t be thrown out of obsidian pipes
Items can be thrown out of obsidian pipes again.
#114 bucket “eaten” by stone engine
Stone engine do not remove the bucket anymore.
#116 temporary fix for the refinery
Fuel can’t enter back in the refinery anymore.
#117 can’t import SMP world from 2.2.5
World created with BC before 2.2.6 can now be properly loaded in BuildCraft again
#118 issues with auto-workbench refresh
Fixed a dupe bug (again) in SMP auto-workbench
#119 consider move FillerPattern and FillerRegistry out of the API
Temporary moved FillerPattern and FillerRegistry out of the API since they rely on core. AFAIK, nobody is using these at the moment, but let me know if that causes a problem.
#121 fix potential pipe exception in SMP
Fixed various exceptions in SMP when loading worlds with invalid pipe contents.
The BuildCraft server (s15972928.onlinehome-server.info) is to be updated soon. Enjoy!
Moving further in BuildCraft 3.x Alpha! Here comes a preview of the next feature set, to be released in a few weeks with a version tagged 3.1.0:
Enjoy!
BuildCraft 2.2.11 is on the way, including fixes for three annoying bugs:
[1] loading SMP worlds may not load pipes properly, e.g. port from 2.2.5 to > 2.2.5 is know to remove all the pipes
[2] a remaining SMP dupe bug with auto-crafting tables
[3] fuel can get in the input slot of refineries and be stuck there
All three of these issue, plus a couple of minor ones (http://buildcraft.trac.cvsdude.com/buildcraft/query?status=closed&group=resolution&milestone=BuildCraft+2.2.11) are fixed in the development version. BuildCraft 2.x is really converging now, and I would really like to put this on the side and concentrate entirely on the 3.x branch. For that, I’m now looking for all potential blocking issues still remaining there:
- crashes
- problems that prevent reasonable game-play
I need BuildCraft community help for that. If you know of any problem in the above category, now is the best time ever to make bug report. See http://www.mod-buildcraft.com/documentation/faq/#bug_report to get ideas on how to efficient there. Thanks to you, 2.2.11 might be the final release on the branch!
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!
Well, it was short. Forge 1.2.3 is out, and uncovers one BuildCraft severe bug that needs to be urgently fixed:
#113 pipe / engine drop issues
Pipe are properly dropped again, engine do not crash anymore.
BuildCraft 2.2.9 + Forge 1.2.2 works great AFAIK – so you only need to upgrade if you’re running on a server that uses Forge 1.2.3 (which is going to be the case for the BuildCraft official server anytime soon).
Ok, so the previous server seemed to be very laggy, crashing all the time, so I went ahead and upgraded it. Since I still didn’t take over all the DNS functionalities,I still have a stupid address, but that should work much better. It is now accessible from:
s15972928.onlinehome-server.info
Enjoy!
*EDIT* definitely works way better. I’ve increased the number of slots to 40, will assess if it can go beyond that in a few days once there’s some more BC contents running on it. I’ve also opened a forum for the server offline discussions on http://www.mod-buildcraft.com/forums/forum/servers/official-buildcraft-server/.
Hi all! To celebrate BuildCraft 2.2.9 and a couple of stability fixes there, it is my great pleasure to officially launch a legit BuildCraft server! You can access to it from:
s394594430.onlinehome.fr
s15972928.onlinehome-server.info
Yeah, I know, the domain name looks bad, but oh well… Trying to see how I can improve this. It’s currently a BuildCraft 2.2.9 server with 20 open slots. As of today, its access is free. I’m intending to use it as a validation server, verifying that SMP works great and investigating potential crashes. Come and have a try!
Oh – yeah, and BuildCraft 2.2.9 is out. Fixes three major issues:
#101 fix quarry digging
The Quarry now digs grass as it used to. This fixes also similar problems with the filler.
#102 further fixes in diamond pipes SMP
The diamond pipe has been further improved under SMP.
#110 repair duplicates items in autocrafting table
Items repaired are not duplicated anymore in the auto crafting table.
Enjoy!
Ok, so there’s three known problems that are reported with BC 2.2.8, just that you know:
[1] There can be black screens with a couple of mods integrating the API, such as Railcraft. This is really my bad, I’ve updated the API without thinking of the potential incompatiblities here. The workaround is to install 2.2.7 instead from http://www.mod-buildcraft.com/download/previous-releases/.
[2] The quarry doesn’t mine grass. This is a minor issue, but if it’s getting into your nerves, installing 2.2.7 works too.
[3] Grass doesn’t drop seeds. This is a Forge issue, I want to make some verification before releasing Forge 1.2.2 with the fix. Out soon!
* Edit * Go check out Forge 1.2.2 on http://sourceforge.net/projects/minecraftforge/files/1.2.2/
Yet another hotfix. Some pretty annoying issues for SMP on the 2.x stable branch have been fixed. Hopefully, this will be one of the last one there, so that I can fully concentrate on the 3.x one!
For 3.x, only minor fixes have been implemented. Most of them are for people developing mods relying on BuildCraft.
#65 broken pipe do not release contents
Items in traveling in the pipe are now correctly released when the pipe is broken.
#84 SMP pipes don’t disapear for other players
SMP pipes now properly disapear and reaper when other players are changing them. In particular, even if there was an other pipe at the same location, they will correctly be displayed.
#87 obsidian pipe may suck items in infinite quantity
In SMP, obsidian pipe may extract infinite amount for a same item, this should now be fixed.
#88 two players may duplicate objects with a workbench
The dupe bug where two player could generate items out of a workbench is fixed.
#89 decrease the amount of oil
The medium size oil deposits generation has been slightly decreased.
#91 investigate diamond pipe issue
Diamond pipes don’t crash clients anymore in SMP.
#16 quarry should consider oil like other liquids
Quarry will ignore oil as well as other blocks such as flower or grass.
#92 fix block size magic constants
Magic constants for block list size have been fixed in the code.
#73 improve liquid API
The liquid API is now based on stacks, taking into account meta, and can be used with any kind of container.
#90 use dynamic / configurable blocks ids for laser and assembly table
The assembly table and laser block ids can now be configured.
#66 gates transfer wire signals without wires
Gates do not conduct signal anymore if they don’t have wire.
#74 laser effects remain after laser block is moved
“Phantom” laser still in effect after block removal is fixed.
#85 add “from” in power reception
In the API, it is now possible to know what directions the power is coming from.
