We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
1.11.9
1.11.13
steamcmd - enshrouded
No, I did not modify the egg
making enshrouded server configure the server password joining the with password
joining server, password is incorrect
The Dev`s have updated the server config and they added extra "usergroups" settings with password variable. the old one variable is not used
Step 1 - install server Step 2 - Configure Password Step 3 - Try to connect
game update
The text was updated successfully, but these errors were encountered:
use the lastest egg. Its allready fixed since months
Sorry, something went wrong.
i have it downloaded just today from this repo the pterodactyl egg and the server json is the old one, mine from the server is this:
enshrouded_server.json
it looks different then from the github repo.
ok, i only updated it in my repo: Use this, until i find some time, to update this egg here too
https://github.com/gsrvtech/gameserver-templates/tree/main/steamcmd-games/enshrouded
btw: My egg is the official one in their discord ;) With some search you could find it :)
No branches or pull requests
Panel Version
1.11.9
Wings Version
1.11.13
Service
steamcmd - enshrouded
Modified
No, I did not modify the egg
Expected Behavior
making enshrouded server
configure the server password
joining the with password
Actual Behavior
joining server, password is incorrect
The Dev`s have updated the server config and they added extra "usergroups" settings with password variable. the old one variable is not used
Steps To Reproduce
Step 1 - install server
Step 2 - Configure Password
Step 3 - Try to connect
Install logs
game update
The text was updated successfully, but these errors were encountered: