Jump to content

JaariAtmc

Ascended
  • Posts

    3036
  • Joined

  • Last visited

  • Days Won

    112

Everything posted by JaariAtmc

  1. These should be all the clientside mods, but to be sure I'll need your serverlog, which should be in the server folder. Please upload it to paste.ubuntu.com. I don't want a ridiculously long log in here.
  2. Logs please. Logs can be found in %appdata%\.technic\logs and will have to be uploaded to paste.ubuntu.com.
  3. Have you also changed the link, as the one used in my quote no longer exists? And with that, I mean the 4vlstwmjghw9obp/Rokh.zip part of it.
  4. Upload a log found in .technic\logs would be a good start. Can be uploaded to paste.ubuntu.com.
  5. Try using Tekkit Restrict, it has a log filter ability. http://dev.bukkit.org/bukkit-plugins/tekkit-restrict/files/58-tekkit-restrict-2-0-release/
  6. Looking at that, it is not related to Chickenbones at all. That is your java acting up, how much RAM are you allocating to your game?
  7. Not going to do much without logs then.
  8. Times out on downloading modpack file, because 1.) File does not exist. 2.) ?dl=0 should be changed to ?dl=1
  9. Get 64-bit Java, and don't go allocating more than 4 GB of RAM.
  10. Try this page instead: chickenbones.net/Pages/links.html Instead of some modrepost site.
  11. Post the full crashreport/log here: paste.ubuntu.com
  12. Yeah, inside the bin folder, there is a file called "modpack.jar" which needs to be renamed to "modpack".
  13. Hmm, interesting, you are using a different java version now. Could you try removing all java versions, then reinstalling the 64-bit version of Java?
  14. Considering you already downgraded your java, not that it would make a difference because you are running Win7, not Win10, try updating your graphics drivers. Utility can be found here: http://www.intel.com/content/www/us/en/support/detect.html
  15. If the log is too big for pastebin, use paste.ubuntu.com instead.
  16. Well, unfortunately for you, deleting a modpack also means deleting all words. Sorry to break your bubble there mate. You may have some luck if you have a backup somewhere, but judging your reaction, you do not have such a thing.
  17. Well, it is a hostile mob, so it might despawn. Can't give you any promises on that part.
  18. That makes me wonder, what kinda antivirus are you using?
  19. Not even going to bother helping as long as you have Xray in your pack. Go cheat somewhere else. Edit: Well, good for you that I didn't see it in your second report:
  20. Yes, very faulty indeed. Your modpack is a 1.7.10 modpack and not a 1.7.9 modpack (looks further down in the list), contains 1.8 and 1.9 mods, contains mods from questionable sources and finally, you capitalized the folder names which you shouldn't do. Finally, change the filename in your bin folder from "modpack.jar" to "modpack".
  21. It is not the issue that it is spawning, it is the issue that it is already there.
  22. Put it in the mods folder, same .technic folder, but modpacks -> projecthero -> mods now.
  23. Well, your fault for downloading crap off illegitimate sources. If you had actually downloaded all those mods off Curse, you wouldn't have this problem now. http://minecraft.curseforge.com/projects/minechem/files/2251057/download
  24. Yeah, that'd be a good guess indeed... Ask staff of said server (they should have forums, right?) to said entity.
×
×
  • Create New...