-
Posts
3 -
Joined
-
Last visited
Profile Information
-
Gender
Male
-
Minecraft In-Game Name
MarshTheBacca
MarshTheBacca's Achievements
Dirt (1/9)
0
Reputation
-
MarshTheBacca changed their profile photo
-
MarshTheBacca reacted to a post in a topic: Custom Modpack Loads Vanilla Minecraft
-
Custom Modpack Loads Vanilla Minecraft
MarshTheBacca replied to MarshTheBacca's topic in Platform Pagoda
Thank you it worked :). -
Custom Modpack Loads Vanilla Minecraft
MarshTheBacca replied to MarshTheBacca's topic in Platform Pagoda
Thanks I’ll try it out when I get home. -
Yes I know, it's a common error, but I can't for the life of me figure out what I did wrong. When I look in my .technic/modpacks/(my modpack) folder, I notice that there's a folder surrounded by what seems to be vanilla minecraft files. The folder is the name of my modpack, and inside is: .bin which has "modpack.jar, which is just my universal forge file, and it is NOT .jar.jar or .zip or any funny business; and also the mods folder, which has around 35 mods all of which are up to date and compatible with each other. I recognised the issue, and I moved my "modpack.jar" into the vanilla file's .bin folder and moved all my mods into a mods folder in the previous directory. This then launched the modpack sucessfully with no issues. The issue is that these files shouldn't have been in their own subfolder named (my modpack). What is the fix? It's just a formatting error I think, but I'd like the public to be able to use my modpack without moving the files around. My modpack is called "MarshTheModpack" Thanks for any help -Marsh