Server Import Issues
Closed this issue · 14 comments
Trying to import a 1.11.1 vanilla server, checked that it runs, still fails to import. Generic "there was an issue, please try again." I tried with multiple other servers, only one worked, and I don't know why.
Don't know whether there is a log.txt, or I would send it.
Don't know whether there is a log.txt, or I would send it.
Hi there, out of curiosity, does the server have a startup script?
I would suggest downloading the latest artifact from actions and seeing if that works for you.
works with latest artifacts build
You should publicize this more, this is an amazing tool.
Happened again, when importing valhesia 3 3.5.1 server, there is an error
Happened again, when importing valhesia 3 3.5.1 server, there is an error
Is this a modpack? If so, make sure you're importing the server as a .zip and not like you'd import a standard server, it may not work as expected. If it's a modpack, please post the link to the exact version you downloaded!
It is not a zip, it's a server. It doesn't have as server.jar though, just a startup .bat.
this is the structure of the folder
this is the structure of the folder
auto-mcs will only let you import a modpack as a .zip file. Since this server doesn't have a .jar file other than the forge installer, I don't believe it's able to recognize just the installer. If Forge was installed auto-mcs would be able to recognize the server. You could compress the files into a .zip file and you should be able to import this server as a modpack. It's kind of inconvenient, but I will continue looking into a better way to import a modpack that's extracted.
Can it identify this?
Can it identify this?
Try it, I believe it would recognize Forge
Hi @5ghzx, are you still having issues with this?
Closing as no response was recieved about this