-
-
Notifications
You must be signed in to change notification settings - Fork 38
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
Add configuration for custom info (hibernation-warmup) and loading-screen messages #48
Comments
Yes, we deprecated the Python Version simply because of too much overhead for maintenance. As for the go version; we plan to add instructions on how to build it by yourself, but basically it is a simple matter of installing go and running the command Copied answer from #30 (comment) |
@Br31zh exacly, as a plus in next releases will include a compiled binary (no go installation stuff 😉) and I'm thinking about adding more config options in the .json file to increase configurability |
Of course, it was a bad formulation, even if you hadn’t stop maintaining the Python version it’s still a good idea to permit to change that from the configuration ^^ Changing the source code is a temporary workaround. |
Add configuration for custom info (hibernation-warmup) where added in a7cc6c0. configuration for custom loading-screen messages where not added since there is a %d in the string which cal lead to problems if omitted |
@gekigek99 The string from the config could be combined with a string in the script for the countdown though? |
Oh yes... You are right! I will figure it out when I add this functionality (since I think it more important than a silly configurable string) |
I think it’s related, so what about adding configuration for custom hibernation and startup messages? I modified the Python version for that until now but since it’s deprecated…
Sorry if it was already present or proposed.
Originally posted by @Br31zh in https://github.com/gekigek99/minecraft-server-hibernation/issue_comments/709141763
The text was updated successfully, but these errors were encountered: