Wiring is meant to be challenging.
Just like redstone.
I've designed the system in relation to latter one, on the principe "You get basic elements, but can create ANYTHING from it".
Sidenote: MFE's, etc, do NOT use Entity IDs... arrows or TNTs do, static blocks don't. Unless you're talking about GUI id's, in which case i could use the normal MFE one.
Rather i would code the MFE to charge said stuff. But i didn't , intentional, because the Mobile Charger is some sort of "Adapter" between batterys and entirely different tools.
Period :O
Some sort of Nether-Generator is already on my TODO-List.
It will produce "free" energy similar to a solar, at about 1 EUs, all-day, only in nether. Since nether itself will usually limit your choice of energy, it will be, next to geothermal, be it's #1 energy source.
I don't see a point in creating a whole new machine for that single use. I can consider adding some sort of "1 flower > 4 dye" extraction for the normal Extractor, though.
... until Notch codes an applyable limit break for sprites.
Actually it should be easyly possible. At least some sort of instant (de)charge...
No new ores (lead).
However, if somebody can supply me with an idea how to implement lag-free radiation and a way to counter it (excluding it), you're free to ask again.
I don't like the idea of portable lights.
For once, it's entirely against the scheme of Minecraft.
Even worse, the code isn't designed to handle mobile lightsources afaik. And i'm not gonna spending hours rewriting it :O
Guess i could spent some time working on this idea. It would re-use the reinforced texture and thus solely consume a single block ID...
Not sure whether i can easyly merge redstone-input with the hatches, though... Btw, can you open wood hatches with redstone? (because in that case i would only have to disable manual opening, easy)
Once i've figured out how to manipulate wheather, without editing a basefile, i will create a few TFBP to manipulate weather within a few chunks radius.
