Jump to content

Torezu

Retired Staff
  • Posts

    6945
  • Joined

  • Last visited

  • Days Won

    6

Everything posted by Torezu

  1. Yes. Drop those memory allocation arguments in the Java command line to something your server has the RAM to run, like -xMs512M -xMx1g. The -xMs arg is for starting RAM allocation, while the -xMx one is for maximum. Be warned that if you're trying to run a client on the same machine, and you don't have 2GB or so to dedicate to it, your client (and probably server) will run like crap.
  2. And he's made off with all of our punctuation!
  3. I'd remove the JDK unless you intend on doing some programming with Java in the near future. Get Java 7u5 (JRE), 64-bit of course, and then reboot. That should fix at least this error. I'd consider uninstalling AVG entirely, though. It's not a good antivirus any more.
  4. Have you restarted your computer since this occurred? If not, Java's probably still running. Try closing it (java.exe) with Task Manager in Processes and rerunning the launcher.
  5. Try 3.5 next, then 2 - I think you need 3.5 though.
  6. So you removed AVG entirely, not just disabled it? It likes to interfere even when disabled. Also, did you get a new copy of the launcher and delete your tekkit folder before attempting to reinstall?
  7. I'm not inclined to take your money. I notice you updated your launcher. Did you delete the techniclauncher folder at the same time? That would be a good idea.
  8. Install the .NET Framework.
  9. Works fine for me. Oh, and I'd update your Java. Yours is a bit old.
  10. You don't have 64-bit Java, or the launcher isn't using it.
  11. 1) It's not a company, its resources are (likely) nowhere near Mojang's, and it has 3 admins and less than a dozen moderators. I think your mental picture is flawed somehow. 2) Technic/Tekkit may just skip 1.3 entirely, depending on the actions of the modders, Mojang, and anyone else involved. 3) "Tekkit" doesn't have a modder staff. Some of the staff may be capable of modding, yes, but the mods actually being assembled don't come from this site.
  12. Fix it yourself, then.
  13. You may want to figure out why those clusters were there. The usual culprits are quarries and BC pipe systems that are out of room to put stuff somewhere.
  14. Nope. BuildCraft pipes don't do well when unloaded (chunk-wise). It's either that, or your chest was full. Post pictures of your setup and somebody might decide to take a look and diagnose the problem.
  15. Based on the mods on the list, 3.0.4, which needs 3.0.3 as a client.
  16. S'okay, I think it was Mojang's (poor) idea of spawn protection to keep griefing down. The Bukkit team and modders have provided plugins with a hundred times the level of protection, though.
  17. And so the thread dies.
  18. What FAQ? That's been a feature of vanilla MC servers for a long time.
  19. The client version that matches 3.0.4 is now, and has always been since 3.0.4 came out, 3.0.3 - 3.0.4 was a server-side-only update.
  20. Are you right next to the spawn-in point? Only OPs and people with permissions can break blocks there.
  21. Huh? The server's running CraftBukkit 1.3.1, so not Tekkit. Tekkit hasn't been updated to use 1.3.1, and it won't for quite some time.
  22. You need the brackets, exactly like he said to type it.
  23. He was asking if you had tried running the .jar instead of the .exe - have you? Also, stop triple-posting.
  24. Torezu

    cant play

    -.- Holy crap, you're right. OP: 1GB of ram, and you're running Win7 Premium? Does your computer scream and cry every time you push the power button?
  25. You missed the button. Look for the button.
×
×
  • Create New...