Jump to content

Torezu

Retired Staff
  • Posts

    6945
  • Joined

  • Last visited

  • Days Won

    6

Everything posted by Torezu

  1. It is certainly possible and even recommended to install OptiFine by simply dropping the contents into modpack.jar. EE is in 7.0.1 but not in 7.1.0, and I've heard it's difficult to install.
  2. What select mods don't load? This looks like just a Video Options > Render Distance issue.
  3. Okay, let's see the contents of your batch file. That looks like a partial directory error, so you probably need to add quotes somewhere.
  4. *twitch* Go here. Get mod_NetherOres.jar from the dropbox. Replace the one in your server's mods folder. Run it and see what happens. Otherwise, just delete the same .jar from your server's mods folder and accept that you're not going to have Nether Ores.
  5. This is a prime example of a "bug report" by someone who didn't read the stickies. Go to it!
  6. You tried to change the Mo' Creatures properties in game, didn't you? Read this thread.
  7. I would guess your RAM is being used for other things that are running. It probably can't quite get up to 1GB. You can manually set the RAM allocation in the launcher properties config file. Try something like 768 just to see what it does. Then don't push the options button again.
  8. This is likely to be an antivirus issue. Either add an exception or permissions for the launcher, or disable/uninstall your AV.
  9. There's a drop box in the upper left corner. That's your mod pack selection. If you include vanilla, there are 6 mod packs to choose from.
  10. If you're sure you're running Java 7 and only Java 7, go find the new Bukkit port for NetherOres and install it over the old one. That should fix your problem.
  11. Update to 64-bit Java 7, and get rid of all the old versions you have. Then post the whole launcher log. Use pastebin if it's too long for code tags.
  12. Launcher log?
  13. This, right here, is probably your issue. Read the Common Problems and Solutions thread next time before you report a non-existent bug.
  14. What could be wrong is that you're not posting a bug report. 3.1.0 will not work with any server. 3.0.3 should, but there are sometimes problems.
  15. Antivirus/firewall in place? Port forwarding set up incorrectly? Wrong client version? The information you provided is insufficient to diagnose...anything.
  16. You're running a 32-bit OS, and the launcher .exe sometimes doesn't cooperate. Run the .jar directly with Java. Delete the .exe version.
  17. Right-click launcher. Click Edit. You should be able to edit it with Notepad. Change the "tekkit.jar" inside the batch file to "technic-launcher.jar". That's it.
  18. I gave you a probable path. If you can't use that to find the directory...you need computer training.
  19. Go back and reread the Submit a Bug Report screen. Carefully.
  20. You need to edit the batch file to change the tekkit.jar inside it to whatever the name of the launcher is, probably technic-launcher-latest.jar or something like that.
  21. You've run the .jar with Java? And it does nothing? Try a batch file. Pull the one from the server files and rename its target if you don't know how to make one from scratch. Add "pause" as a 2nd line so you can see any error messages. It'll look something like: java -jar technic-launcher-latest.jar pause
  22. This is a typical Block ID conflict, and usually needs a reinstall to fix.
  23. Launcher log?
  24. Negative - I'm pretty sure he's in the right spot. It's just that he posted a Java error log instead of the launcher log, and that's not terribly helpful to troubleshoot with.
×
×
  • Create New...