Tinkertool minecraft6/15/2023 ![]() To fix this issue you will have to manually weed out the erroneous mods. Remove all mods from the mods folder and put them on your desktop. Divide your mods into manageable subgroups of 5-7. Put the first group into the mods folder and run Minecraft. If you get the same error (same crashlog report with gui missing), then you have managed to locate at least one of the two problematic mods. Try to avoid other silly errors, such as not pairing up libraries with their respective mods, when making and testing groups. ![]() If there is no error, create a new folder in the mods folder called MODS GROUP 1 and put them in the folder. ![]() (Minecraft will still be able to run these mods, do not worry). Should you still have a problem, reply to this message. The reason that mod authors can't really prevent this error is because it requires two mods, usually ones far apart from each other, to combine and create this error. Post your installer log, found in the same place you ran the installer Please post logs using one of the following sites (Thank you Lumber Wizard for the list):ĭo NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads. This log will be called either installer.log or named the same as the installer but with. Windows hides file extensions by default so the installer may appear without the. log is added the log will appear with the. minecraft\logs.Ĭurse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch: Mojang Launcher: When using the Mojang launcher debug.log is found in. When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub. When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository.
0 Comments
Leave a Reply. |