awsomeaassasin Posted April 7, 2014 Posted April 7, 2014 I have recently noticed a recurring problem. I've seen this problem in other people's posts and experienced it in my own mod pack. When I press play on my own custom mod pack, it loads and then closes like the client is about to start and then opens again and the client never loads. I have also had this error with BareBonesPack, which I use to get config files. As soon as I put the files in the pack this same error happens. Is there anyway to fix this?
Discord Moderator plowmanplow Posted April 8, 2014 Discord Moderator Posted April 8, 2014 This is because your pack is invalid. The BareBonesPack (my pack) has no mods in it. It always works. What will make it not work (what you identify as "never loads") is putting in mods that aren't compatible or not configured properly. It is the job of all modpack creators to methodically assemble the desired mods and supporting files in order to achieve a working modpack. The BareBonesPack is just one tool which can be used to start the process. Check your logs. That's what I have attempted to relay in my previous posts to you: Also, you already had a thread started. It is much easier to continue working on that than to start a whole new thread and lose all that contextual information in the old one. As for your pack development, one does not simply collect mods and files from other packs and random locations on the internet. One must figure out what mods one wishes to include and proceed to retrieve those mods and the proper installation procedures from the authors' preferred distribution channels. If you want to continue debugging your modpack I recommend continuing your previous thread. Make sure you include or reference current links to your pack page and downloads.
awsomeaassasin Posted April 9, 2014 Author Posted April 9, 2014 So what you mean is to put links to the modpack page? My pack is hidden, and I plan to unhide it when it's done.
Discord Moderator plowmanplow Posted April 9, 2014 Discord Moderator Posted April 9, 2014 If you don't include at least the pack URL (what you would paste into the launcher) it is much harder to know for certain where the problem lies. Without being able to examine the download URL it is impossible to know exactly what you might have in your pack (lots of folks put in extraneous/incorrect stuff). Without log files it is impossible to have the slightest clue what the problem might be. Anecdotal statements and vague descriptions are not helpful. Just the facts, ma'am.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now