Jump to content

Dromoka

Members
  • Content Count

    6
  • Joined

  • Last visited

  1. I'm afraid that this didn't fix the problem... https://pastebin.com/CH93U9eF I have however now enabled the file name extensions showing so I don't make silly mistakes like that in the future
  2. I just reuploaded the 'correctly zipped' file to Technic, relaunched the launcher, reinstalled the pack and clicked Play, only to run back into the same problem. I've already tried zipping the file both ways already, neither work, so I don't think that was the issue at hand here (unless I'm being completely stupid; which is not impossible). https://pastebin.com/V8WaDgKs
  3. Ok thanks! Here is a log file of today: https://pastebin.com/FGegfwC0 I just opened Technic, played my modpack, saw that Vanilla had opened, and closed Minecraft.
  4. Ah I didn't know, thanks for the info. That could very well be the cause of the problem. How would I check the validity of the jar file? Or provide the log file? (Sorry for my lack of knowledge, technology is not my strong point)
  5. Thanks for moving it to the right forum. However I'm using Minecraft 1.12.2, for both modpacks. And Forge works fine in the first one, and as I just copy-pasted, it should be the same Forge file that's present in the second pack too.
  6. Hey guys, So I made a modpack with some mods in it and uploaded it to Technic, and it worked just fine. I then wanted to make a new modpack which was the same as the previous one, minus a few mods (as they weren't compatible with a server I wanted to make). Except this new modpack doesn't work, as each time I play with it Technic just launches Vanilla Minecraft 1.12.2. I've tried and re-tried making the modpack from scratch, as well as copying the previous modpack and just deleting the mods I didn't want anymore. But I still get the same issue. To run you through exactly what I did
×
×
  • Create New...