Jump to content

Recommended Posts

Posted

I need help

I recently created a minecraft forge server simple enough and it worked. The odd part is that i cant use any mods that add blocks/weapons and the like only ones like not enough items. the modded items appear in not enough items but the mods don't work. I have tried to find out if there is a different type of these mods (Aether 1.12.2 and twilight forest 1.12.2) but to no such luck is there any way that these would work? 

Posted

First off it really motivates everyone to help you when you make multiple posts and uses terminology such as ASAP, even if you're not trying to come across as important there are also other people who have questions and the people who answer them are donating their time to help them. To many of us, the most important person in the community is LexManos as he donates all of his time to make all of this possible. It also makes it very difficult to help you if you don't post any actual helpful information. Please post your logs don't ask us how there's this great thing called google.

  • Like 1
Posted (edited)
14 minutes ago, MDW01 said:

First off it really motivates everyone to help you when you make multiple posts and uses terminology such as ASAP, even if you're not trying to come across as important there are also other people who have questions and the people who answer them are donating their time to help them. To many of us, the most important person in the community is LexManos as he donates all of his time to make all of this possible. It also makes it very difficult to help you if you don't post any actual helpful information. Please post your logs don't ask us how there's this great thing called google.

Sorry it was an internet problem and i will not post twice again it was rushed and stupid on my part. to reply to the google part thats where it came up short as i was unable to find much that helped apologies for the two posts and If it was annoying just know that it was an accident on my part

 

is there any way to delete a thread as i feel guilty for posting two

Edited by SilverD4C
Posted

No, don't worry about it. I guess I snapped at you a bit so sorry about that I just had a long day working with a bunch of inconsiderate people. Hope you have a good rest of your day.

Posted
3 minutes ago, MDW01 said:

No, don't worry about it. I guess I snapped at you a bit so sorry about that I just had a long day working with a bunch of inconsiderate people. Hope you have a good rest of your day.

Thank you and again Apologies

Posted
3 hours ago, MDW01 said:

No, don't worry about it. I guess I snapped at you a bit so sorry about that I just had a long day working with a bunch of inconsiderate people. Hope you have a good rest of your day.

Do you know anything on how to fix this by any chance

Posted
9 hours ago, diesieben07 said:

 

Yes apologies here they are although google didnt help so i just pasted them in sorry if that was wrong I am extremely new at this

 

[16:36:50] [Server thread/INFO]: Starting minecraft server version 1.12.2
[16:36:50] [Server thread/WARN]: To start the server with more ram, launch it as "java -Xmx1024M -Xms1024M -jar minecraft_server.jar"
[16:36:50] [Server thread/INFO]: Loading properties
[16:36:50] [Server console handler/ERROR]: Exception handling console input
java.io.IOException: The handle is invalid
    at java.io.FileInputStream.readBytes(Native Method) ~[?:1.8.0_171]
    at java.io.FileInputStream.read(Unknown Source) ~[?:1.8.0_171]
    at java.io.BufferedInputStream.read1(Unknown Source) ~[?:1.8.0_171]
    at java.io.BufferedInputStream.read(Unknown Source) ~[?:1.8.0_171]
    at sun.nio.cs.StreamDecoder.readBytes(Unknown Source) ~[?:1.8.0_171]
    at sun.nio.cs.StreamDecoder.implRead(Unknown Source) ~[?:1.8.0_171]
    at sun.nio.cs.StreamDecoder.read(Unknown Source) ~[?:1.8.0_171]
    at java.io.InputStreamReader.read(Unknown Source) ~[?:1.8.0_171]
    at java.io.BufferedReader.fill(Unknown Source) ~[?:1.8.0_171]
    at java.io.BufferedReader.readLine(Unknown Source) ~[?:1.8.0_171]
    at java.io.BufferedReader.readLine(Unknown Source) ~[?:1.8.0_171]
    at nz$2.run(SourceFile:100) [minecraft_server.jar:?]
[16:36:50] [Server thread/INFO]: Default game type: SURVIVAL
[16:36:50] [Server thread/INFO]: Generating keypair
[16:36:50] [Server thread/INFO]: Starting Minecraft server on *:25565
[16:36:50] [Server thread/INFO]: Using default channel type
[16:36:51] [Server thread/WARN]: **** FAILED TO BIND TO PORT!
[16:36:51] [Server thread/WARN]: The exception was: java.net.BindException: Address already in use: bind
[16:36:51] [Server thread/WARN]: Perhaps a server is already running on that port?
[16:36:51] [Server thread/INFO]: Stopping server

 

