Torezu

There's a section for posts like this, and a post in it to use for Small Scale Recruitment (General Tekkit SMP). Try there.

You have nothing else Java-related running? It doesn't sound like you should have a problem allocated 512MB to 1GB - I wouldn't go as high as 1.5GB.

Please ignore this man. It's normal for Tekkit to run out of the box, as it is a Bukkit server. How are you attempting to run the server? Also, this is in the wrong place. I suggest posting a bug report in the Tekkit Bug Board with more relevant information.

And advanced machines need a piece of cobble or something in the power/battery slot, or RP tubes will put stuff in there too.

You can either put quotes around the Java path part, or add the Java bin directory to your system path variable, like so: Control Panel > System > Advanced System Settings > Advanced tab > Environment variables... > Click on Path and then Edit... > add exactly this to the end of the Variable value (without the quotes): ";C:\Program Files (x86)\Java\jre7\bin" That's if you're using 32-bit Java. If it's 64-bit like you should be using if you have a 64-bit OS, remove the (x86).

Update to, and correctly use, Java 7 to run the server.

Pistons do not explode. The only things that explode are machines that receive too much voltage, wires (mini-boom, melting), steam/combustion engines, creepers, dynamite, etc.

That's a sign of world corruption, usually caused by power loss crashes on the server. Regrettably, it usually means taking drastic measures like loading the world from a backup.

Did you pick a mod pack? There's a drop box in the upper-left corner.

The BarrackBlockID error resolution is floating around the boards somewhere that's not in the YogBox sections (now defunct). Did you try the search bar?

I'll stack on top of this by adding that if you could just as easily, no thanks to me, figure it out yourself, why bother posting at all?

I would not have assigned 13GB to the server, tbh. That just doesn't leave enough for Java to use its garbage disposal routines. Maybe 10?

I gave you a possible solution. Were you paying attention? If you want to use Linux as an OS, you may be expected to do your own troubleshooting. Well, really, you may be expected to do your own troubleshooting regardless of your OS, but we're more familiar with Windows and Mac OS here (Windows only, myself), so there you go.

Try creating and running a batch file using Java to run the launcher then, like so: 1) Open Notepad or any other basic text editor. 2) Type the following two lines: java -jar technic-launcher.jar pause 3) Save that as a batch file (launcher.bat, for example) in the same folder as the launcher .jar 4) Double-click it in Windows Explorer and see what happens.

Oops, you're on a Mac. Yeah, no clue then, sorry. You probably want getpacket as the command, if I had to guess, but...

Hmmm - wonder which OS is better? Anyway, let me get this straight. You're running an external server, with software that might not be compatible, using a server wrapper that's not designed for this, controlling a poorly-written (yes, Minecraft is) piece of Java software with over 40 mods, and you're complaining because you have to do a bit of troubleshooting? You might be stretching your indignation a little.

That's probably correct, then. Go check in your Program Files directory to make sure the Java\jre7\bin folder is there, then do a restart.

That should have worked - are you sure you're using 64-bit Java? Try tracking down your Java folder, to see if it's in Program Files or Program Files (x86). If it's in the latter, it's 32-bit Java.

I assume you're using localhost to join. Check your externally visible IP address. It may be through your router software, or you may just want to run ipconfig from a command prompt.

This is in fact the wrong place, as there's an LP section on the forum. I'll move this there.

Oh, well in that case it was almost definitely a Mercurial Eye. Tearing the entire volcano down and rebuilding it with pink wool manually would take forever, and wool doesn't have a real high EMC value, so...I would consider banning Mercurial Eyes altogether, except that they're so darned useful as building tools.

It's not poor support, you're exhibiting poor manners by intruding on someone else's help request with something that isn't the same problem. Learn to tell the difference, and to spell.

A black command prompt flashing on screen is usually a sign that the launcher can't find Java, regardless of whether it lets you try to run it with Java or not. Try adding the Java bin directory to your system path variable, like so: Control Panel > System > Advanced System Settings > Advanced tab > Environment variables... > Click on Path and then Edit... > add exactly this to the end of the Variable value (without the quotes): ";C:\Program Files\Java\jre7\bin"

First off, that's hilarious. Second, are you sure it's not just a texture pack issue? Third, that's hilarious. Fourth, the only things I can think of that will do this are extensive use of a Mercurial Eye (and it would take a while, unless just the surface was changed), or somebody with WorldEdit and a penchant for mischief.

It looks like your update botched. Save your waypoints (rei_minimap folder in tekkit directory), delete the tekkit folder, manual-select 3.1.2, and reinstall with a new copy of the launcher.