![]() gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from) Note that it is intentional that some are not synced with GitHub and this is done with the (hidden). ![]() Navigate to GitHub and you should now see most of the files. In the case of GitHub it should look like: /.git Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in). Open a command prompt (CMD, Powershell, Terminal, etc). 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. 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 most convenient way to do this is via GitHub or another source control hub. 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. 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. ![]() log is added the log will appear with the. Windows hides file extensions by default so the installer may appear without the. This log will be called either installer.log or named the same as the installer but with. Post your installer log, found in the same place you ran the installer Don't be sad, have a hug! GradleStart.java:25)Ī detailed walkthrough of the error, its code path and all known details is as follows:Īt .Maps.uniqueIndex( Maps.java:1385)Īt .Maps.uniqueIndex( Maps.java:1341)Īt .Loader.identifyMods( Loader.java:427)Īt .Loader.loadMods( Loader.java:566)Īt .FMLClientHandler.beginMinecraftLoading( FMLClientHandler.java:232)Īt .init( Minecraft.java:513)Īt .run( Minecraft.java:421)Īt .Main.main( Main.java:118)Īt 0(Native Method)Īt ( NativeMethodAccessorImpl.java:62)Īt ( DelegatingMethodAccessorImpl.java:43)Īt .invoke( Method.java:498)Īt .launch( Launch.java:135)Īt .main( Launch.java:28)Īt .launch( GradleStartCommon.java:97)Īt .launch( GradleStartCommon.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. Java VM Version: OpenJDK 64-Bit Server VM (mixed mode), You'll probably notice that it fails when the Game Launches, it builds a little, then crashes and then is called "failed build".Ĭontact me if needed, for now i'm going to sleep, should be back around 12:00 PM to 1:30 PM (Canada Time)īuild info: MCreator 207, 1.12.2, 64-bit, 16343 MB, Windows 10, JVM 1.8.0_232, JAVA_HOME: C:\Program Files\Pylo\MCreator\jdk I added some of my personnal mods to the MCreatorWorkspace/terraria/run/mods/ but those worked way before so that's not it. (should not be the problem, i'm fairly certain.) I edited some kind of procedures (3 of them) that SHOULD work but didn't test right after. I changed the Name, description and author of the mod. I recently edited "mod version : 1.0.0" to "mod version 1.2.3"
0 Comments
Leave a Reply. |