MokahTGS Posted January 5, 2019 Posted January 5, 2019 Using the Twitch Launcher and updating a profile to any Forge version higher than 2796 will load a 1.13.2 instance of Minecraft. Not sure what's going on but I can't seem to upgrade my forge version any further. Quote
DaemonUmbra Posted January 5, 2019 Posted January 5, 2019 I don't see this issue on my end, and even if I did it would be a Twitch issue. How are you updating the profile? Quote This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy. As the most common issue I feel I should put this outside the main bulk: The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge. If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan. For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety. Spoiler Logs (Most issues require logs to diagnose): Spoiler Please post logs using one of the following sites (Thank you Lumber Wizard for the list): https://gist.github.com/: 100MB Requires member (Free) https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$) https://hastebin.com/: 400KB Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads. What to provide: ...for Crashes and Runtime issues: Minecraft 1.14.4 and newer: Post debug.log Older versions: Please update... ...for Installer Issues: Post your installer log, found in the same place you ran the installer This log will be called either installer.log or named the same as the installer but with .log on the end Note for Windows users: Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension Where to get it: Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs. Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch: Spoiler Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge) Make a launcher profile targeting this version of Forge. Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it). Now launch the pack through that profile and follow the "Mojang Launcher" instructions above. Video: Spoiler or alternately, Fallback ("No logs are generated"): If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft Server Not Starting: Spoiler If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output. Reporting Illegal/Inappropriate Adfocus Ads: Spoiler Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad. Lex will need the Ad ID contained in that URL to report it to Adfocus' support team. Posting your mod as a GitHub Repo: Spoiler When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub. When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository. Open a command prompt (CMD, Powershell, Terminal, etc). Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in). Run the following commands: git init git remote add origin [Your Repository's URL] In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git git fetch git checkout --track origin/master git stage * git commit -m "[Your commit message]" git push Navigate to GitHub and you should now see most of the files. note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from) Now you can share your GitHub link with those who you are asking for help. [Workaround line, please ignore]
MokahTGS Posted January 5, 2019 Author Posted January 5, 2019 Through the Twitch Launcher. Agreed that I don't think it's a Forge issue exactly, but I was curious as to how that launcher gets what version to use. Is there some file that was uploaded incorrectly? Quote
TensorTime Posted January 5, 2019 Posted January 5, 2019 (edited) I've seen this issue on various machines as well. Create custom profile, pick any version above 2796 for 1.12.2 and twitch does not correctly install the requested forge version and so the launcher defaults to 1.13.2 instead of getting an assigned profile. It is true for all versions above 2796 so not sure if it's something specifically a Twitch bug or if there is something wrong with the way the versions have been uploaded to Twitch/Curse. This is with the Jar launcher. Testing native now (though I never use it). Ok confirmed it's only the Jar launcher experiencing the problem for me. The Native Launcher works just fine. Edited January 5, 2019 by TensorTime Quote
LexManos Posted January 5, 2019 Posted January 5, 2019 If this is the case, than this seems to be a issue on Twitches end, not ours. We provide the metadata in our jsons and installer data. It's on them to parse it correctly. Quote I do Forge for free, however the servers to run it arn't free, so anything is appreciated. Consider supporting the team on Patreon
TensorTime Posted January 5, 2019 Posted January 5, 2019 23 minutes ago, LexManos said: If this is the case, than this seems to be a issue on Twitches end, not ours. We provide the metadata in our jsons and installer data. It's on them to parse it correctly. I don't disagree it's on them but I would think that considering it's your mod/framework they are not distributing correctly, and they are the primary resource for most users, that you would be interested in determining why they are screwing it up Up to you I guess, it's not skin off my back. I'm just letting you know that there is an issue with how many people and pack devs use forge these days. --tensor Quote
LexManos Posted January 5, 2019 Posted January 5, 2019 You should let them {a 3rd party company that makes tons of money, has several developers on staff for this type of thing, and who's thing is broken} know not us {a single/two person setup who doesn't make tons of money and isn't the one the broke things}. Quote I do Forge for free, however the servers to run it arn't free, so anything is appreciated. Consider supporting the team on Patreon
Telshin Posted January 6, 2019 Posted January 6, 2019 Forge Versions above 2796 are working again in the Desktop App. If you run into issue, please do the following: Open your profile Click the `...` menu in the upper right hand corner Click on 'Repair Minecraft' If the steps above do not work, please let us know by filing a ticket on https://support.curse.com/hc/en-us Quote
Recommended Posts
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.