Closed Norisek closed 7 months ago
Heya,
errors like this may be caused by paths with spaces in them when running a server on Windows. Its a Powershell issue I have no control over. Or it may be an issue with Forge. Either way, this is, unfortunately for you, not a ServerPackCreator issue/bug.
Just to be on the safe side: You mentioned
past windows path
You are using Windows and you ran the .ps1-script, correct?
Cheers, Griefed
You are using Windows and you ran the .ps1-script, correct?
Yes and yes.
I said "past windows path" because it looks as if the illegal character was inside the jar file according to the path from the error.
If the invalid character was inside the JAR, then there'd be nothing I could do about it, as that portion of the start procedure already concerned the Forge server.
The only thing I could imagine being an issue would be spaces or special characters inside the path to the server pack.
It's recently come to my attention that the way a Powershell script is started may also have an affect on running it.
Unless you're already doing it that way, then:
.\start.ps1
If this also doesn't help, then I'm out of ideas.
Cheers, Griefed
Closing this due to lack of feedback. Feel free to re-open if this pops up again. Keep in mind, though, that the described behaviour is nothing I can do much about, as I already explained how to handle it.
Cheers, Griefed
What happened?
I can't start server, because of illegal character, but it's past windows path.
What did you expect to happen?
Server launches normally.
Version
5.1.10
Relevant log output
Anything else you would like to add?
Tell me!
If you are using the webservice, in which browers did you encounter this bug?
No response
Code of Conduct