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
Adds a dynamic config to cap the maximum threat level, max_threat_level #61869
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Update dynamic/README.md to include it with the rest of the documentation.
Does that var max out at 100? |
I asked what to default it to and Mothblocks said 100. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we have a sample dynamic.json somewhere? If so, add this to it please
@Cyberboss We don't need it there, there's a large amount of configuration options that aren't (considering everything that is a var is configurable). Good documentation is sound enough. |
…hreat_level (tgstation#948) * Adds a dynamic config to cap the maximum threat level, max_threat_level (tgstation#61869) Co-authored-by: Mothblocks <35135081+Mothblocks@ users.noreply.github.com> * Adds a dynamic config to cap the maximum threat level, max_threat_level Co-authored-by: Iamgoofball <iamgoofball@gmail.com> Co-authored-by: Mothblocks <35135081+Mothblocks@ users.noreply.github.com>
About The Pull Request
See title.
Why It's Good For The Game
Config requested by the downstream.
Changelog
🆑
server: Dynamic now has an extra configuration value, max_threat_level. Defaults to 100 threat.
/:cl: