Jump to content

Torezu

Retired Staff
  • Posts

    6945
  • Joined

  • Last visited

  • Days Won

    6

Everything posted by Torezu

  1. You're the only person I've seen posting this recently, though there's always a first person when minecraft.net is having issues, or the Technic site is down. It just doesn't look like that's the issue right now. So: - You've definitely deleted the entire .techniclauncher folder? - You're 100% certain you have 64-bit Java to match your 64-bit OS ("java -version" in a command prompt will confirm this) - You tried running the .jar version of the launcher after the .exe didn't work?
  2. If you're going to use "than" for comparison, you have to have a level of comparison. It says "Checking Launcher Version" more often than it doesn't do anything, perhaps?
  3. If you like those, you could try banana s'mores. Let me know how those go. We're not being very helpful because you're in the wrong section, asking something over which we have no control, and are still behind the times. 3.1.2 is out already.
  4. That...strikes me as a made-up acronym. And the "Did you read this?" was for the OP.
  5. I like chocolate-covered espresso beans.
  6. See, this is why you don't put bug reports in the wrong section of the forum.
  7. Jay?, are you being nice and helping with a Technic problem in the launcher section? That's kind of you!
  8. The launcher, and Minecraft, won't force you to do anything. You updated, and converted from MC 1.1 to MC 1.2.5, and it changed world formats, and broke your world. If you'd done a little bit of reading before updating, you'd know that you'd be starting a new world anyway, most likely.
  9. Did you guys all miss the Tekkit sections?
  10. That just means those particular mods don't have blocks, or have blocks that don't have metadata. It's normal. As for your missing mods: that's what happens when you update. It damages worlds, because so many mods update and so many block IDs change. I would pretty much assume you need to start a new world every time a new minor version (that's moving from 7.1 to 7.2, for example) comes out. If you really don't want to start a new world, do some research to figure out how to avoid that. It may just involve not updating.
  11. You probably need to reinstall Java, making sure you have the 64-bit version.
  12. Read this. Pay careful attention to the part on antivirus software.
  13. Grab a new copy of the launcher, then go double-check to make sure you don't have multiple copies or the wrong bit version of Java.
  14. The...pinned threads...at the top of every forum section? This one, in particular, would be helpful to you.
  15. What do you mean by "desktop application"? If you're just talking about a shortcut, what's to stop you from sticking a batch file on your desktop that runs Java with the launcher?
  16. "Java Version: 5" This. This is your problem, right here.
  17. I can just see it now. Anonymous people by the hundreds posting bugs with not enough information to help them, then them screaming about how unhelpful those Technic people are. Yeah, no, that probably wouldn't happen...would it?
  18. Then you should run the .jar with a batch file. There's one in with the server files you can just edit and use if you want.
  19. Yup, I'm going to start handing out a stock "Low Effort Post" warning for people that don't read that thread before posting, and have a bug report like this. It'll generate a few more kellers, but...oh well.
  20. Did you read this?
  21. I would update to Java 7, first of all - the newest mods in Tekkit really need it to run, and it's nicer on system resources anyway. Then I'd delete your .techniclauncher\tekkit folder, select the proper Tekkit version for the server, and reinstall. Keep in mind that your waypoints and configs will go with your tekkit folder unless you back them up. Configs may not be a big deal (easy to redo), but waypoints...yeah, those can be a pain to replace.
  22. From the Common Problems and Solutions thread you should have read before posting this: Opening the .exe does nothing, or flashes a loading icon, or says "checking launcher version" then closes. This is a Java issue. The most common cause is using 32 bit Java. If your Operating system is 64 bit, make sure you update to the latest 64 bit version of Java. Links on www.technicpack.net. If no matter what you do, the exe just doens't work, go to your .techniclauncher folder and there should be a .jar in there. If not then download it from www.technicpack.net and use that. Read further up the list for how to determine the bit version of your OS or JAVA.
  23. Use the .jar version of the launcher instead. 32-bit Windows doesn't like the .exe most of the time.
  24. You updated...and you didn't think it would mess up your world? I'd think that through a little more in the future.
  25. What, out of curiosity, is the path for your copy of Java? It's usually something like C:\Program Files\Java\jre7\bin - that may be the source of the illegal character.
×
×
  • Create New...