Jump to content

EvilOwl

Ascended
  • Posts

    1462
  • Joined

  • Last visited

  • Days Won

    36

Everything posted by EvilOwl

  1. You forgot
  2. Modpack not complete. Upload config directory
  3. Can you edit the post? 1. List the server side mods (use pastebin), there's a very nifty command in windows command line (dir /b) that can help you 2. List the client side mods separately (use pastebin) 3. Upload the whole log. This one you uploaded is not complete and something is wrong with Reikas mods.... oh, missing magical crops From what I can tell now: - you don't have AE on the server - you should. - you don't have autoutils on the server - you should - if I understand this correctly you don't have magical crops on the server - you should (and Reikas mods are requesting this also)
  4. Positive. Edit: Let me check it more thorough for you... Done.
  5. I guess you know that 1.6.4 modpacks crash with java 1.8.0_20 and above. Maybe you don't need to edit the path at all. Download this and place it in the mods directory. Security concerns? Look here. Edit: If you have more issues we have a tracker for this here.
  6. Uninstall java 1.8 and install java 1.7 (take notice these are actually two different steps). If you have problems with installing/uninstalling java there's a simple jarfix made by one of the Forge devs for 1.6.4 based modpacks. Drop it to the mods directory. Download link.
  7. You have this issue. -Xmx4096m -XX:MaxPermSize=256m -Xmx512M Read the >rules when posting next time. This wall of text shouldn't be here. We have a tracker for this kind of problems and we use pastebin (or similar sites) for logs.
  8. Upload the whole FML log and modlist. Edit: Check for dev mod versions in your environment.
  9. You need to buy the game to play the game.
  10. Logs or it didn't happen.
  11. If you can login to the Minecraft default launcher you can login to the Technic Launcher (use full email as login)
  12. Download CodeChickenCore and drop it to the mods directory. Run the pack, watch the log and post new logs if you spot errors.
  13. Need more info on that server... Public? You're the admin? Running the same (broken) version?
  14. Well.. Captainsparklez went overboard with the update. It makes Reliquary crash. xreliquary{1.2} [Reliquary] (Reliquary-1.2.175.jar) Unloaded->Constructed->Errored Temporary fix: remove Reliquary-1.2.175.jar from mods (beware this will delete all Reliquary blocks and items from the world save). You can make backups. Long term fix: contact the modpack author. Edit: You can also downgrade the pack to the previous version (also dangerous for the world save)
  15. Run the launcher. Select a modpack. Run it. Let it crash. Find the crash-reports directory in the technicmodpacksmodpack_name directory (cog wheel under the modpack logo and the Open Folder button) Upload the newest log to pastebin (copy-paste) Post the link here. Only the link, not the whole log.
  16. You need a valid account to use Technic Launcher. Edit: If you have any problems with the launcher you can visit this place.
  17. Uninstall java 1.8 then install java 1.7 or drop this to the mods directory of the pack that refuses to work.
  18. The future of ICBM doesn't look good.
  19. This is an issue for the tracker. Prepare crash logs and follow the rules when posting there.
  20. You can check with a new world in creative if that's persistent. If it is the tracker awaits you. (I suspect data corruption in one world only)
  21. Well.. You had an issue with DimDoors so I'm guessing that you deleted the dimension data directory that this mod creates. No rifts is a side effect of the fix.
  22. You can check out here but those are experimental 1.7.10 versions and can crash on you. Remember to add OpenModsLib
  23. Please leave your log here so others can benefit (I see you've edited it out).
×
×
  • Create New...