New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug Report] Jmusic-0.4.0 jar file - a java exception has occured #1497
Comments
same here |
I believe this is because we have upgraded to Java 11 in version 0.4.0 & you're using Java 8 at the moment. Can you check if you have Java 8 & if you do, upgrade to 11? |
seems to work with AdoptOpenJDK x64 11 which can be handily installed via ninite dot com |
that was the reason why - its fixed now thanks |
Can you expand on how to update Java? I downloaded version 11 (11.0.22) and confirmed it is the version I am using by typing java -version into the cmd, but I am still getting the error when trying to run the bot. |
With just that screenshot it's a bit hard to debug. For anyone still running into this issue, can you share the output of running both |
Can you navigate to the folder ( |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
the issue was because i didnt know i needed Java 11 Lmao - and i dont run it via CMD - but i downloaded Java 11 and it worked so :) |
This comment was marked as off-topic.
This comment was marked as off-topic.
Please keep in mind that the issue we are tracking is a java exception occurring. This happens immediately upon double-clicking the jar in a desktop environment. |
I have the same problem. I have java 21 installed and 4.0 jar fails to start. |
Bug Description
Steps to Reproduce
download the latest, then attempt to run it after setting up the file
Expected Result
to load up the music bot
Debug Output
cannot get bot to load - just has a the following thing in the image below
Additional Info
No response
Checklist
The text was updated successfully, but these errors were encountered: