Proposal: User Account Control
Popular, 7-0. Enacted by JonathanDark.
Adminned at 25 Jan 2024 13:49:12 UTC
Create a new rule called “The Mainframe”:
‘’‘The Mainframe’‘’ is a strong AI with advanced natural language capabilities. All dynastic gamestate is secretly tracked by the Mainframe unless otherwise stated, or where it would be impossible.
The Mainframe shall assign each Agent an ‘’‘IP address’‘’ in the form #.#.#.# where each # is a number from 1-255. If any Agent has not been assigned an IP, the Mainframe should secretly randomly assign them one before performing any dynastic actions.
Create a new rule called “Clients”:
There may be any number of ‘’‘Clients’‘’. Each Client has a unique Name and a Passcode, which are strings of 4-16 characters containing only letters, numbers, and underscores. Names are not case-sensitive but Passcodes are. Client Names are publicly tracked in the Database.
As a weekly virtual action, an Agent may ‘’‘create a new Client’‘’ by specifying the desired Name and Passcode for the Client. This may be re-attempted if the action fails.
Add a subrule to “Clients” called “Connections”:
An Agent may be ‘’‘connected’‘’ to any number of Clients. A connection is a relationship between exactly one Agent and one Client.
As a virtual action, an Agent may ‘’‘connect to a Client’‘’ by specifying exactly one Client Name and Passcode pair. If the Passcode is correct for the specified Client, the Agent becomes connected to that Client.
As a virtual action, an Agent may ‘’‘disconnect from a Client’‘’ by specifying a client they are connected to, at which point the Agent is no longer connected to that Client.
Clucky: he/him
It is currently unclear if you fail to attempt a weekly virtual action if you can try again that week.
Also probably need to shore up what it means to be “connected to a client”