Posted November 10, 20186 yr Hello when i start the forge server i get this We appear to be missing one or more essential library files. You will need to add them to your server before FML and Forge will run successfully.java.lang.ClassNotFoundException: net.minecraft.launchwrapper.Launch at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(Unknown Source) at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(Unknown Source) at java.base/java.lang.ClassLoader.loadClass(Unknown Source) at java.base/java.lang.Class.forName0(Native Method) at java.base/java.lang.Class.forName(Unknown Source) at net.minecraftforge.fml.relauncher.ServerLaunchWrapper.run(ServerLaunchWrapper.java:44) at net.minecraftforge.fml.relauncher.ServerLaunchWrapper.main(ServerLaunchWrapper.java:31) i use forge 1.12. i dont know how to fix this
November 10, 20186 yr You appear to be missing a library, how did you install the server? This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy. As the most common issue I feel I should put this outside the main bulk: The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge. If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan. For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety. Spoiler Logs (Most issues require logs to diagnose): Spoiler Please post logs using one of the following sites (Thank you Lumber Wizard for the list): https://gist.github.com/: 100MB Requires member (Free) https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$) https://hastebin.com/: 400KB Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads. What to provide: ...for Crashes and Runtime issues: Minecraft 1.14.4 and newer: Post debug.log Older versions: Please update... ...for Installer Issues: Post your installer log, found in the same place you ran the installer This log will be called either installer.log or named the same as the installer but with .log on the end Note for Windows users: Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension Where to get it: Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs. Curse/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: Spoiler Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge) Make a launcher profile targeting this version of Forge. Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it). Now launch the pack through that profile and follow the "Mojang Launcher" instructions above. Video: Spoiler or alternately, Fallback ("No logs are generated"): If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft Server Not Starting: Spoiler If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output. Reporting Illegal/Inappropriate Adfocus Ads: Spoiler Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad. Lex will need the Ad ID contained in that URL to report it to Adfocus' support team. Posting your mod as a GitHub Repo: Spoiler 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. Open a command prompt (CMD, Powershell, Terminal, etc). Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in). Run the following commands: git init git remote add origin [Your Repository's URL] In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git git fetch git checkout --track origin/master git stage * git commit -m "[Your commit message]" git push Navigate to GitHub and you should now see most of the files. note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from) Now you can share your GitHub link with those who you are asking for help. [Workaround line, please ignore]
November 10, 20186 yr Author i installed with the windows installer normaly Edited November 10, 20186 yr by blackhammer34
November 10, 20186 yr Try the non-windows installer This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy. As the most common issue I feel I should put this outside the main bulk: The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge. If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan. For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety. Spoiler Logs (Most issues require logs to diagnose): Spoiler Please post logs using one of the following sites (Thank you Lumber Wizard for the list): https://gist.github.com/: 100MB Requires member (Free) https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$) https://hastebin.com/: 400KB Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads. What to provide: ...for Crashes and Runtime issues: Minecraft 1.14.4 and newer: Post debug.log Older versions: Please update... ...for Installer Issues: Post your installer log, found in the same place you ran the installer This log will be called either installer.log or named the same as the installer but with .log on the end Note for Windows users: Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension Where to get it: Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs. Curse/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: Spoiler Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge) Make a launcher profile targeting this version of Forge. Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it). Now launch the pack through that profile and follow the "Mojang Launcher" instructions above. Video: Spoiler or alternately, Fallback ("No logs are generated"): If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft Server Not Starting: Spoiler If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output. Reporting Illegal/Inappropriate Adfocus Ads: Spoiler Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad. Lex will need the Ad ID contained in that URL to report it to Adfocus' support team. Posting your mod as a GitHub Repo: Spoiler 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. Open a command prompt (CMD, Powershell, Terminal, etc). Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in). Run the following commands: git init git remote add origin [Your Repository's URL] In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git git fetch git checkout --track origin/master git stage * git commit -m "[Your commit message]" git push Navigate to GitHub and you should now see most of the files. note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from) Now you can share your GitHub link with those who you are asking for help. [Workaround line, please ignore]
November 10, 20186 yr Author i installed reinstalled java 8 32 & 64 tried the non windows installer and it said successfully installed and the forge universal content copyed to the server jar and started with the batch file and so gettin the error that one ore more libary files is missing Edited November 10, 20186 yr by blackhammer34
November 11, 20186 yr Try deleting the libraries folder and running the installer again. This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy. As the most common issue I feel I should put this outside the main bulk: The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge. If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan. For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety. Spoiler Logs (Most issues require logs to diagnose): Spoiler Please post logs using one of the following sites (Thank you Lumber Wizard for the list): https://gist.github.com/: 100MB Requires member (Free) https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$) https://hastebin.com/: 400KB Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads. What to provide: ...for Crashes and Runtime issues: Minecraft 1.14.4 and newer: Post debug.log Older versions: Please update... ...for Installer Issues: Post your installer log, found in the same place you ran the installer This log will be called either installer.log or named the same as the installer but with .log on the end Note for Windows users: Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension Where to get it: Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs. Curse/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: Spoiler Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge) Make a launcher profile targeting this version of Forge. Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it). Now launch the pack through that profile and follow the "Mojang Launcher" instructions above. Video: Spoiler or alternately, Fallback ("No logs are generated"): If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft Server Not Starting: Spoiler If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output. Reporting Illegal/Inappropriate Adfocus Ads: Spoiler Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad. Lex will need the Ad ID contained in that URL to report it to Adfocus' support team. Posting your mod as a GitHub Repo: Spoiler 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. Open a command prompt (CMD, Powershell, Terminal, etc). Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in). Run the following commands: git init git remote add origin [Your Repository's URL] In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git git fetch git checkout --track origin/master git stage * git commit -m "[Your commit message]" git push Navigate to GitHub and you should now see most of the files. note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from) Now you can share your GitHub link with those who you are asking for help. [Workaround line, please ignore]
November 11, 20186 yr Post updated logs About Me Spoiler My Discord - Cadiboo#8887 My Website - Cadiboo.github.io My Mods - Cadiboo.github.io/projects My Tutorials - Cadiboo.github.io/tutorials Versions below 1.14.4 are no longer supported on this forum. Use the latest version to receive support. When asking support remember to include all relevant log files (logs are found in .minecraft/logs/), code if applicable and screenshots if possible. Only download mods from trusted sites like CurseForge (minecraft.curseforge.com). A list of bad sites can be found here, with more information available at stopmodreposts.org Edit your own signature at www.minecraftforge.net/forum/settings/signature/ (Make sure to check its compatibility with the Dark Theme)
November 11, 20186 yr Author here the installer log Considering library net.minecraftforge:forge:1.12-14.21.1.2387: Not Downloading {Wrong Side} Considering library net.minecraft:launchwrapper:1.12 Downloading library net.minecraft:launchwrapper:1.12 Trying unpacked library net.minecraft:launchwrapper:1.12 Considering library org.ow2.asm:asm-all:5.2 Downloading library org.ow2.asm:asm-all:5.2 Trying unpacked library org.ow2.asm:asm-all:5.2 Considering library jline:jline:2.13 Downloading library jline:jline:2.13 Trying unpacked library jline:jline:2.13 Considering library com.typesafe.akka:akka-actor_2.11:2.3.3 Downloading library com.typesafe.akka:akka-actor_2.11:2.3.3 Unpacking packed file akka-actor_2.11-2.3.3.jar.pack.xz Signed Checksum Length: 140942 Total Length: 2606968 Temp File: C:\Users\etien\AppData\Local\Temp\art2953899384542440794.pack Successfully unpacked packed file akka-actor_2.11-2.3.3.jar.pack.xz Checking "C:\Users\etien\Desktop\forge temp\libraries\com\typesafe\akka\akka-actor_2.11\2.3.3\akka-actor_2.11-2.3.3.jar" internal checksums checksums.sha1 validated successfully Jar contents validated successfully Considering library com.typesafe:config:1.2.1 Downloading library com.typesafe:config:1.2.1 Unpacking packed file config-1.2.1.jar.pack.xz Signed Checksum Length: 12246 Total Length: 111476 Temp File: C:\Users\etien\AppData\Local\Temp\art9159153345966076438.pack Successfully unpacked packed file config-1.2.1.jar.pack.xz Checking "C:\Users\etien\Desktop\forge temp\libraries\com\typesafe\config\1.2.1\config-1.2.1.jar" internal checksums checksums.sha1 validated successfully Jar contents validated successfully Considering library org.scala-lang:scala-actors-migration_2.11:1.1.0 Downloading library org.scala-lang:scala-actors-migration_2.11:1.1.0 Unpacking packed file scala-actors-migration_2.11-1.1.0.jar.pack.xz Signed Checksum Length: 3311 Total Length: 52481 Temp File: C:\Users\etien\AppData\Local\Temp\art2878725108772176856.pack Successfully unpacked packed file scala-actors-migration_2.11-1.1.0.jar.pack.xz Checking "C:\Users\etien\Desktop\forge temp\libraries\org\scala-lang\scala-actors-migration_2.11\1.1.0\scala-actors-migration_2.11-1.1.0.jar" internal checksums checksums.sha1 validated successfully Jar contents validated successfully Considering library org.scala-lang:scala-compiler:2.11.1 Downloading library org.scala-lang:scala-compiler:2.11.1 Unpacking packed file scala-compiler-2.11.1.jar.pack.xz Signed Checksum Length: 942120 Total Length: 9183051 Temp File: C:\Users\etien\AppData\Local\Temp\art4767305713684619804.pack Successfully unpacked packed file scala-compiler-2.11.1.jar.pack.xz Checking "C:\Users\etien\Desktop\forge temp\libraries\org\scala-lang\scala-compiler\2.11.1\scala-compiler-2.11.1.jar" internal checksums checksums.sha1 validated successfully Jar contents validated successfully Considering library org.scala-lang.plugins:scala-continuations-library_2.11:1.0.2 Downloading library org.scala-lang.plugins:scala-continuations-library_2.11:1.0.2 Unpacking packed file scala-continuations-library_2.11-1.0.2.jar.pack.xz Signed Checksum Length: 2416 Total Length: 18871 Temp File: C:\Users\etien\AppData\Local\Temp\art8214273586910098923.pack Successfully unpacked packed file scala-continuations-library_2.11-1.0.2.jar.pack.xz Checking "C:\Users\etien\Desktop\forge temp\libraries\org\scala-lang\plugins\scala-continuations-library_2.11\1.0.2\scala-continuations-library_2.11-1.0.2.jar" internal checksums checksums.sha1 validated successfully Jar contents validated successfully Considering library org.scala-lang.plugins:scala-continuations-plugin_2.11.1:1.0.2 Downloading library org.scala-lang.plugins:scala-continuations-plugin_2.11.1:1.0.2 Unpacking packed file scala-continuations-plugin_2.11.1-1.0.2.jar.pack.xz Signed Checksum Length: 16815 Total Length: 139418 Temp File: C:\Users\etien\AppData\Local\Temp\art7357035588809326429.pack Successfully unpacked packed file scala-continuations-plugin_2.11.1-1.0.2.jar.pack.xz Checking "C:\Users\etien\Desktop\forge temp\libraries\org\scala-lang\plugins\scala-continuations-plugin_2.11.1\1.0.2\scala-continuations-plugin_2.11.1-1.0.2.jar" internal checksums checksums.sha1 validated successfully Jar contents validated successfully Considering library org.scala-lang:scala-library:2.11.1 Downloading library org.scala-lang:scala-library:2.11.1 Unpacking packed file scala-library-2.11.1.jar.pack.xz Signed Checksum Length: 341368 Total Length: 5984083 Temp File: C:\Users\etien\AppData\Local\Temp\art7427433546647393969.pack Successfully unpacked packed file scala-library-2.11.1.jar.pack.xz Checking "C:\Users\etien\Desktop\forge temp\libraries\org\scala-lang\scala-library\2.11.1\scala-library-2.11.1.jar" internal checksums checksums.sha1 validated successfully Jar contents validated successfully Considering library org.scala-lang:scala-parser-combinators_2.11:1.0.1 Downloading library org.scala-lang:scala-parser-combinators_2.11:1.0.1 Unpacking packed file scala-parser-combinators_2.11-1.0.1.jar.pack.xz Signed Checksum Length: 37614 Total Length: 273457 Temp File: C:\Users\etien\AppData\Local\Temp\art5242763490997925027.pack Successfully unpacked packed file scala-parser-combinators_2.11-1.0.1.jar.pack.xz Checking "C:\Users\etien\Desktop\forge temp\libraries\org\scala-lang\scala-parser-combinators_2.11\1.0.1\scala-parser-combinators_2.11-1.0.1.jar" internal checksums checksums.sha1 validated successfully Jar contents validated successfully Considering library org.scala-lang:scala-reflect:2.11.1 Downloading library org.scala-lang:scala-reflect:2.11.1 Unpacking packed file scala-reflect-2.11.1.jar.pack.xz Signed Checksum Length: 291610 Total Length: 3217021 Temp File: C:\Users\etien\AppData\Local\Temp\art5659656978847351840.pack Successfully unpacked packed file scala-reflect-2.11.1.jar.pack.xz Checking "C:\Users\etien\Desktop\forge temp\libraries\org\scala-lang\scala-reflect\2.11.1\scala-reflect-2.11.1.jar" internal checksums checksums.sha1 validated successfully Jar contents validated successfully Considering library org.scala-lang:scala-swing_2.11:1.0.1 Downloading library org.scala-lang:scala-swing_2.11:1.0.1 Unpacking packed file scala-swing_2.11-1.0.1.jar.pack.xz Signed Checksum Length: 39019 Total Length: 888907 Temp File: C:\Users\etien\AppData\Local\Temp\art4418883718718815500.pack Successfully unpacked packed file scala-swing_2.11-1.0.1.jar.pack.xz Checking "C:\Users\etien\Desktop\forge temp\libraries\org\scala-lang\scala-swing_2.11\1.0.1\scala-swing_2.11-1.0.1.jar" internal checksums checksums.sha1 validated successfully Jar contents validated successfully Considering library org.scala-lang:scala-xml_2.11:1.0.2 Downloading library org.scala-lang:scala-xml_2.11:1.0.2 Unpacking packed file scala-xml_2.11-1.0.2.jar.pack.xz Signed Checksum Length: 35380 Total Length: 739509 Temp File: C:\Users\etien\AppData\Local\Temp\art1189778993849433502.pack Successfully unpacked packed file scala-xml_2.11-1.0.2.jar.pack.xz Checking "C:\Users\etien\Desktop\forge temp\libraries\org\scala-lang\scala-xml_2.11\1.0.2\scala-xml_2.11-1.0.2.jar" internal checksums checksums.sha1 validated successfully Jar contents validated successfully Considering library lzma:lzma:0.0.1 Downloading library lzma:lzma:0.0.1 Trying unpacked library lzma:lzma:0.0.1 Considering library net.sf.jopt-simple:jopt-simple:4.6 Downloading library net.sf.jopt-simple:jopt-simple:4.6 Trying unpacked library net.sf.jopt-simple:jopt-simple:4.6 Considering library java3d:vecmath:1.5.2 Downloading library java3d:vecmath:1.5.2 Trying unpacked library java3d:vecmath:1.5.2 Considering library net.sf.trove4j:trove4j:3.0.3 Downloading library net.sf.trove4j:trove4j:3.0.3 Trying unpacked library net.sf.trove4j:trove4j:3.0.3 Considering library net.minecraftforge:MercuriusUpdater:1.12 Downloading library net.minecraftforge:MercuriusUpdater:1.12 Trying unpacked library net.minecraftforge:MercuriusUpdater:1.12 Saving optional modlist to: C:\Users\etien\Desktop\forge temp\mods\mod_list.json Edited November 11, 20186 yr by blackhammer34
November 14, 20186 yr You should try using the most recent Recomended Forge (2768) About Me Spoiler My Discord - Cadiboo#8887 My Website - Cadiboo.github.io My Mods - Cadiboo.github.io/projects My Tutorials - Cadiboo.github.io/tutorials Versions below 1.14.4 are no longer supported on this forum. Use the latest version to receive support. When asking support remember to include all relevant log files (logs are found in .minecraft/logs/), code if applicable and screenshots if possible. Only download mods from trusted sites like CurseForge (minecraft.curseforge.com). A list of bad sites can be found here, with more information available at stopmodreposts.org Edit your own signature at www.minecraftforge.net/forum/settings/signature/ (Make sure to check its compatibility with the Dark Theme)
November 15, 20186 yr No no no, do not modify the vanilla jar. Just run the Forge jar like you would the vanilla server jar, it will load the vanilla jar into memory and do all of its changes in RAM before the server starts. This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy. As the most common issue I feel I should put this outside the main bulk: The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge. If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan. For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety. Spoiler Logs (Most issues require logs to diagnose): Spoiler Please post logs using one of the following sites (Thank you Lumber Wizard for the list): https://gist.github.com/: 100MB Requires member (Free) https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$) https://hastebin.com/: 400KB Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads. What to provide: ...for Crashes and Runtime issues: Minecraft 1.14.4 and newer: Post debug.log Older versions: Please update... ...for Installer Issues: Post your installer log, found in the same place you ran the installer This log will be called either installer.log or named the same as the installer but with .log on the end Note for Windows users: Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension Where to get it: Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs. Curse/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: Spoiler Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge) Make a launcher profile targeting this version of Forge. Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it). Now launch the pack through that profile and follow the "Mojang Launcher" instructions above. Video: Spoiler or alternately, Fallback ("No logs are generated"): If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft Server Not Starting: Spoiler If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output. Reporting Illegal/Inappropriate Adfocus Ads: Spoiler Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad. Lex will need the Ad ID contained in that URL to report it to Adfocus' support team. Posting your mod as a GitHub Repo: Spoiler 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. Open a command prompt (CMD, Powershell, Terminal, etc). Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in). Run the following commands: git init git remote add origin [Your Repository's URL] In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git git fetch git checkout --track origin/master git stage * git commit -m "[Your commit message]" git push Navigate to GitHub and you should now see most of the files. note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from) Now you can share your GitHub link with those who you are asking for help. [Workaround line, please ignore]
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.