bug - minion stuck at splash screen
 

I had previously loaded minion and it worked for several months, but after a break from the game, I returned to find it not working. I have uninstalled and reinstalled severl times, each time, after getting to "finish" of the installation, it stalls out at the splash screen.

I have attached the minion.xml and minion0.log.

Thanks for any help. I'm missing my addons!

I just want to confirm, it stalls at the splash screen with the Minion logo right? Not the Loading... screen? The log you provide suggests that it actually gets to the Loading... screen on 2014-09-07T19:46:27?

What security software do you have installed? There are some that try to run Minion in a sandbox and since Minion already runs in a sandbox via the JVM it doesn't work.

If you're up to it and have Minion installed in the default location open a windows Command Prompt and run the following command:

Java -jar C:\Users\Kayhleen\AppData\Local\Minion\app\Minion-jfx.jar

If it errors out paste the error here.

Try removing your minion.xml and restarting Minion. Although it looks like this might have already happened.

It is the splash screen with the minion logo.

I am using Avast.

I typed in the command into the Command Prompt as you suggested. The splash screen went away this time but did nothing else.

I uploaded the current log files.

Looking closer at your log the java.library.path is being overridden for Minion. It should be pointing to C:\Users\your username\AppData\Local\Minion\app\ and some reason its set to C:\Program Files (x86)\Java\jre7\bin

Do you have anything that could be overriding our setting? I'll bring this up to our java programmer tomorrow to see what he thinks could cause this to happen.

Thanks for all the information. Hopefully we can figure this out soon. :)

I want to confirm that the logs you posted in your original post was from double clicking the Minion icon. Right? You weren't trying to run the Minion-jfx.jar directly for the first log you posted?

I don't know of any programs that would be overriding your settings.

Yes, the first post was not from running the jar file directly. I believe it was from starting it from my list of programs.