Search results

There's not really a good way to handle this I'm afraid, short of adding transport which also has permissions. Which, ehh, maybe.

No limit and no loss. It's a unified point in spacetime. Stuff goes in, stuff comes out.

To be fair, there are reports that TE3 conduits are doing this sometimes too. It has something to do with a mod which is bypassing the normal chunk load/unload procedures. That may be the case here.

As long as Minecraft is single-threaded, the answer to this is always yes. Every point counts. Also, that benchmark *definitely* depends on the tile entities.

Problem with this is that it's sort of going "Hey let's compromise! Well...actually YOU compromise. Well maybe not compromise, you do this." It is beyond trivial from both a code and computational resource point of view to support RF. The same can't be said of MJ - there *is* a computational...

No, I wanted something else entirely. What went in was another way of achieving the same basic goal while keeping the system entirely as a restricted walled garden. I didn't ask for that. But again, none of this even matters. RF is here, it's staying, MJ is here, it's staying. Difference in...

To be *really* fair here, any difference in lag is actually quite minor. Server-side, I know CJ redid BC engines to be much better and send far far fewer packets. TESRs aren't too bad either, in all honesty - I just know some people who run *very* low end machines and I try to help them out. TE...

The nature of the BC API means that it is onerous to accept MJ, from a memory/CPU perspective, and yet trivial to send it. It would likewise be trivial to add an RF compatibility layer on top of something that already accepts MJ and it would cost 0 additional memory to do so. And as far as the...

Technically, this isn't *quite* right. Certain conduits have a buffer, and the buffer is 6 times the throughput of the conduit. So, 60k RF on the top-end ones, but not every conduit in the grid has a need for a buffer. ;)

Swing and a miss. RF is push-based. The difference being that it doesn't force a doWork call on you upon reception, or a required loss. It's a freeform API. Having to call useEnergy to convert from MJ internally is a kludge - it means that the received MJ has already been stored, passed through...

On the interface level, I agree - but you actually grab the PowerReceiver, not the Handler. The assistant to the helper gremlin, as it were. And the under the hood code involves the various deputy and sub-gremlins - the safe time trackers, perdition calculation, the required doWork call, etc.

Alternatively, removing the final keyword - what was actually requested - would have done this just as well. EDIT: This is getting off track from the real point of the topic, and I apologize for contributing to that. Welcome back, SpaceToad.

For point 1: Okay, so to receive BC power, you must have a PowerReceiver. This is non-negotiable. End of story. Awesome, so you just add one to your class, and store in another structure or another type of energy? Oh no wait, it's private to PowerHandler. Also non-negotiable, end of story...

Technically this is an inconsistency on the part of the chisel, but I can probably rework the Infuser to prevent it.

Er...huh? TE adds Dynamos, not another mod.

I actually had almost no influence on the BC API. It wouldn't look ANYTHING like it does if I did. The problem is that ultimately, the restricted design meant three things: 1) MJ-based Tile Entities use an additional 100+ bytes of memory that is flat out unnecessary. (Compared to RF) 2)...

Yes and no. The problem is that equating difficulty with tedium and punishment is incorrect. TE isn't really easy - it's intuitive. There is a world of difference and people seem to conflate them. Not really an FOTM. Other mods exist which are "easier" but the real appeal is that you can run a...

If this "fixed" it, the problem was never the conduit.

b11b and 3.0 have fixes to counteract the railcraft-induced block behavior, though it can't repair all worlds. In this particular case, updating will cause your ducts to once again show up. Update early and update often.

Aaaaaaaaand....3.0! Merry Christmas. :)