Loader

I'm sure this is a reasonable request if you're intending to pay the developers.  Are you intending to pay for the developers?
 
If you consider for a minute that the main reason they're working on this is because they want to and they're sharing it with everyone because they're being nice.  They're paying for you to be able to play and provide a tool for installation and updates (which took time to write) and paying for your bandwidth costs when you download from them, all to make it easier for you.  They provide even the latest twitchy version if people want to play with it, but they won't call it recommended if it's not ready to be called recommended (this saves many people like me a lot of trouble we'd get from something not being ready, I don't need to pay nearly so much attention because they've got it sorted).
 
I know you're not trying to appear ungrateful, but think about what you're saying here;
The B-Team work with the Technic pack guys to make this stuff available for you to play with (and it is available, just not recommended).  Much bigger groups that should be able to afford it more easily don't bother with that, it's an exceptional interaction with their community.
The Technic pack guys develop and distribute these packs for free - this must be expensive even just for the bandwidth.  The cost in time for the people working on it is time they could be spending doing contracts for actual money - they're choosing to spend it here, for you.  This is no different in effect from spending even more money, for you.
 
The reason not asking about it is policy is probably because of how demoralizing it can be - I don't and have never worked in this team, but in similar situations I've seen similar questions or demands and believe me - when you're doing this for a community because you like them, they like you, it's all "happy fun times" and you get a bunch of guys showing up who make it not fun by making demands on your already stretched time it's really hard to keep bothering (remember you're usually working to be able to pay for all this stuff you're giving away, this is what you do in your free time).  My first reaction when seeing something like this is something along the lines of "Ugh.. you entitled little-" (I'm not saying this about you, I didn't think your post was that bad, but some can be awful and I'm trying to help you understand how another persons mindset might go from the other side of the dev process).
 
 
Now you've read all that you should be able to see what it sounds like and how it comes across - if anyone owes anyone anything, it's you that owes the Technic guys, both for their time and their money.  Your statement can translate to something like "Thanks for the free stuff, but you should give me more free stuff sooner please", which is a little ridiculous sounding when you look at it like that.  Hostility that you see from other forum members when asking about this kind of thing is based around that - if you upset the devs to the point they decide to take a week off or something then you've slowed it down, making things worse for everyone - the devs both who are working with heavier loads now, the devs who are taking a break and may even drop the project altogether if you really struck a nerve, the players who have longer to wait - everyone in the community can suffer for a comment like that, so even if there isn't a rule specifically disallowing it (which, as it was pointed out, there is), it's still a dick thing to do.
 
Sorry to rant about this here, but if even one person understands a little better because of this it'll have been worth it.

