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

Java.lang.ArrayIndexOutOfBoundsException causing Forge installer to not launch

Connor_

By Connor_
in Support & Bug Reports

 Share

Recommended Posts

Connor_ Tree Puncher

Connor_

Posted
Posted

Hello, I downloaded JRE 8, the latest one, and installed it on my system, but i kept having issues opening and or installing forge. First it gave me a SHA1 checksum error for a certain library, and now it just fails to open. Ive tried both the executable and jar, and launched it manually as well as via console and it fails each time. 

Log File
  

Exception in thread "main" java.lang.ExceptionInInitializerError
	at net.minecraftforge.installer.ClientInstall.getSponsorMessage(ClientInstall.java:401)
	at net.minecraftforge.installer.InstallerAction.getSponsorMessage(InstallerAction.java:60)
	at net.minecraftforge.installer.InstallerPanel.updateFilePath(InstallerPanel.java:334)
	at net.minecraftforge.installer.InstallerPanel.<init>(InstallerPanel.java:315)
	at net.minecraftforge.installer.SimpleInstaller.launchGui(SimpleInstaller.java:164)
	at net.minecraftforge.installer.SimpleInstaller.main(SimpleInstaller.java:51)
Caused by: java.lang.ArrayIndexOutOfBoundsException: 1
	at net.minecraftforge.installer.MirrorData.buildMirrorList(MirrorData.java:84)
	at net.minecraftforge.installer.MirrorData.<init>(MirrorData.java:63)
	at net.minecraftforge.installer.MirrorData.<clinit>(MirrorData.java:17)
	... 6 more

Console Output: 

C:\Users\[REDACTED]\Downloads>java forge-1.11.2-13.20.0.2260-installer.jar
Error: Could not find or load main class forge-1.11.2-13.20.0.2260-installer.jar

Is this an issue with my JRE or is this the installer causing the issue?
 

Link to comment
Share on other sites
Connor_ Tree Puncher

Connor_

Posted
  • Author
Posted

Did some testing in a VM, looks like the installer is broken on the website? I tried old JRE versions, specifically JRE- 8u51, which according to my old logs was the version that was running when I installed my old minecraft world with forge. This version HAS to work with the 1.11.2 installer. This error baffles me. 

Link to comment
Share on other sites
DaemonUmbra Reality Controller

DaemonUmbra

Posted
Posted

Really old Minecraft versions are no longer supported on this forum.

Please update to a modern version of Minecraft to receive support.

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]

 

Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Go to topic listing


×
×
  • Create New...

Important Information

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

  I accept