Jump to content

jumpandshootbeef

Members
  • Posts

    276
  • Joined

  • Last visited

  • Days Won

    6

Everything posted by jumpandshootbeef

  1. You say that doesn't fix it. I try to fix it, thats how it works Allright, first things first. The error in your log is the following: The world 370d2070 (world) may have leaked: first encounter (5 occurences). So this means some mod screws up the unloading of your world, if you have a shady mod in your modpack that alters these kind of actions, try to remove it. I found this too:You can fix this by making sure the worlds never unload. Start server Go to dimension (nether, end, twilight forest, ..) Place loader (make sure with /chunkloaders that it is properly doing its job) Stop server Start server (there shouldn't be any more world leakage) My guess is that when a world unloads some mod does not properly do so and keeps a reference to the old world. Then, after loading the world again, there are two versions. Placing items (only really seen it with chunk loading blocks) crashes the client and freaks the server out, which results in regenerated chunks. Again, all my speculation, based on the post by Nallar I quoted above. There is also this program you can try to use to fix it: http://www.ej-technologies.com/products/jprofiler/overview.html I hope this does help you , Greetings from holland
  2. Ehm. That is quite a rare issue. Try downloading CCleaner or an advanced deleter program. And clean up ALL the bits the technic launcher left behind. Also, delete your current java version and download java 8 & 64 bits http://javadl.sun.com/webapps/download/AutoDL?BundleId=113219 After you've done that try downloading the technic launcher again
  3. Well I've found out that that error doesn't have any significance. There is another error causing this. The error we have been discussing happens every time. Please turn on console, launch the pack and give the error code.
  4. You can manually fix it. Download the latest forge universal for your version (1.7/1.8 I dont know) and put it in modpacks/madpack 3.0/bin and rename it to modpack.jar. That should fix it
  5. Your video card drivers are outdated. Update them
  6. Can you pastebin your fml-latest.log or even better your crash log if it is present?
  7. I dont know how mac handles things, cant help you
  8. I do not have an idea where this comes from, try googling it. I am not really able to do do much, have computer problems
  9. No it is just the launcher, but have you completely ddeleted the .technic folder from your computer and re-downloaded the launcher?
  10. I have no idea what it causing this, you sure you allocated 2-3 gig ram?
  11. uninstall your moreplanets mod. It causes this. I do not know how. 4space is also a mod which adds planets for galacticraft
  12. Then add it to your modpack, copy a working one from another 1.7.10 modpack
  13. Thats very weird indeed, I'll see if googling it brings up anything option 1: if you have 64-bit java, you can run it directly from "C:Program FilesJavajre#binjava.exe" replacing the # symbol with either 7 or 8 depending on which version you have installed, so you'd just replace the "java" part in the batch file with that entire string, including the quotes. There is also other people saying this: yes! ive managed to get it working myself. i just uninstalled every version of java then installed it again and now it works. Thanks Gen
  14. 5/7 haha I get that quote damn you Brendan!
  15. Try checking the buildcraft config. And if you cant find anything there, make a video or take a few screenshots, I might see it there
  16. so it works now? And what I meant with upload it to a hosting company: upload it to dropbox or such because no-one except for you has permission to download via the link you provided
  17. it was the minecraft.jar in your bin folder there was a minecraft.jar which was corrupted
  18. The SLF4J thing is nothing. Ignore it. Did you download the 64 bit version of java? Set your allocated RAM to 2-3 gig in launcher options
  19. I've had that problem too. I fixed it by buying more RAM
  20. Have you migrated your account to mojang? Then use your mojang email adress and mojang password to log in
  21. What does your console say when you try to download a modpack? Enable it in launcher options
  22. The logs were the ones you should have posted on pastebin and then posted the link here. But this works fine too. I'm going to instill it now and see what the crash report/fml-latest.log says. I'll find out what the problem is in no time Edit 1: I found this: [B#339] [12:58:04] [main/ERROR] [FML]: There is a binary discrepency between the expected input class ahu (ahu) and the actual class. Checksum on disk is 782b2e42, in patch 746fe971. Things are probably about to go very wrong. Did you put something into the jar file? [B#339] [12:58:04] [main/ERROR] [FML]: The game is going to exit, because this is a critical error, and it is very improbable that the modded game will work, please obtain clean jar files. You can try to re-download the forge-latest universal.jar Looking further into it now Edit 2: It still happens when I download a clean version of forge. Checking other jars with a bug tracker Edit 3: There was a .litemod file (voxelmap). Do not use these! These are for the liteloader. Just use normal forge, liteloader is not handy anymore.} And I think I have found the problem Edit 4: I have found one of the problems. You have downloaded the 1.8 version of botania! I think there are a couple more of these mistakes. Edit 5: I fixed it! Here are the things you need to do: -change your bin folder to only have the modpack.jar (in the file that gets downloaded when you install the modpack) Because that minecraft.jar is corrupted So the inside of your modpack's bin folder only has modpack.jar in it. This is how it is intended. -Download the 1.7 version of botania -Download the voxelmap.jar instead of the .litemod
×
×
  • Create New...