Bear in mind it still looks like the blocks are breaking on clients (obviously it works fine for singleplayer), so careful of the holes they made (but didn't really make).

I'm sure this is a reasonable request if you're intending to pay the developers.  Are you intending to pay for the developers?
 
If you consider for a minute that the main reason they're working on this is because they want to and they're sharing it with everyone because they're being nice.  They're paying for you to be able to play and provide a tool for installation and updates (which took time to write) and paying for your bandwidth costs when you download from them, all to make it easier for you.  They provide even the latest twitchy version if people want to play with it, but they won't call it recommended if it's not ready to be called recommended (this saves many people like me a lot of trouble we'd get from something not being ready, I don't need to pay nearly so much attention because they've got it sorted).
 
I know you're not trying to appear ungrateful, but think about what you're saying here;
The B-Team work with the Technic pack guys to make this stuff available for you to play with (and it is available, just not recommended).  Much bigger groups that should be able to afford it more easily don't bother with that, it's an exceptional interaction with their community.
The Technic pack guys develop and distribute these packs for free - this must be expensive even just for the bandwidth.  The cost in time for the people working on it is time they could be spending doing contracts for actual money - they're choosing to spend it here, for you.  This is no different in effect from spending even more money, for you.
 
The reason not asking about it is policy is probably because of how demoralizing it can be - I don't and have never worked in this team, but in similar situations I've seen similar questions or demands and believe me - when you're doing this for a community because you like them, they like you, it's all "happy fun times" and you get a bunch of guys showing up who make it not fun by making demands on your already stretched time it's really hard to keep bothering (remember you're usually working to be able to pay for all this stuff you're giving away, this is what you do in your free time).  My first reaction when seeing something like this is something along the lines of "Ugh.. you entitled little-" (I'm not saying this about you, I didn't think your post was that bad, but some can be awful and I'm trying to help you understand how another persons mindset might go from the other side of the dev process).
 
 
Now you've read all that you should be able to see what it sounds like and how it comes across - if anyone owes anyone anything, it's you that owes the Technic guys, both for their time and their money.  Your statement can translate to something like "Thanks for the free stuff, but you should give me more free stuff sooner please", which is a little ridiculous sounding when you look at it like that.  Hostility that you see from other forum members when asking about this kind of thing is based around that - if you upset the devs to the point they decide to take a week off or something then you've slowed it down, making things worse for everyone - the devs both who are working with heavier loads now, the devs who are taking a break and may even drop the project altogether if you really struck a nerve, the players who have longer to wait - everyone in the community can suffer for a comment like that, so even if there isn't a rule specifically disallowing it (which, as it was pointed out, there is), it's still a dick thing to do.
 
Sorry to rant about this here, but if even one person understands a little better because of this it'll have been worth it.

I'm sure this is a reasonable request if you're intending to pay the developers.  Are you intending to pay for the developers?
 
If you consider for a minute that the main reason they're working on this is because they want to and they're sharing it with everyone because they're being nice.  They're paying for you to be able to play and provide a tool for installation and updates (which took time to write) and paying for your bandwidth costs when you download from them, all to make it easier for you.  They provide even the latest twitchy version if people want to play with it, but they won't call it recommended if it's not ready to be called recommended (this saves many people like me a lot of trouble we'd get from something not being ready, I don't need to pay nearly so much attention because they've got it sorted).
 
I know you're not trying to appear ungrateful, but think about what you're saying here;
The B-Team work with the Technic pack guys to make this stuff available for you to play with (and it is available, just not recommended).  Much bigger groups that should be able to afford it more easily don't bother with that, it's an exceptional interaction with their community.
The Technic pack guys develop and distribute these packs for free - this must be expensive even just for the bandwidth.  The cost in time for the people working on it is time they could be spending doing contracts for actual money - they're choosing to spend it here, for you.  This is no different in effect from spending even more money, for you.
 
The reason not asking about it is policy is probably because of how demoralizing it can be - I don't and have never worked in this team, but in similar situations I've seen similar questions or demands and believe me - when you're doing this for a community because you like them, they like you, it's all "happy fun times" and you get a bunch of guys showing up who make it not fun by making demands on your already stretched time it's really hard to keep bothering (remember you're usually working to be able to pay for all this stuff you're giving away, this is what you do in your free time).  My first reaction when seeing something like this is something along the lines of "Ugh.. you entitled little-" (I'm not saying this about you, I didn't think your post was that bad, but some can be awful and I'm trying to help you understand how another persons mindset might go from the other side of the dev process).
 
 
Now you've read all that you should be able to see what it sounds like and how it comes across - if anyone owes anyone anything, it's you that owes the Technic guys, both for their time and their money.  Your statement can translate to something like "Thanks for the free stuff, but you should give me more free stuff sooner please", which is a little ridiculous sounding when you look at it like that.  Hostility that you see from other forum members when asking about this kind of thing is based around that - if you upset the devs to the point they decide to take a week off or something then you've slowed it down, making things worse for everyone - the devs both who are working with heavier loads now, the devs who are taking a break and may even drop the project altogether if you really struck a nerve, the players who have longer to wait - everyone in the community can suffer for a comment like that, so even if there isn't a rule specifically disallowing it (which, as it was pointed out, there is), it's still a dick thing to do.
 
Sorry to rant about this here, but if even one person understands a little better because of this it'll have been worth it.

Awesomebynature, this isn't the tracker, but it is a common fix mentioned in this thread a few times.
For other browsers (and you);
 
If the launcher loads when you click play, then immediately drops you out of minecraft back into the launcher, do this first;
For Windows:
Update Java 64-bit if you have a 64-bit OS, if you're not sure, try it (there's no harm, a 32-bit OS simply won't run it).
You can get those downloads here; https://www.java.com/en/download/manual.jsp
 
For MacOS X:
You need the JDK rather than the JRE as the JRE only updates Java links for your browser.
You can get that download here; http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html
Note: If you're on MacOS 10.6 (Snow Leopard) or older then neither Apple nor Oracle officially support you for Java 1.7+.  It's possible to force an install using a package manager like Pacifist but your best bet is to upgrade to the latest MacOS version if you can - it's free for most MacOS users.

Anything that can take or receive power in TE you should be careful to connect only once to a GC power source.  In your example - letting the TE conduit (can take in power) touch the solar panel or wire on multiple sides in the same conduit - the panel/wire outputs power to the TE system each time it touches, not an overall calculation like it should be, so if you had a TE conduit going around a wire in a U shape it'd touch it three times and draw however much power is in the wire out three times (this is where the infinite power comes from).  The corruption comes from the fact that this extra power can exceed the limits that it should be able to in the TE system and after a point the number gets so high that minecraft can't store it in the allocated space any more and it rolls into the next byte of the chunk save file.
 
A tesseract would be fine in all likelyhood, use GC cables most of the way and go into the tesseract once only, or just make sure any TE conduit touches whatever wire network you have only once and you'll be fine.

Anything that can take or receive power in TE you should be careful to connect only once to a GC power source.  In your example - letting the TE conduit (can take in power) touch the solar panel or wire on multiple sides in the same conduit - the panel/wire outputs power to the TE system each time it touches, not an overall calculation like it should be, so if you had a TE conduit going around a wire in a U shape it'd touch it three times and draw however much power is in the wire out three times (this is where the infinite power comes from).  The corruption comes from the fact that this extra power can exceed the limits that it should be able to in the TE system and after a point the number gets so high that minecraft can't store it in the allocated space any more and it rolls into the next byte of the chunk save file.
 
A tesseract would be fine in all likelyhood, use GC cables most of the way and go into the tesseract once only, or just make sure any TE conduit touches whatever wire network you have only once and you'll be fine.

Fried rice!
 
Mmm.
 
It's not a mod that's greatly about efficiency, that's true, but when another player comes over to visit and you offer them baked potato for the billionth time, don't be surprised if they finally snap and shank you.  It goes some way to prevent that I suppose.

It demonstrates that the MFR harvester can handle pretty much anything you throw at it with its algorithms (it was primarily a test of that originally, but was left in because it's awesome).  People no longer have a leg to stand on when arguing that the harvester can't handle a modded tree like the Red|power stained trees or things like the Redwood trees (which have both caused issues in previous versions), it focuses the attention back where it belongs.
 
Last I looked these could only come from dungeon chests - has that changed?

*Loader's brain makes little crackling noises*
 
Try opening up a DLL or an EXE with notepad++, let me know what you see

*Loader's brain makes little crackling noises*
 
Try opening up a DLL or an EXE with notepad++, let me know what you see

That's an odd question, but I guess you're more familiar with JavaPython than Python, maybe? (I am completely unfamiliar with javapython )
 
.PYD files are compiled already so there's no easy way to read then - think of them as a DLL.  .PYC files are compiled bytecode and again, there's not much you can do with that - think of it as a kind of .EXE if you like.  .PYO files are simply an optimised version of PYC files.
 
There's probably no useful way to edit any of those, if you really want to then what you need to look up is reverse engineering.  What you probably want though is the .PY files (uncompiled sourcecode).
 
The second thing is pretty easy, open up the NEI window and look for an option called "Dump ID Map Now" which will create a list of item IDs, though the format you get will be different it'll give you the item name and ID which I think is what you're after.  It doesn't give you metadata, so that means manually doing it for chisel and wool, things like that, but that's nothing compared with reversing those files.
 
Best of luck!

The strongboxes can be picked up with a crescent hammer too, if it doesn't have to be an actual chest.

You can tell when they're upset, they're not messing around.
 

I do my best to keep the Signature Gnomes in check but newbies trying to justify breaking the rules by claiming we should just accept people will be lazy and willfully ignorant, well that just riles them up.

Reset the pack, that should sort it (the cog on the left under the b-team menu icon has that option).
 
That'll cause it to redownload the modpack files, including (hopefully) the minecraft april-fools version you seem to have.

The tesseracts have a version that can transmit liquids, so you could do it like this;
Have a tesseract in the nether hooked up to a liquid tank and pipes Set the tank to pump out into the tesseract then fill the tank with lava Put down a poppet protection shelf in that chunk (to keep the tanks, pumps and tesseract loaded). Set up a tesseract in the overworld, set it to the same channel as the nether one Set up pipes leading to wherever you need the lava in the overworld This isn't automatic, every once in a while you'll need to go top up the tank in the nether manually as there's not any pumps in this mod, but that's probably what that person meant.

There also needs to be something (anything) molten in the smeltery so it'll do damage, melt an iron ingot or something first.
 
Your English seems fine to me, better than many native speakers I meet on the internet.  Dresden is a lovely place

Oh, I've got it!  I know why this feels like such a familiar situation!
 



 
Deja-vu solved

Oh, I've got it!  I know why this feels like such a familiar situation!
 



 
Deja-vu solved

It's actually in the hats interface, check there;

You can back-up your save in a various manner of ways.
 
The first being just to back-up the entire .technic folder. The issue with this is that it back-ups every single file associated with every single modpack you ever played as well as additional files that are not important to the saves themselves. This is really only useful if you are messing with technic related files that could cause damage to saves, modpacks, etc.
 
The second being to back-up the modpacks folder. This would get rid of some useless files for world save back-ups but it would copy every single modpacks information and may contain unnecessary information if your only intent is to back-up world saves for testing purposes. This method is great though if you want to move the modpack saves and settings from computer to computer as you can just place this back into the technic folder and be back up and running with little issue.
 
The third being to actually back-up the "saves" folder in the individual modpack folder. This is great for saving all worlds for that particular modpack and can be useful when testing fixes, etc. This would cover all saves you ever have though in the modpack folder and can be fairly large in the event you have a lot of worlds or a few worlds with thousands of chunks found. Similarly to the second option, this is best for transferring worlds from one computer to another if you want to keep worlds synchronized between computers you play on (ie: at home on dekstop and in class on laptop [shame on you but i did it too])
 
fourth being back-up of the individual world save. This only keeps the information to the one world and that world only. This is usually the option most people want when testing, or are afraid of something happening or just would like to keep a back-up in the event something DOES go horribly wrong.
 
 
For the first option, you would have to know where you installed the technic launcher to. This is usually a default of "C:Users<USERNAME>AppDataRoaming.technic" on windows vista and later. This location can be found however via the use of the launcher. Run the launcher and click the cog icon in the top right. You should see a text field with the location of the technic installation on that screen. You can easily navigate there by clicking on "Logs" and going up a folder where you would see all of the technic related files.
 
The second option would be the "modpack" folder located in the base technic folder. This can be found by following the above instructions to locate the technic installation.
 
third and fourth option are similarly found. You can use the launcher to find them by clicking on the cog icon under the desired modpack logo and then clicking on "Open Folder" - the third option just copies the "saves" folder found there. The fourth going into the saves folder then copying the world folder with the respective world name you wish to back-up.
 
Copying them anywhere convenient for you outside of the technic folders is a great way to back them up and to prevent accidental backup deletion in the event you have an issue and someone wants you to delete the entire technic folder. To restore any of the back-up methods you would simply just copy back the folder into the respective location that you copied it from.

FORUMS DON'T USUALLY HAVE NO SOUND!?!
 
I'VE BEEN ONLY IMAGINING US ALL YELLING ALL THESE YEARS!!!

Oh yeah, to maximize your chances talk to them all on facebook, comment on their videos with what you'd like to see - I just meant to give an example (I picked chimneyswift because he does witchery already).

No, he means don't worry - it'll come in the next version.
 
Please post your logs up on the tracker and I'll take a look, you can find links to help in my sig