planetguy

IMO it's an OK necropost, since starting a new thread for this same forum game would be redundant. Your eye colours now clash hideously. You are thrown in front of a train by a passing mentally unstable graphic designer. I wish I didn't have to look at the wiki to understand all the mods in Big Dig.

I've never seen anything like that, but then again, I don't know if I've ever dropped a cropnalyzer before. I'll see if I can replicate it. Edit: Upon further testing, it does indeed kick anyone who drops cropnalyzers with "q", but you can safely drop them by opening your inventory and placing the item outside the GUI. I guess the solution is to not drop cropnalyzers with "q".

Sounds good. A GUI is probably easier to code/texture for you and easier to use for us; I'd hate to have to dig up or look really closely at a translocator to see what colour code it is.

Which Tekkit and what version are you using? It looks like a bug in IC2, so maybe it's been fixed in a later mod (and later modpack) version.

That fix deals with Java running out of memory because it can't reserve what it reserves by default. It might be worth a try, but I doubt it would help.

The demon theprolo should be smited by the power of Turtleism for opposing all that is good, just and hard-shelled. And Poryy should be banned for ninja-ing me despite being a lobster. How are lobsters supposed to be ninjas, anyway?

Java doesn't like the ! in your computer account username. You can try something like the minecraft.bat trick, but I don't know if the launcher supports it.

ChickenChunks is crashing while trying to save. Use a Tekkit Lite version with an updated ChickenChunks or delete the mod from your mods folder.

Feed the Beast has some impressive adventure maps that are based on modded Minecraft, if that's what you are looking for. There might be some maps floating around Platform, too, but you'll have to find them yourself.

Mystcraft and Dimensional Doors are both rather greedy performance wise. Chunk loader blocks cause servers to take a performance hit for each time they are used. Loading chunks, especially new chunks, takes a fair bit of CPU power. If you have lots of trouble, you might want to try using MCPC+ instead of the Tekkit Lite server jar.

That's the spirit!

dwwojcik should be banned, since he needs more training on how to not derail threads. What if he freightens the children? He's just on the wrong track.

He is planning to add it.

I've started building against 1.6, so if you used my latest build link it won't work on 1.5. For including with a modpack, this works on 1.5.x extracted into the minecraft root directory.

I have no idea what would possibly do that... Which Gizmos version are you using?

It might be possible to do what you want with the Bukkit plugin Transporter, which if I remember correctly supports chat sharing. I'm sure it allows teleporting between servers if you use their client patch, which is included in Tekkit Classic and possibly the other modpacks, or could certainly be added to a custom modpack.

Reinstall Java?

It's down again. In the console on MCMA it says something about being out of space on the filesystem.

The plugins aren't loaded.

It might help.

Yes, it's worth trying in my opinion.

If you can, run the server and any clients on different computers. If you already are, you might need to take out some client-side-only mods running on the server.

If you run it from a start script, it uses the server package. If you open it with Java, it uses your home directory and nothing in the server package works properly.

Would using the default garbage collection setup cause problems? The error mentions trying to free a pointer that isn't allocated, and that would be a GC bug. If I had to guess, it would be a result of concurrent garbage collection (switched on by +UseConcMarkSweepGC) interfering with object creation, so you might have better luck doing without it.

The crash looks like an error inside the JVM, not in Java code like Minecraft or a mod. My one guess as to what it would be is some mod uses a weird native library that is crashing. You could try a different MCPC+ build, but I doubt it would help much. You could try reinstalling Java or using the default JVM arguments, since it looks a bit like some debug argument passed to the JVM leads to a breakpoint being triggered.