Proposal: Out of Power
Timed out, 2-0 with 2 DEFs. Enacted by JonathanDark.
Adminned at 31 Jan 2024 16:23:16 UTC
In the rule “Clients”, add the following new subrule titled “Power”:
Each client except the Dark Web has ‘’‘Power’‘’, which is an integer between 0 and 100 inclusive and defaults to 50. Every time a Client other than the Dark Web performs a successful ‘’‘Shell Command’‘’ its Power is reduced by the ‘’‘Power Consumption’‘’ of that Shell Command, to a minimum of 0.
To the rule “Shell Commands”, after “An Agent must be connected to a Client to perform Shell Commands as that Client. To perform a Shell Command, you must always specify exactly one Client that you are connected to, or the action fails”, add
Each Shell Command has a ‘’‘Power Consumption’‘’, which is a non-negative integer and by default 10. If a Client (other than the Dark Web) tries to perform a Shell Command whose Power Consumption is greater than that Client’s Power, it will fail.
To the end of the descriptions of the “ping” and “request a copy of logs” Shell Commands, add:
‘’‘Power Consumption’‘’: 0
If there exists a subrule titled “Brute Force”, then in the rule “Clients”, in the subrule “The Dark Web”, add
The Dark Web may not ‘’‘brute force’‘’.
Add the following new subrule titled “Recharge” to the rule “hell Commands”:
As a weekly Shell Command, a Client may ‘’‘recharge’‘’. The Mainframe will set that Client’s Power to 100. ‘’‘Power Consumption’‘’: 0
This should make some gameplay decisions a bit less trivial
JonathanDark: he/him
Each Shell Command has a ‘’‘Power Consumption’‘’ but you added ‘’‘Cost: 0’‘’ to the ping and request logs commands. Either make that ‘’‘Power Consumption: 0’‘’ or change Power Consumption to Cost everywhere else.
Also, the logs command is technically ‘’‘request a copy of logs’‘’ so you should probably use that exact phrase. I wouldn’t be opposed to renaming that command since it’s a bit wordy.