[16:37:11] [Server thread/INFO]: Starting minecraft server version 1.12.2
[16:37:11] [Server thread/WARN]: To start the server with more ram, launch it as "java -Xmx1024M -Xms1024M -jar minecraft_server.jar"
[16:37:11] [Server thread/INFO]: Loading properties
[16:37:11] [Server console handler/ERROR]: Exception handling console input
java.io.IOException: The handle is invalid
    at java.io.FileInputStream.readBytes(Native Method) ~[?:1.8.0_171]
    at java.io.FileInputStream.read(Unknown Source) ~[?:1.8.0_171]
    at java.io.BufferedInputStream.read1(Unknown Source) ~[?:1.8.0_171]
    at java.io.BufferedInputStream.read(Unknown Source) ~[?:1.8.0_171]
    at sun.nio.cs.StreamDecoder.readBytes(Unknown Source) ~[?:1.8.0_171]
    at sun.nio.cs.StreamDecoder.implRead(Unknown Source) ~[?:1.8.0_171]
    at sun.nio.cs.StreamDecoder.read(Unknown Source) ~[?:1.8.0_171]
    at java.io.InputStreamReader.read(Unknown Source) ~[?:1.8.0_171]
    at java.io.BufferedReader.fill(Unknown Source) ~[?:1.8.0_171]
    at java.io.BufferedReader.readLine(Unknown Source) ~[?:1.8.0_171]
    at java.io.BufferedReader.readLine(Unknown Source) ~[?:1.8.0_171]
    at nz$2.run(SourceFile:100) [minecraft_server.jar:?]
[16:37:11] [Server thread/INFO]: Default game type: SURVIVAL
[16:37:11] [Server thread/INFO]: Generating keypair
[16:37:12] [Server thread/INFO]: Starting Minecraft server on *:25565
[16:37:12] [Server thread/INFO]: Using default channel type
[16:37:12] [Server thread/WARN]: **** FAILED TO BIND TO PORT!
[16:37:12] [Server thread/WARN]: The exception was: java.net.BindException: Address already in use: bind
[16:37:12] [Server thread/WARN]: Perhaps a server is already running on that port?
[16:37:12] [Server thread/INFO]: Stopping server

 

16:37:36] [Server thread/INFO]: Starting minecraft server version 1.12.2
[16:37:36] [Server thread/WARN]: To start the server with more ram, launch it as "java -Xmx1024M -Xms1024M -jar minecraft_server.jar"
[16:37:36] [Server thread/INFO]: Loading properties
[16:37:36] [Server console handler/ERROR]: Exception handling console input
java.io.IOException: The handle is invalid
    at java.io.FileInputStream.readBytes(Native Method) ~[?:1.8.0_171]
    at java.io.FileInputStream.read(Unknown Source) ~[?:1.8.0_171]
    at java.io.BufferedInputStream.read1(Unknown Source) ~[?:1.8.0_171]
    at java.io.BufferedInputStream.read(Unknown Source) ~[?:1.8.0_171]
    at sun.nio.cs.StreamDecoder.readBytes(Unknown Source) ~[?:1.8.0_171]
    at sun.nio.cs.StreamDecoder.implRead(Unknown Source) ~[?:1.8.0_171]
    at sun.nio.cs.StreamDecoder.read(Unknown Source) ~[?:1.8.0_171]
    at java.io.InputStreamReader.read(Unknown Source) ~[?:1.8.0_171]
    at java.io.BufferedReader.fill(Unknown Source) ~[?:1.8.0_171]
    at java.io.BufferedReader.readLine(Unknown Source) ~[?:1.8.0_171]
    at java.io.BufferedReader.readLine(Unknown Source) ~[?:1.8.0_171]
    at nz$2.run(SourceFile:100) [minecraft_server.jar:?]
[16:37:36] [Server thread/INFO]: Default game type: SURVIVAL
[16:37:36] [Server thread/INFO]: Generating keypair
[16:37:36] [Server thread/INFO]: Starting Minecraft server on *:25565
[16:37:36] [Server thread/INFO]: Using default channel type
[16:37:36] [Server thread/WARN]: **** FAILED TO BIND TO PORT!
[16:37:36] [Server thread/WARN]: The exception was: java.net.BindException: Address already in use: bind
[16:37:36] [Server thread/WARN]: Perhaps a server is already running on that port?
[16:37:36] [Server thread/INFO]: Stopping server
 

 

if i was supposed to do something else tell me the wonderful search engine at my disposal is extremely useless in this situation

 

 

Posted (edited)

That log is from a server that is trying to start up when another server(Or another program) is already running using the same port.

 

From the sound of it you have a vanilla server running when your forge server tries to start, so you are joining the vanilla server thinking it's the forge server.

 

Edit: It actually looks like you're starting a vanilla server rather than a forge one anyway

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

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
  1. Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
  2. Make a launcher profile targeting this version of Forge.
  3. 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).
  4. 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.

 

  1. Open a command prompt (CMD, Powershell, Terminal, etc).
  2. Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
  3. 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
  4. 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)
  5. Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]

 

Posted (edited)
15 minutes ago, DaemonUmbra said:

That log is from a server that is trying to start up when another server(Or another program) is already running using the same port.

From the sound of it you have a vanilla server running when your forge server tries to start, so you are joining the vanilla server thinking it's the forge server.

Well I’m not sure the server I load in has some mods that work such as not enough items so does have something running and the items from the mods appear in NEI but no luck spawning them in. I’m just using a simple forge provided server from the forge site. If it is vanilla somehow did the forge download not work 

 

I do have one more server log and I will post it to see if that’s still the case

 

[18:48:41] [Server thread/INFO]: Starting minecraft server version 1.12.2
[18:48:41] [Server thread/WARN]: To start the server with more ram, launch it as "java -Xmx1024M -Xms1024M -jar minecraft_server.jar"
[18:48:41] [Server console handler/ERROR]: Exception handling console input
java.io.IOException: The handle is invalid
    at java.io.FileInputStream.readBytes(Native Method) ~[?:1.8.0_171]
    at java.io.FileInputStream.read(Unknown Source) ~[?:1.8.0_171]
    at java.io.BufferedInputStream.read1(Unknown Source) ~[?:1.8.0_171]
    at java.io.BufferedInputStream.read(Unknown Source) ~[?:1.8.0_171]
    at sun.nio.cs.StreamDecoder.readBytes(Unknown Source) ~[?:1.8.0_171]
    at sun.nio.cs.StreamDecoder.implRead(Unknown Source) ~[?:1.8.0_171]
    at sun.nio.cs.StreamDecoder.read(Unknown Source) ~[?:1.8.0_171]
    at java.io.InputStreamReader.read(Unknown Source) ~[?:1.8.0_171]
    at java.io.BufferedReader.fill(Unknown Source) ~[?:1.8.0_171]
    at java.io.BufferedReader.readLine(Unknown Source) ~[?:1.8.0_171]
    at java.io.BufferedReader.readLine(Unknown Source) ~[?:1.8.0_171]
    at nz$2.run(SourceFile:100) [minecraft_server.jar:?]
[18:48:41] [Server thread/INFO]: Loading properties
[18:48:41] [Server thread/INFO]: Default game type: SURVIVAL
[18:48:41] [Server thread/INFO]: Generating keypair
[18:48:42] [Server thread/INFO]: Starting Minecraft server on *:25565
[18:48:42] [Server thread/INFO]: Using default channel type
[18:48:42] [Server thread/INFO]: Preparing level "world"
[18:48:42] [Server thread/INFO]: [STDERR]: java.util.zip.ZipException: Not in GZIP format
[18:48:42] [Server thread/INFO]: [STDERR]:     at java.util.zip.GZIPInputStream.readHeader(Unknown Source)
[18:48:42] [Server thread/INFO]: [STDERR]:     at java.util.zip.GZIPInputStream.<init>(Unknown Source)
[18:48:42] [Server thread/INFO]: [STDERR]:     at java.util.zip.GZIPInputStream.<init>(Unknown Source)
[18:48:42] [Server thread/INFO]: [STDERR]:     at gi.a(SourceFile:25)
[18:48:42] [Server thread/INFO]: [STDERR]:     at bfm.a(SourceFile:49)
[18:48:42] [Server thread/INFO]: [STDERR]:     at oo.b(SourceFile:145)
[18:48:42] [Server thread/INFO]: [STDERR]:     at net.minecraft.server.MinecraftServer.a(SourceFile:281)
[18:48:42] [Server thread/INFO]: [STDERR]:     at nz.j(SourceFile:233)
[18:48:42] [Server thread/INFO]: [STDERR]:     at net.minecraft.server.MinecraftServer.run(SourceFile:434)
[18:48:42] [Server thread/INFO]: [STDERR]:     at java.lang.Thread.run(Unknown Source)
[18:48:42] [Server thread/INFO]: Loaded 488 advancements
[18:48:43] [Server thread/INFO]: [STDERR]: java.util.zip.ZipException: Not in GZIP format
[18:48:43] [Server thread/INFO]: [STDERR]:     at java.util.zip.GZIPInputStream.readHeader(Unknown Source)
[18:48:43] [Server thread/INFO]: [STDERR]:     at java.util.zip.GZIPInputStream.<init>(Unknown Source)
[18:48:43] [Server thread/INFO]: [STDERR]:     at java.util.zip.GZIPInputStream.<init>(Unknown Source)
[18:48:43] [Server thread/INFO]: [STDERR]:     at gi.a(SourceFile:25)
[18:48:43] [Server thread/INFO]: [STDERR]:     at bfm.a(SourceFile:49)
[18:48:43] [Server thread/INFO]: [STDERR]:     at ok.b(SourceFile:72)
[18:48:43] [Server thread/INFO]: [STDERR]:     at net.minecraft.server.MinecraftServer.a(SourceFile:285)
[18:48:43] [Server thread/INFO]: [STDERR]:     at nz.j(SourceFile:233)
[18:48:43] [Server thread/INFO]: [STDERR]:     at net.minecraft.server.MinecraftServer.run(SourceFile:434)
[18:48:43] [Server thread/INFO]: [STDERR]:     at java.lang.Thread.run(Unknown Source)
[18:48:43] [Server thread/INFO]: [STDERR]: java.util.zip.ZipException: Not in GZIP format
[18:48:43] [Server thread/INFO]: [STDERR]:     at java.util.zip.GZIPInputStream.readHeader(Unknown Source)
[18:48:43] [Server thread/INFO]: [STDERR]:     at java.util.zip.GZIPInputStream.<init>(Unknown Source)
[18:48:43] [Server thread/INFO]: [STDERR]:     at java.util.zip.GZIPInputStream.<init>(Unknown Source)
[18:48:43] [Server thread/INFO]: [STDERR]:     at gi.a(SourceFile:25)
[18:48:43] [Server thread/INFO]: [STDERR]:     at bfm.a(SourceFile:49)
[18:48:43] [Server thread/INFO]: [STDERR]:     at ok.b(SourceFile:72)
[18:48:43] [Server thread/INFO]: [STDERR]:     at net.minecraft.server.MinecraftServer.a(SourceFile:285)
[18:48:43] [Server thread/INFO]: [STDERR]:     at nz.j(SourceFile:233)
[18:48:43] [Server thread/INFO]: [STDERR]:     at net.minecraft.server.MinecraftServer.run(SourceFile:434)
[18:48:43] [Server thread/INFO]: [STDERR]:     at java.lang.Thread.run(Unknown Source)
[18:48:43] [Server thread/INFO]: Preparing start region for level 0
[18:48:44] [Server thread/INFO]: Preparing spawn area: 12%
[18:48:45] [Server thread/INFO]: Preparing spawn area: 57%
[18:48:46] [Server thread/INFO]: Preparing spawn area: 99%
[18:48:46] [Server thread/INFO]: Done (3.434s)! For help, type "help" or "?"
[18:50:23] [User Authenticator #1/INFO]: UUID of player SilverD4C is 506c091d-3857-4cde-b12a-911dc2941056
[18:50:24] [Server thread/INFO]: SilverD4C[/25.81.12.216:50800] logged in with entity id 76 at (-233.55449806928576, 70.0, 137.03852276628945)
[18:50:24] [Server thread/INFO]: SilverD4C joined the game
[18:50:26] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 2797ms behind, skipping 55 tick(s)
[18:52:26] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 2296ms behind, skipping 45 tick(s)
[18:53:14] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 21781ms behind, skipping 435 tick(s)
[18:53:17] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 2437ms behind, skipping 48 tick(s)
[18:53:38] [Server thread/WARN]: SilverD4C moved too quickly! -10.386101240512517,-1.713744068098066,-0.02574107376858592
[18:53:44] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 4842ms behind, skipping 96 tick(s)
[18:54:03] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 5381ms behind, skipping 107 tick(s)
[18:54:08] [Server thread/INFO]: SilverD4C fell out of the world
[18:54:08] [Server thread/INFO]: [SilverD4C: Killed SilverD4C]
[19:03:26] [Server thread/INFO]: SilverD4C lost connection: Disconnected
[19:03:26] [Server thread/INFO]: SilverD4C left the game
[19:03:45] [Server thread/INFO]: Stopping server
[19:03:45] [Server thread/INFO]: Saving players
[19:03:45] [Server thread/INFO]: Saving worlds
[19:03:45] [Server thread/INFO]: Saving chunks for level 'world'/overworld
[19:03:45] [Server Shutdown Thread/INFO]: Stopping server
[19:03:45] [Server Shutdown Thread/INFO]: Saving players
[19:03:45] [Server Shutdown Thread/INFO]: Saving worlds
[19:03:45] [Server Shutdown Thread/INFO]: Saving chunks for level 'world'/overworld
[19:03:45] [Server Shutdown Thread/INFO]: Saving chunks for level 'world'/the_nether
[19:03:45] [Server Shutdown Thread/INFO]: Saving chunks for level 'world'/the_end
[19:03:45] [Server thread/INFO]: Saving chunks for level 'world'/the_nether
[19:03:45] [Server thread/INFO]: Saving chunks for level 'world'/the_end
 

Edited by SilverD4C
Posted (edited)

NEI is almost entirely clientside, it shows you the items that your client can use, not necessarily what's on the server.

What server jar are you launching, the forge one or the minecraft_server.1.12.2.jar?

Edit: I'm stupid and forgot there are no forge info messages in latest.log

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

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
  1. Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
  2. Make a launcher profile targeting this version of Forge.
  3. 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).
  4. 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.

 

  1. Open a command prompt (CMD, Powershell, Terminal, etc).
  2. Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
  3. 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
  4. 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)
  5. Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]

 

Posted

Where are you getting your mods?

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
  1. Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
  2. Make a launcher profile targeting this version of Forge.
  3. 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).
  4. 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.

 

  1. Open a command prompt (CMD, Powershell, Terminal, etc).
  2. Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
  3. 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
  4. 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)
  5. Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]

 

Posted

Are you starting your server through the command line or are you just double clicking it?

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
  1. Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
  2. Make a launcher profile targeting this version of Forge.
  3. 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).
  4. 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.

 

  1. Open a command prompt (CMD, Powershell, Terminal, etc).
  2. Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
  3. 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
  4. 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)
  5. Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]

 

Posted
3 minutes ago, DaemonUmbra said:

Are you starting your server through the command line or are you just double clicking it?

Double clicking is that the wrong way because the server works

Posted (edited)

It starts it but it doesn't mean it's launched with the correct options, create a file called launch.bat and put this in it:

java -jar forge.jar -Xmx3G -Xms3G
pause

Note that you will need to replace forge.jar with the name of the forge universal jar.

Double click the launch.bat and it will start the server with more RAM, which might make things a bit clearer.

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

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
  1. Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
  2. Make a launcher profile targeting this version of Forge.
  3. 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).
  4. 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.

 

  1. Open a command prompt (CMD, Powershell, Terminal, etc).
  2. Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
  3. 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
  4. 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)
  5. Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]

 

Posted
1 minute ago, DaemonUmbra said:

It starts it but it doesn't mean it's launched with the correct options, create a file called launch.bat and put this in it:


java -jar forge.jar -Xmx3G -Xms3G
pause

Note that you will need to replace forge.jar with the name of the forge universal jar.

Double click the launch.bat and it will start the server with more RAM, which might make things a bit clearer.

Thank you I’m currently away from my computer so when I get back I will check and Say if there is any problems

Posted
3 hours ago, DaemonUmbra said:

It starts it but it doesn't mean it's launched with the correct options, create a file called launch.bat and put this in it:


java -jar forge.jar -Xmx3G -Xms3G
pause

Note that you will need to replace forge.jar with the name of the forge universal jar.

Double click the launch.bat and it will start the server with more RAM, which might make things a bit clearer.

Alright so I did what you said to and the blocks are now in the creative menu but that's about as far as it goes some will spawn in for a split second and just disappear 

Posted

Can i get a fresh log?

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
  1. Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
  2. Make a launcher profile targeting this version of Forge.
  3. 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).
  4. 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.

 

  1. Open a command prompt (CMD, Powershell, Terminal, etc).
  2. Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
  3. 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
  4. 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)
  5. Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]

 

Posted
31 minutes ago, DaemonUmbra said:

Can i get a fresh log?

Here

 

[17:39:15] [Server thread/INFO]: Starting minecraft server version 1.12.2
[17:39:15] [Server thread/WARN]: To start the server with more ram, launch it as "java -Xmx1024M -Xms1024M -jar minecraft_server.jar"
[17:39:15] [Server thread/INFO]: Loading properties
[17:39:15] [Server console handler/ERROR]: Exception handling console input
java.io.IOException: The handle is invalid
    at java.io.FileInputStream.readBytes(Native Method) ~[?:1.8.0_171]
    at java.io.FileInputStream.read(Unknown Source) ~[?:1.8.0_171]
    at java.io.BufferedInputStream.read1(Unknown Source) ~[?:1.8.0_171]
    at java.io.BufferedInputStream.read(Unknown Source) ~[?:1.8.0_171]
    at sun.nio.cs.StreamDecoder.readBytes(Unknown Source) ~[?:1.8.0_171]
    at sun.nio.cs.StreamDecoder.implRead(Unknown Source) ~[?:1.8.0_171]
    at sun.nio.cs.StreamDecoder.read(Unknown Source) ~[?:1.8.0_171]
    at java.io.InputStreamReader.read(Unknown Source) ~[?:1.8.0_171]
    at java.io.BufferedReader.fill(Unknown Source) ~[?:1.8.0_171]
    at java.io.BufferedReader.readLine(Unknown Source) ~[?:1.8.0_171]
    at java.io.BufferedReader.readLine(Unknown Source) ~[?:1.8.0_171]
    at nz$2.run(SourceFile:100) [minecraft_server.jar:?]
[17:39:15] [Server thread/INFO]: Default game type: SURVIVAL
[17:39:15] [Server thread/INFO]: Generating keypair
[17:39:16] [Server thread/INFO]: Starting Minecraft server on *:25565
[17:39:16] [Server thread/INFO]: Using default channel type
[17:39:16] [Server thread/INFO]: Preparing level "world"
[17:39:17] [Server thread/INFO]: Loaded 488 advancements
[17:39:17] [Server thread/INFO]: Preparing start region for level 0
[17:39:18] [Server thread/INFO]: Preparing spawn area: 12%
[17:39:19] [Server thread/INFO]: Preparing spawn area: 52%
[17:39:20] [Server thread/INFO]: Preparing spawn area: 92%
[17:39:20] [Server thread/INFO]: Done (3.520s)! For help, type "help" or "?"
[17:39:30] [Server thread/INFO]: Unknown command. Try /help for a list of commands
[17:39:42] [Server thread/INFO]: Unknown command. Try /help for a list of commands
[17:40:06] [Server thread/INFO]: Stopping server
[17:40:06] [Server thread/INFO]: Saving players
[17:40:06] [Server thread/INFO]: Saving worlds
[17:40:06] [Server thread/INFO]: Saving chunks for level 'world'/overworld
[17:40:06] [Server Shutdown Thread/INFO]: Stopping server
[17:40:06] [Server Shutdown Thread/INFO]: Saving players
[17:40:06] [Server Shutdown Thread/INFO]: Saving worlds
[17:40:06] [Server Shutdown Thread/INFO]: Saving chunks for level 'world'/overworld
 

Posted (edited)

Are you opped on the server? If not then that is likely to be spawn protection preventing you from building or breaking blocks too close to spawn.

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

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
  1. Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
  2. Make a launcher profile targeting this version of Forge.
  3. 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).
  4. 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.

 

  1. Open a command prompt (CMD, Powershell, Terminal, etc).
  2. Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
  3. 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
  4. 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)
  5. Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]

 

Posted
2 minutes ago, DaemonUmbra said:

Are you opped on the server? If not then that is likely to be spawn protection preventing you from building or breaking blocks too close to spawn.

yes i am opped

Posted

could you put the fml-server-latest.log on pastebin and link to it here?

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
  1. Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
  2. Make a launcher profile targeting this version of Forge.
  3. 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).
  4. 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.

 

  1. Open a command prompt (CMD, Powershell, Terminal, etc).
  2. Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
  3. 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
  4. 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)
  5. Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]

 

Posted

That's not fml-server-latest, that's just latest.

Can you send a screenshot of your server's root folder (the one where the server jars are)?

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
  1. Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
  2. Make a launcher profile targeting this version of Forge.
  3. 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).
  4. 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.

 

  1. Open a command prompt (CMD, Powershell, Terminal, etc).
  2. Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
  3. 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
  4. 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)
  5. Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]

 

Posted
10 minutes ago, DaemonUmbra said:

That's not fml-server-latest, that's just latest.

Can you send a screenshot of your server's root folder (the one where the server jars are)?

I cant seem to send screenshots the uploads have failed and simple low qual phone pictures dont work either

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.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.