Forge

Author

- Share

Spoiler

Server cannot dowload

Spoiler

Server stop dowload

Spoiler

The folder that suppose to contain the server with only the libaries folder which is empty

Spoiler

The vannila minecraft server

Spoiler

How can i post and how to find the folder that the installer create.

Link to comment

Share on other sites

Cadiboo

- Share

thanks that was pretty helpful, can you post the output log of the installer? it should be in the same folder as the installer is in (probably your downloads folder)

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)

Link to comment

Share on other sites

BeAm

Author

- Share

what is an out put log

Link to comment

Share on other sites

BeAm

Author

- Share

is it the log file

Link to comment

Share on other sites

BeAm

Author

- Share

What do i do with it

Do i put it in the server folder or somewhere else

Link to comment

Share on other sites

BeAm

Author

- Share

Can you show me the tutorial with pictures

Link to comment

Share on other sites

MDW01

- Share

Usually to fix this you to do download the Minecraft server jar manually for your version and put it in the folder. You may have to rename it to 'minecraft_server.1.12.2.jar' or whatever your version is so Forge is happy.

Link to comment

Share on other sites

BeAm

Author

- Share

So if i rename it it will automatically turn into a modded server

Link to comment

Share on other sites

MDW01

- Share

No, the error means that it could not download the vanilla server which it needs to run the forge server. You need to download the Minecraft server jar from Mojang for the version of Minecraft you want to use. Place it in the folder with the forge jar and rename it to 'minecraft_server.1.xx.x.jar' replace the 'x' with your version number. Then continue to launch the forge jar.

Link to comment

Share on other sites

BeAm

Author

- Share

and how do i get the forge jar

Link to comment

Share on other sites

DaemonUmbra

- Share

Run the installer again after renaming the vanilla server, the installer will take a quick look at the jar and skip the step that appears to be giving you issues.

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 ($$$)

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:
1. git init
2. 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
3. git fetch
4. git checkout --track origin/master
5. git stage *
6. git commit -m "[Your commit message]"
7. 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]

Link to comment

Share on other sites

BeAm

Author

- Share

forge-1.11.2-13.20.1.2588-installer.jar.log

thanks

Link to comment

Share on other sites

DaemonUmbra

- Share

Either your server jar is corrupted or you did not rename it:

10 hours ago, MDW01 said:

Place it in the folder with the forge jar and rename it to 'minecraft_server.1.xx.x.jar' replace the 'x' with your version number.

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 ($$$)

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.

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

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:
1. git init
2. 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
3. git fetch
4. git checkout --track origin/master
5. git stage *
6. git commit -m "[Your commit message]"
7. 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]

Link to comment

Share on other sites

BeAm

Author

- Share

Spoiler

still doesn't work

Link to comment

Share on other sites

DaemonUmbra

- Share

Posted June 7, 2018 (edited)

You are running the installer for 1.11.2...

Also, please activate Windows...

Edited June 7, 2018 by DaemonUmbra

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 ($$$)

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.

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

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:
1. git init
2. 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
3. git fetch
4. git checkout --track origin/master
5. git stage *
6. git commit -m "[Your commit message]"
7. 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]

Link to comment

Share on other sites

BeAm

Author

- Share

can this method be use for older version too

Link to comment

Share on other sites

DaemonUmbra

- Share

What version are you trying to run?
For 1.12.2: Get the 1.12.2 installer

For 1.11.2: Get a 1.11.2 vanilla server jar

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 ($$$)

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.

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

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:
1. git init
2. 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
3. git fetch
4. git checkout --track origin/master
5. git stage *
6. git commit -m "[Your commit message]"
7. 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]

Link to comment

Share on other sites

BeAm

Author

- Share

1.12.2

Link to comment

Share on other sites

DaemonUmbra

- Share

2 minutes ago, DaemonUmbra said:

Get the 1.12.2 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 ($$$)

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.

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

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:
1. git init
2. 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
3. git fetch
4. git checkout --track origin/master
5. git stage *
6. git commit -m "[Your commit message]"
7. 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]

Link to comment

Share on other sites

BeAm

Author

- Share

i got the installer already but when i install the server forge into the folder that has the server.jar it failed

Link to comment

Share on other sites

DaemonUmbra

- Share

Is it the same installer you got that log from?

Because that is a 1.11.2 version, each forge installer only installs one version, you cannot use a 1.11.2 installer to install a 1.12.2 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 ($$$)