Adds minimum dynamic threat threshold for War Ops #81854
Conversation
tgstation-server
added
Balance
|
https://tgstation13.org/phpBB/viewtopic.php?f=5&t=35881 to discuss it. |
MrMelbert
changed the title
| /datum/antagonist/nukeop | ||
| name = ROLE_NUCLEAR_OPERATIVE | ||
| roundend_category = "syndicate operatives" //just in case | ||
| antagpanel_category = ANTAG_GROUP_SYNDICATE |
There was a problem hiding this comment.
Idk what's going on here but you seem to have re-added the entirety of the nuke op datum, and I don't know why. I think someone moved its file recently so that might be your problem.
|
Also I guess this technically exists already?
|
I think the idea is to disable warops aka declaring war, not nukeops |
|
Isn't this something that already basically exists as a population lock? |
|
What is the point of a chef when the station is getting nuked in 10 minutes instead of 30 |
|
before you make this next time please check with headadmins and headcoders to come up with a design for what you want to achieve. mostly this PR just confused them. |
About The Pull Request
This should allow war ops to only happen if the threat is above a certain level.
Why It's Good For The Game
Unlike other round-ending game-modes (eg cult/revs) This game mode makes everyone act differently and ruins the round for anyone who wants to act normally. What is the point of a chef when the station is either getting nuked in 30 minutes or evacuated in 30?
Changelog
🆑
balance: war ops requires threat
admin: added an admin threat limit for war ops
server: something server ops should know
/:cl:
I'm fairly certain this isn;t enough code to do the thing I want to but I'm not gonna do more code before I;m at least relatively certain this code is liked by the powers that be :)