-
-
Notifications
You must be signed in to change notification settings - Fork 239
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
Linux gsm #49
Comments
Could you share what your file looks like? I've tried a few edits after " ## Special case: if there is an arg, use that as executable path ..." but nothing seems to be working so having a copy to look at and compare would be super helpful. Also could you share what your vhserver.cfg looks like? Thank you for making this post btw, was pulling my hair out on how to add it to gsm, now only if i could get it to run. (Server starts but doesn't stay running and I'm not sure why) |
This is what I commented out:
|
I've done that/removed it at one point, what I'm having trouble with is what to do / where to put "do If I add the above code without the (Do/Done ((Leaving the rest of the Case code)) ) and start the server I get (in green) OK and looks to start. If I run details it'll show offline, looking at the log file I see "password to short" (zodm1) but I've tried "ThisLongPass" and still it quits on me with the same password to short error, I can share my log file if needed. |
Probably easier if I share the whole file
|
Thank you so much for posting this, everything's working and v+ is working wonderfully. |
https://i.imgur.com/U06Octo.png Seems like this appears on me |
I think that error is related to binding the server port.
|
Same error with putting that as well. I am using Ubuntu 20.04. |
I used the following script to try and debug any problems with arguments that were being passed
change lgsm config
shows what arguments are being passed |
-public 1 was removed and is not longer used |
Hey, I am writing on a PR that is incorporating am automatic publish system for V+ builds, UnixServer included. I did something similar to this with run_bepinex.sh and would deploy that script on release. I will also add some code which tries to identify (or guess ;)) if it is run within LGSM and act accordingly. All one needs to do is changing the default.cfg or instance.cfg in LGSM. But maybe we can get them to include some magic into LGSM, too... |
I was making it more complicated than it needs to be.
Change lgsm config located at
|
Your version is fine if you want to be LGSM-neutral. Add your params to the run-script or get any of them fomr the arguments. |
Our start.sh for 0.9.6 should be working on any system now. |
When the game server is installed using Linux gsm it passes arguments to a defined executable, so it would be useful for
run_bepinex.sh
to correctly intercept them.Hope this can be implemented for the next linux server release, or it helps anyone searching for guidance for v+ with linuxgsm.
Remove/modify the code which takes an argument to be executable name:
## Special case: if there is an arg, use that as executable path
...Add this switch:
Replacing the following line allows us to start the server with the expected arguments passed by gsm:
"${PWD}/${executable_name}" -name "servername" -password "serverpassword" -nographics -batchmode -port 2456 -world "world"
Change to:
"${PWD}/${executable_name}" -name "${argName}" -password "${argPassword}" -port "${argPort}" -world "${argWorld}" -public "${argPublic}"
Update gsm config file located at:
~/lgsm/config-lgsm/vhserver/vhserver.cfg
Add
executable="./run_bepinex.sh"
Now
./vhserver start
works as expectedConnect to the console if needed with:
tmux a -t vhserver
The text was updated successfully, but these errors were encountered: