Jump to content
Please read the rules and FAQ before starting a new topic
Currently supported: All versions

Loading stops when trying to load a texture pack on 1.14.2

Henrith

By Henrith
in Support & Bug Reports

 Share

Recommended Posts

Henrith Tree Puncher

Henrith

Posted
Posted

I'm able to launch and run forge 1.14.2 fine, but when I want to switch to a texture pack other than the default MC and MC Developers Pack, it will load, almost finish loading, and then stop at the spot as seen in this picture. The world itself loads fine using forge when I load in, but the moment I try to change the texture pack, it stops working. To remedy this issue, I have to switch to a vanilla 1.14 version, turn back to the default texture pack, and only then will forge load when I launch it. Otherwise, it runs into the same issue immediately after launch. 

 

I've got World Edit installed as a mod, but other than that, nothing else is active. 

 

Here is the debug log from my loading into a world and trying to change the texture pack using forge 1.14.2: 

Spoiler

[19:54:04] [main/INFO]: ModLauncher running: args [--username, Henrith, --version, 1.14.2-forge-26.0.63, --gameDir, C:\Users\Henry\AppData\Roaming\.minecraft, --assetsDir, C:\Users\Henry\AppData\Roaming\.minecraft\assets, --assetIndex, 1.14, --uuid, 851b3b3121384f1db55b258e34ebe8a8, --accessToken, ????????, --userType, mojang, --versionType, release, --launchTarget, fmlclient, --fml.forgeVersion, 26.0.63, --fml.mcVersion, 1.14.2, --fml.forgeGroup, net.minecraftforge, --fml.mcpVersion, 20190603.175704]
[19:54:04] [main/INFO]: ModLauncher starting: java version 1.8.0_51 by Oracle Corporation
[19:54:04] [main/INFO]: Added Lets Encrypt root certificates as additional trust
[19:54:05] [main/INFO]: Launching target 'fmlclient' with arguments [--version, 1.14.2-forge-26.0.63, --gameDir, C:\Users\Henry\AppData\Roaming\.minecraft, --assetsDir, C:\Users\Henry\AppData\Roaming\.minecraft\assets, --username, Henrith, --assetIndex, 1.14, --uuid, 851b3b3121384f1db55b258e34ebe8a8, --accessToken, ????????, --userType, mojang, --versionType, release]
[19:54:07] [Client thread/INFO]: Setting user: Henrith
[19:54:08] [Client thread/INFO]: Loading Network data for FML net version: FML2
[19:54:16] [Client thread/INFO]: LWJGL Version: 3.2.1 build 12
[19:54:18] [modloading-worker-1/INFO]: Forge mod loading, version 26.0.63, for MC 1.14.2 with MCP 20190603.175704
[19:54:18] [modloading-worker-1/INFO]: MinecraftForge v26.0.63 Initialized
[19:54:21] [Client thread/INFO]: Narrator library for x64 successfully loaded
[19:54:21] [Client thread/INFO]: Built for minecraft version 1.14.2
[19:54:29] [Thread-1/FATAL]: Forge config just got changed on the file system!
[19:54:29] [Forge Version Check/INFO]: [forge] Starting version check at https://files.minecraftforge.net/maven/net/minecraftforge/forge/promotions_slim.json
[19:54:29] [modloading-worker-3/INFO]: WorldEdit for Forge (version 7.0.1-beta-01;c97071c) is loaded
[19:54:29] [Forge Version Check/INFO]: [forge] Found status: BETA Current: 26.0.63 Target: 26.0.63
[19:54:30] [Server-Worker-1/WARN]: Codepoint '1ed0' declared multiple times in minecraft:textures/font/accented.png
[19:54:40] [Client thread/INFO]: OpenAL initialized.
[19:54:40] [Client thread/INFO]: Sound engine started
[19:54:40] [Client thread/INFO]: Created: 512x512 textures-atlas
[19:54:41] [Client thread/INFO]: Created: 256x256 textures/particle-atlas
[19:54:41] [Client thread/INFO]: Created: 256x256 textures/painting-atlas
[19:54:41] [Client thread/INFO]: Created: 128x128 textures/mob_effect-atlas
[19:55:02] [Client thread/WARN]: Ambiguity between arguments [teleport, destination] and [teleport, targets] with inputs: [Player, 0123, @e, dd12be42-52a9-4a91-a8a1-11c01849e498]
[19:55:02] [Client thread/WARN]: Ambiguity between arguments [teleport, location] and [teleport, destination] with inputs: [0.1 -0.5 .9, 0 0 0]
[19:55:02] [Client thread/WARN]: Ambiguity between arguments [teleport, location] and [teleport, targets] with inputs: [0.1 -0.5 .9, 0 0 0]
[19:55:02] [Client thread/WARN]: Ambiguity between arguments [teleport, targets] and [teleport, destination] with inputs: [Player, 0123, dd12be42-52a9-4a91-a8a1-11c01849e498]
[19:55:02] [Client thread/WARN]: Ambiguity between arguments [teleport, targets, location] and [teleport, targets, destination] with inputs: [0.1 -0.5 .9, 0 0 0]
[19:55:02] [Server thread/INFO]: Starting integrated minecraft server version 1.14.2
[19:55:02] [Server thread/INFO]: Generating keypair
[19:55:02] [Thread-1/FATAL]: Forge config just got changed on the file system!
[19:55:02] [Server thread/INFO]: Injecting existing registry data into this SERVER instance
[19:55:02] [Server thread/INFO]: Reloading ResourceManager: worldedit-forge-mc1.14.2-7.0.1-beta-01.jar, forge-1.14.2-26.0.63-universal.jar, Default
[19:55:04] [Server thread/INFO]: Loaded 6 recipes
[19:55:08] [Server thread/INFO]: Loaded 811 advancements
[19:55:08] [Server thread/INFO]: Preparing start region for dimension minecraft:overworld
[19:55:10] [Client thread/INFO]: Preparing spawn area: 0%
[19:55:10] [Client thread/INFO]: Preparing spawn area: 0%
[19:55:10] [Client thread/INFO]: Preparing spawn area: 0%
[19:55:10] [Client thread/INFO]: Preparing spawn area: 0%
[19:55:10] [Client thread/INFO]: Preparing spawn area: 0%
[19:55:11] [Client thread/INFO]: Preparing spawn area: 0%
[19:55:11] [Client thread/INFO]: Preparing spawn area: 0%
[19:55:13] [Client thread/INFO]: Preparing spawn area: 83%
[19:55:13] [Client thread/INFO]: Preparing spawn area: 83%
[19:55:13] [Client thread/INFO]: Preparing spawn area: 83%
[19:55:13] [Client thread/INFO]: Time elapsed: 4564 ms
[19:55:13] [Server thread/INFO]: Got request to register class com.sk89q.worldedit.forge.ForgePlatform with WorldEdit [com.sk89q.worldedit.extension.platform.PlatformManager@3e57e8fd]
[19:55:14] [Server thread/INFO]: Registering commands with com.sk89q.worldedit.forge.ForgePlatform
[19:55:14] [Server thread/INFO]: ThreadedAnvilChunkStorage (DIM1): All chunks are saved
[19:55:14] [Server thread/INFO]: ThreadedAnvilChunkStorage (DIM-1): All chunks are saved
[19:55:14] [Server thread/INFO]: Changing view distance to 12, from 10
[19:55:16] [Netty Local Client IO #0/INFO]: Connected to a modded server.
[19:55:16] [Server thread/INFO]: Henrith[local:E:e05fc052] logged in with entity id 92 at (-143.98194778057402, 78.0, 390.0528349326773)
[19:55:16] [Server thread/INFO]: Henrith joined the game
[19:55:19] [Server thread/INFO]: Saving and pausing game...
[19:55:19] [Client thread/INFO]: Loaded 121 advancements
[19:55:19] [Server thread/INFO]: Saving chunks for level 'New World'/minecraft:overworld
[19:55:21] [Server thread/WARN]: Can't keep up! Is the server overloaded? Running 3797ms or 75 ticks behind
[19:55:39] [Server thread/INFO]: Saving and pausing game...
[19:55:39] [Server thread/INFO]: Saving chunks for level 'New World'/minecraft:overworld
[19:55:44] [Client thread/INFO]: Reloading ResourceManager: forge-1.14.2-26.0.63-universal.jar, worldedit-forge-mc1.14.2-7.0.1-beta-01.jar, Default, jicklus-1-14-1561476411.zip
[19:55:44] [Thread-1/FATAL]: Forge config just got changed on the file system!
[19:55:44] [Server-Worker-14/WARN]: Codepoint '1ed0' declared multiple times in minecraft:textures/font/accented.png
[19:55:44] [Server-Worker-14/WARN]: Codepoint 'df' declared multiple times in minecraft:textures/font/nonlatin_european.png
[19:55:44] [Server-Worker-14/WARN]: Codepoint '406' declared multiple times in minecraft:textures/font/nonlatin_european.png
[19:55:45] [Server-Worker-11/WARN]: Exception loading blockstate definition: 'minecraft:blockstates/grass_path.json' missing model for variant: 'minecraft:grass_path#'
[19:58:07] [Client thread/INFO]: Stopping!
[19:58:07] [Server thread/INFO]: Henrith lost connection: Disconnected
[19:58:07] [Server thread/INFO]: Henrith left the game
[19:58:08] [Server thread/INFO]: Stopping singleplayer server as player logged out
[19:58:08] [Server thread/INFO]: Unregistering com.sk89q.worldedit.forge.ForgePlatform from WorldEdit
[19:58:08] [Server thread/INFO]: Stopping server
[19:58:08] [Server thread/INFO]: Saving players
[19:58:08] [Server thread/INFO]: Saving worlds
[19:58:08] [Server thread/INFO]: Saving chunks for level 'New World'/minecraft:overworld
[19:58:08] [Server thread/INFO]: ThreadedAnvilChunkStorage (New World (2)): All chunks are saved
[19:58:08] [Server thread/INFO]: ThreadedAnvilChunkStorage (New World (2)): All chunks are saved
 

 I've tried browsing this forum and others, but I can't find any solutions. I've turned off and uninstalled everything except for World Edit on forge and two of texture packs (Steven's Traditional and jicklus' are the ones that I have and use, both give the exact same result of not loading completely). Any and all help is much appreciated!

DaemonUmbra Reality Controller

DaemonUmbra

Posted
Posted

That looks like a latest.log rather than a debug.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]

 

Henrith Tree Puncher

Henrith

Posted
  • Author
Posted

My apologies! I believe I need some clarification then, please. The game never crashes, just stops loading. I have to close it manually. There is no crash report and I was under the impression that the latest.log of something that went wrong would contain the information that a debug.log would, as well as more. What do I need to do differently?

DaemonUmbra Reality Controller

DaemonUmbra

Posted
Posted

The debug.log contains much more info, if you could provide it that would help.

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]

 

Henrith Tree Puncher

Henrith

Posted
  • Author
Posted

Alright, I can't seem to find the debug.log file. I've looked all over, but in my logs file there is only dated logs and then latest.log. Am I doing something wrong?

DaemonUmbra Reality Controller

DaemonUmbra

Posted
Posted

Are you running Minecraft through the Twitch launcher?

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]

 

DaemonUmbra Reality Controller

DaemonUmbra

Posted
Posted

Could you provide a screenshot of your logs folder?

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]

 

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.

×
 Share
Go to topic listing

Announcements



×
×
  • Create New...

Important Information

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

  I accept