Search results

Because BuildCraft pipes have traditionally acted on a pipe-by-pipe basis and not a network, like... pretty much every system. It adds a lot to its behaviour and makes them much more reliable in theory (the practice suffers from a lack of developers) - that makes any clever energy algorithm...

BuildCraft 6.4.7 is here :D Small bugfixes and a workaround for the multiple-fluids-in-one-pipe-causes-losses thing. Here.

We fix--- er, worked around the multiple fluids in one pipe issue in BC! (The one which caused so many people to lose their precious TCon metals). Sadly, BuildCraft comes without warranty and I don't have anything to pay you with for your unfortunate losses, except the bugfixed release right here!

They aren't lossy since a bugfix in 6.4.0 - however, that bugfix restored loops. It's one or the other apparently.

Lossy? What?

WAILA fixed it in 1.5.8/1.5.10, WAWLA however also breaks it. For a 100% definite fix, update BuildCraft to 6.4.6, WAILA to 1.5.10 and disable WAWLA until DarkHax releases an update (he said it will be this weekend). Closed.

The renderer, the resource pack format, the icon registration process, and sometimes even the models...

No. The texture format changed far too much. Just wait for 7.0 Stable.

A different developer was handling the textures. While Cyanide was doing the art, I was doing code. Also, the textures bring some utility functions - BuildCraft machines now have LED state indicators.

You didn't read the entire post. We CANNOT use original Mojang textures and use BuildCraft textures outside Minecraft - and we are considering moving further than just Minecraft with BuildCraft. Doing so would be a violation of the EULA. We want the textures available freely to use for all...

The new engines are made to fit with themselves, not Unity. Check it! Also, it's not just engines... Auto Workbench, Filtered Buffer, etc. I am generally a fan of pastel coloring. Also, I don't think an engine should have the exact properties of the material it's made out of - it's poor for...

BuildCraft 6.4.6! Fixed builder lag! \o/!!!

The behaviour changed in 6.4.0, but YouTube videos don't update as fast as we do.

Bad idea.

Both are not my work.

BuildCraft 7.0.0 Beta is out! Modularization, new textures, ???

Did BuildCraft 6.4.5 fix it?

If it persists, fire up VisualVM, double-click on your Minecraft instance (launchwrapper something), pick Sampler, click CPU, let it run for a few minutes, create a thread dump and save it and send it to me.

Try BuildCraft 6.4.5. We attempted a fix but we got no feedback for it so we had to test it on users live. I still have no idea why this happens. We need someone to provide a VisualVM sampling as we cannot reproduce it, period.

All MJ and RF are is just passing numbers between blocks. It's up to mods what they do with it. We decided to move to RF to let mod packs make the decisions, not us. They're generally better at ensuring balance between fifty different mods than we could ever be.