Search results

Flip the situation around and ask, "Why is Thermal Expansion is locking out people from using BC/RC/Forestry power generation?" Because right now, if I want to use a Combustion Engine to power a Thermal Expansion machine, I can't. But I can use a Dynamo to power an Assembly Laser just fine. I...

Which is why I'd rather see a clean split, because right now we have two different target audiences. And frankly I'm tired of seeing the TE people rant on BC constantly.

Most people switched back when Conductive Pipes were exploding right and left. And I don't blame them. Pipes sucked. Now they don't, but the people still think they do.

The part of the power system people didn't like was the powerloss per pipe and exploding pipes. Both of which have since been removed, I didn't like them either.

Buildcraft Kinesis Pipes cannot explode anymore. No matter what you do to them. A Diamond Kinesis Pipe can store 14,336 MJ, fourteen times that of a TE Conduit. Admittedly, this is not really a supported use of Pipes. Plugs? They are dirt cheap. I also would rather see a clean split rather...

Yes, KingLemming himself implemented this change into Buildcraft. Unfortunately it had to be implemented in every mod that used the Power API as well. This was one of the reasons we needed a new API. I don't even know what that means, but my best guess tells me you've never seen a BC energy...

Reduced it by like 99% in fact. I don't know about you, but I call that a buff.

Which I repeat the SafeTimeTrackers are only there because it was practically forced on us to support tickless operation in order to keep the peace. The old API didn't support tickless operation either, but it was kind of possible via a bastardization of the PowerFramework API. A modification...

The only mechanics "change" I made was removing the 20% powerloss per pipe. Everything else was minor tweaks to existing mechanics.

And it would have made the rewrite completely pointless, since the primary cause of all the bugs was inconsistent PowerProvider and IPowerReceptor implementations. Also, I have the IRC logs, you never actually asked that. Complained about miniscule cost validation checks and JVM Hotspot...

The only reason it has the SafeTimeTrackers is because Aidan and you insisted that it had to support tickless operation. Remove that requirement and you don't need the time trackers. They were not part of the original design. Not really, you grab the tile's power handler, give it power, and...

The Facts, in chronological order: Severe designs flaws are noticed in the old API that result in a constant slew of bugs. API is refactored and cleaned up, using the old API as the foundation so that users of the new API wouldn't be required to rewrite their machines completely. Legacy...

There is bug that limits it to being breed on the 27th and 2nd only. It's been fixed in the source but... yeah

Faster pump == more lag

I don't see how that could possible be related to Buildcraft.

Diamond pipes can do weighted random distributions. Normal Pipes distribute items fairly evenly at junctions. These properties can be used to distribute items.

Emerald Pipes in blocking mode will output items is a specific ratio. Diamond Pipes will output in a semi-random distribution weighted on how many times a specific item appears in the list.

Uh...no somehow it got re-enabled accidentally, some Git derp somewhere probably. Don't expect to see the Builder until after the 1.7 update, its on hold atm pending migration to the new block ID system in 1.7.

"can't be picked up" typically means the client and server are running different datasets. Check your configs and installed mods.

ISEs produce 8 MJ/t, always have, probably always will.