Jump to content

Dromoka

Members
  • Posts

    6
  • Joined

  • Last visited

Dromoka's Achievements

Dirt

Dirt (1/9)

0

Reputation

  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 with the copying: I took my old modpack files (the one that works), copied the whole folder on my desktop, went into the 'mods' folder, deleted the mod files I didn't want anymore, selected the modpack folder, added to archive (using WinRAR), made it a ZIP, uploaded the file into Dropbox, copied the Share link to the modpack file location in Technic (changing the last part to dl=1), update the modpack, then open the Technic Launcher, find and install my new modpack, then click Play, which opens Vanilla Minecraft... My guess is that this problem could be due to Forge not being properly installed in the new modpack as it has a new location, but normally all the files in the old modpack are also present in the new one. Another possibility is that the mods in the new folder aren't properly installed on a 'clean client'. Or it could be something else; I'm not very tech-savvy. Either way I hope someone is able to tell me what the problem might be and how exactly I can fix it. Any help is greatly appreciated! Thanks in advance! (PS: both my modpacks are hidden as I haven't yet asked for permission from the mod creators to add their mods to a modpack. I will of course get their permission before making the modpacks public)
×
×
  • Create New...