Skip to content
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

Error: Could not find or load main class Support.gdlauncher_next.datastore.libraries #1075

Open
PowerSchill opened this issue Sep 19, 2021 · 2 comments
Labels
Type: Bug Non fatal problems who can be ignored/worked around

Comments

@PowerSchill
Copy link

Describe the bug

When trying to launch an instance with Forge 37.0.69 and Minecraft version 1.17.1 the following error is presented.

ps stderr: Error: Could not find or load main class Support.gdlauncher_next.datastore.libraries
Caused by: java.lang.ClassNotFoundException: Support.gdlauncher_next.datastore.libraries

To Reproduce
Steps to reproduce the behavior:

  1. Create a Forge instance for 37.0.69
  2. Launch the above instance

Expected behavior

Minecraft starts loading

Possible solutions

Screenshots

image

Operating System:

  • OS: MacOS
  • Version: 12.0 Monterey Beta
  • Java Version: 16
  • Minecraft Version: 1.17.1
  • Mod Loader: Forge

Additional context

@Eskaan
Copy link
Collaborator

Eskaan commented Sep 19, 2021

Yeah, we know that. It’s caused by the space in one of your folders in the path.Temporary Fix: in the settings, move your files to somewhere whit no space in the path. i.e. Documents/GDLauncher/

@Eskaan Eskaan added the Type: Bug Non fatal problems who can be ignored/worked around label Sep 19, 2021
@blarfoon
Copy link
Member

It’s fixed in latest beta coming out tomorrow, it’ll come out in stable in a week

@Eskaan Eskaan linked a pull request May 18, 2022 that will close this issue
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Non fatal problems who can be ignored/worked around
Development

Successfully merging a pull request may close this issue.

3 participants