#Problem setting up server
40 messages · Page 1 of 1 (latest)
Oh, haven't seen that in a while, but have seen it before.
Perchance your system is set to non English?
I did manage to setup a Craftoria server for me and a few friends around January this year in the exact same way.
Huh. iirc, that error—not finding the winargs.txt—was what happed when someone used an java earlier than java21.
But you are using 21, so it's weird.
Did you change JDK installs between now and January when you last had success with installing a Craftoria server?
might be worth adding - "-version" and seeing what version it prints out or just pointing the forced java path to the 21 install
some underlying issue is that serverstarter doesnt use the java path that it is running from, it uses the default java command https://github.com/TeamAOF/ServerStarter/blob/b626da338b1c32c23c879d5561afc166a8162ecb/src/main/kotlin/atm/bloodworkxgaming/serverstarter/LoaderManager.kt#L242-L243
Ahhh… makes sense.
Yes, that please @tired plaza … try running the command “java -version” and see what that says.
Output from running the command:
Not 100% sure but I do not believe I changed anything.
it does look like you are missing the entire neoforge install. i suggest deleting the .lock file and letting it reinstall neoforge
I have tried doing that multiple times for the past few days.
Just to ask the dumb question, because somethings going wrong...
...exactly what steps are you going through to install the server?
I install the server files from the curseforge page, I unarchive the zip, run the "startserver.bat" let it download everything and accept the EULA, and then the server doesn't start and shows the same error that I would get when trying to start it later on.
If needed to I could happily provide a screen share or other kind of recording.
where is the libraries folder
if you continue to have problems with it installing neoforge and you want to actually troubleshoot:
open the yaml file in notepad
change installPack: true to installPack: false
delete the .lock file
run startserver and see what it says when trying to install
No worries about screen share or anything like that.
Sometimes people come up with odd (and wrong) ways to do something—but what you are describing is correct.
if you dont feel like troubleshooting, you can just install the correct version of neoforge using the official neoforge installer https://maven.neoforged.net/releases/net/neoforged/neoforge/21.1.169/neoforge-21.1.169-installer.jar (this is for the 1.20.3 version of the pack which uses neoforge 21.1.169)
If you do want to debug a little more... what's the output for the command: echo %JAVA_PATH%?
||I think I got that right... I'm a bit shaky on Windows stuff||
||only works in cmd. powershell would use $env:JAVA_PATH||
True. I think he's using CMD. At least in the one screenshot they are.
This is the output from the troubleshooting.
This doesn't output anything
Could I get a little insight of how to install this and implement it? Never done this before
What’s up with the ? in the pathname?
oh its because I enjoy having a clean desktop combined with wallpaper engine. Its an invisible unicode and never caused me issues.
For science... try it without that; give it a normal name.
As in just having it on the desktop?
As in rename whatever the folder is that's showing as a ? in that path... to something simple with just the plain letters of the alphabet.
Then try installing the server again.
Alright give me a minute for it to install.
🤦♂️ it suddenly worked... I am so sorry lol 😦 wasted so much of your time, I managed to install it in that folder before as I have all other minecraft servers there as well so never thought of it being the problem.
No worries!
As you said, that hadn't caused any other problems for you for some time. How could you know?
I didn't know... was just keeping an eye out for something unusual and we happened to find it.
Anyhow... enjoy your game and world(s)!
Thank you! Weirdly enough this is somehow the only modpack that won't start because of that 😄
¯_(ツ)_/¯
I wonder if adding -Dfile.encoding=utf8 to the JAVA_ARGS environment variable would have fixed this