Torezu

It really could be anything. I'd say just go grab a new copy of the launcher, put it in the same place, and try to run it. Otherwise, post a bug report.

You can also use "standard" Fuel, the Destruction Catalyst will use anything from redstone dust to Aeternalis fuel as power. There's a 16 EMC/block destruction cost, so redstone won't go very far.

This is an extremely odd error. Are they 16x16 chunks, or is your view range just set really short?

Reading the stickies?

Cinematic motion control, or freeze cursor. Either way, not much good to your average player.

They're in the Rei's minimap subfolder somewhere. They'll be labelled by world, and are computer-specific.

I made a suggestion to allow the launcher in Norton - did you look into that? Turning everything off will not necessarily mean the software will allow your internet connection to do some things. You need to add an exception or do something active with Norton, or uninstall it entirely.

This isn't a launcher bug - it's a mod pack bug, with Technic I'm assuming from the mod list. Why don't you post a bug report in the right section?

That's not a launcher log from where you've been playing the game for 20 minutes - try again. It looks like an AV may be blocking your connection, but you say you don't have one, so...check for a firewall?

You want this thread. Follow the advice from torylon toward the end of the page. Or completely reinstall. Your choice.

Then it's McAfee. Look into adding an exception for the launcher, and probably also Minecraft and Java.

You remapped a critical key. I'm guessing that some mod in Technic doesn't like that.

Run with the launcher .jar instead - see if that helps. Oh, and double check to make sure your firewall isn't blocking the launcher.

Then you probably need the newest version of the launcher - yours is old.

That last line in the path is what I was looking for in the first place. You've got a bunch of extra stuff in there, like Roxio (media creator) and Windows Live stuff that you could take out if you knew what you were doing. Otherwise Java should be working fine.

You have installed the Development Build. Go into options on the launcher screen and change it to 3.0.3 ('Always Use Recommended Build' does this automatically).

Good news and bad news. Bad news: You're probably going to have to reinstall, if you tried to edit the block IDs, unless you know what you changed. Good news: The reinstall will fix everything. What you should have done is notice that they're the same block, conclude that you had duplicate mod files, gone into your .techniclauncher\technicssp\mods folder, found the duplicates, and deleted the older ones. @Brunswick: *light smack*

You don't have a 64-bit OS, so you need to use 32-bit Java (which you are). However, 32-bit Java can only ever use 1.5GB of RAM, including the RAM used for the garbage disposal process. Try editing the launcher properties to reduce your memory allocation to 768 MB (I think all you need is the number). You can use Normal, but you will want to reduce the other graphical settings to compensate, and I strongly recommend never using a 32x or higher texture pack.

You probably need to delete your .minecraft and .techniclauncher\technicssp folders and reinstall technic. Back up any world(s)\waypoints you want to save. It would seem your keyboard configuration is messing something up, and configuration files can be several places. I'd be sure to disable McAfee during this whole process.

Yup. Thought so. Replace the: %APPDATA%\.techniclauncher\technic-launcher.jar in your batch file with "c:\Users\Packard Bell\AppData\Roaming\.techniclauncher\technic-launcher.jar" Keep the quotes.

Try deleting your .minecraft folder. Make backups of whatever you want to save, of course. NullPointerExceptions are hard to pin down.

Whaa...where did you come from? Post your own bug report. Your situation is likely not to be the same.

It's at the bottom. Anyway, use pastebin.

Just delete the mod .jar or .zip from the server \mods folder.

I was saying that the path I gave you is usually the right path, but if you're using the 32-bit version of Java for whatever reason, it might be Program Files (x86), for example. Just check to make sure the path I gave was right, and then use it.