User:GreytideSkye/Sandbox

Bitrunner Antagonists (Hostile Data Entities / Cyber Police) PERMANENT MECHANICAL STATE

Enabled
Description: You are a hostile data entity created in response to a network intrusion. You are created in the context of a virtual domain, and are themed as such, but your objectives remain static: Kill the intruders and protect your home. You cease to exist when the domain is unloaded.
Special Rules: The Beach Bums spawned in the Beach Bar virtual domain are non-hostile. CI applies with them, roleplay is encouraged, and fighting is frowned upon. The entire Bitrunning Domain is in a Permanent Mechanical State, including the Safehouse structure. You are aware that you are actively under attack. You do not need to witness a bitrunner to justify making additional defensive decisions or modifications to your surroundings. Do not attempt to permanently ensnare bitrunners in the virtual domain. You want them dead and gone, not vegetatively immobile. This includes breaking, damaging, or otherwise rendering the Encrypted Cache permanently unable to be moved to the drop-off, or the puzzle to acquire the Cache unable to be completed. You are not aware of the significance of the Encrypted Cache and should not be moving or hiding it. You are in a permanent mechanical state at all times. CI isn’t necessary, nor is RP. You are unaware you're virtual code. The entire simulation is real to you. Cyber Police are aware they are virtual, and are the computer's response to the hostile intrusion. If you are somehow removed from the virtual domain and are able to interact with the "real world," contact an admin.
Metaprotections: None. You are just another hostile program in a virtual domain full of hostile programs.

Guide to Money

or... Station Economy?

there is no fucking way that's true. that'd be so dumb. that'd be madness. I'm going to search the tg codebase for what actually happens Was right about the Protolathes, that money for Unauthorized Users goes to the department. Don't think the electricity tax on cyborgs for using the lathe goes anywhere.

• • ACCOUNT_ENG** has vendors including a "Bluespace Vendor"
  • ACCOUNT_SCI** has vendors, including the modular computer vendor. Papers you sell. There's a **setting** where *every node researched on the Techweb* pays the budget some amount "techweb_bounty" (250cr by default), and while the default parameter for "get\_that\_dosh" is TRUE I can't promise it's actually used.

There's a FULL_ANCAP mode where shit like cryopods charge money. (Fun fact, the default value for fair\_market\_price is 69. niiiiice)

• • ACCOUNT_MED** has the Medical Kiosk out front which always charges you 15cr *but you can use a multitool on the **board** to change this price*. Under FULL\_ANCAP, Med charges 10cr for cryopods, 5cr for Sleepers, 10cr for Stasis beds.
  • ACCOUNT_SRV** gets the cash from *all* the snack vendors. I **don't** see where the Tourist robots add to the department budget, so I think they... don't? (Double-checking on Skyrat's code, and nope don't see shit there either, but fun fact: LustWish goes there too) Which means the strategy is to *ask your Cook to **not** make free food, and direct folk to the snack vendors*.
  • ACCOUNT_CAR** is the big one that coders treat as **The Station Budget**. See: paying pirates, the vault, shuttle insurance (Fun fact: if you buy shuttle insurance but then the shuttle catastrophe happens, you get 8000cr) There's this gem: ||icon_state = "car_budget" //saving up for a new tesla|| The "galactic_grant" positive station trait gives you 2k-5k bonus here at the start. Contractor ransom (1k-3k) comes from here. Cargo consoles all need to know ACCOUNT_CAR.

Confirming: the tourist only gives holochip payment. The round-end number is a total of these holochips handed over, and nothing goes into the Service Budget from them.

ok update apparently all departments get (at most) 500 credits every 5 minutes, as per /economy/proc/departmental_payouts().

Delivery crates with a Department Destination give Payment to ACCOUNT_CAR equal to pack.cost,