zha everything broken

While I don't have much I 'can' say in response to your direct questions (being that I'm almost 100% code-side and not lore), I did want to just call out that IMO this was a very considered and well-written critique/inquiry. I strongly agree with where you're coming from, though I don't Expect that final product will be as bleak as you might fear (internally we do tend to mock both the grimdark and HOOAH vibes, and their general avoidance is a subject that's been gone into at some length, and still touched on). So yeah. I don't have anything super substantive to add but I really really really like your post and wanted to call that out.

welcome to the fun zone

Absolute +1. Champ during an insane chaos round. Very well handled.

Reporting Personnel: Eliza Kolmstadt Job Title of Reporting Personnel: Engineer, Hephaestus Industries Game ID: cDh-acjL Personnel Involved: Eliza Kolmstadt, Engineer - Reporting Personnel Yua Kaneko, Atmospheric Technician - Witness D.I.R.E., Artificial Intelligence - Witness Oliver Neely, Engineer - Offender Secondary Witnesses: Rei Ozeuoi, Engineer - Involved in incident remediation. Asher Shi'berud, Engineering Apprentice - Involved in incident remediation. Morgan Guillame, Captain - Monitored radio communications and debriefed Engineering team after incident remediation. Time of Incident: 1-22-2468, roughly between 00:00 and 01:00 Real Time: 1/22/26, roughly between 19:30 PM to 20:30 PM EST Location of Incident: Engineering, Supermatter Reactor Nature of Incident: [X] - Workplace Hazard [ ] - Accident/Injury [ ] - Destruction of Property [X] - Neglect of Duty [ ] - Harassment [ ] - Assault [X] - Misconduct [ ] - Other _____ (Place an x in the box that applies. If other, replace line and specify.) Overview of the Incident: Shift start. Engineering splits up to commence shift-start tasks. Engineer Neely takes Supermatter Ignition; Engineer Kolmstadt takes on training Apprentice Shi'berud, reviewing gear lockers (just outside SM). Atmospheric alarm is triggered in the SM reactor compartment. AI reports Engineer Neely opened the hydrogen canisters, which coupled with active emitter caused immediate hydrogen fire and temperature/pressure spike within SM reactor, along with draining loops of coolant. AI then reports Neely opens the filter bypass pump, causing superheated gas to fill and disable the scrubber lines ship-wide for the duration of the shift, despite ardent efforts by Technician Kaneko to clear them. Engineer Neely's patterns of behavior, while often frustrating and irritating, have not previously provoked incidents of this severity or potential consequence. The combination of reported actions (opening hydrogen cans inside reactor w/ active ignition source, and opening critical valves causing serious damage to atmospherics systems) are cause for grave concern for safety of crew and integrity of ship systems. Submitted Evidence: N/A - Telemetry not collected during incident due to extremity of events, comms logs unavailable to me following incident. Would you like to be personally interviewed? [X] - Yes [ ] - No Did you report it to a Head of Staff or a superior? If so, who? If not, why? Morgan Guillame, Captain. Actions taken: Immediately following incident, Engineer Kolmstadt enters SM reactor chamber to begin remediation, Engineer Neely scrubs out. Due to compartment power failure (and scrubber line shutdown), Engineer Kolmstadt removes a section of outer window in the starboard exterior access airlock vestibule to decompress and vent the reactor compartment. Once superheated gas is vented, lines are refilled with liquid nitrogen (2x canisters) and hydrogen (canisters filled and provided by Technician Kaneko). After SM crystal temperatures stabilize, additional emitter pulses are fired to bring it to nominal low-power state to safely resume provision of ship-wide power. Engineering crew is debriefed by Captain Guillame. Investigators are brought in to interview and investigate grounds, but (to my knowledge) no charges are brought.

Absolutely a +1 from here. Joe is solid.

Need to do a little math to figure out what values make sense, but yeah the behavior needs a quick QoL pass. My INITIAL thoughts: 1. Discharge rate and shift start charge should be semi-randomized per-device. You should always be reasonably near to full charge at shift start, and discharge rates should only vary enough to keep devices from dying in sync. 2. Program usage should impact charge, like Maxspells suggests. An engineer keeping their PDA alive on the alarms app in their pocket at all times, or Josie sending ~2-5 chat messages per minute, should both use more power than someone who leaves it idle in their bag the whole round.

Hey FYI regular crowbars Already Fit in the emergency box

I intend to have a dev diary on engineering stuff coming out Soon(tm)! There's still a handful of items I need to do some basic trials on locally, but I'm super stoked about the engi stuff myself. Post-roundstart activities like actual basebuilding.

yeah i have 0 interest developing for ss14, personally.

hell, it's about time. +1

Big +1 from me! Really excellent work from this one, and easy to talk to about it.

This. I would most likely have peaced out after discovering this place. Tails have more Vibes/Connotations, even if they ought not to, than something like an extra set of arms or similar for IPCs. It's like cat ears or what have you.

I really love this! There's an important distinction that need to be made here between an Exploitables Framework and a Consent Framework though, as one is a development concern and the other is a moderation concern. Using the word 'consent' for this changes Exploitables from a roleplay aid into something that also becomes an additional moderation subject. This would require a larger, separate discussion to pursue meaningfully. By logging into the server, a certain level of broad consent is understood (99% of antag rounds involve violence at some level, right?), and it comes down to having a community that has a basic level of mutual respect and trust to ensure everyone can feel comfortable and safe here on an OOC level. Even if someone fills in an entry as 'negative,' while a courteous antag would always do their best to avoid it, antag rounds Can be chaotic and shit happens and Sometimes you Need a human shield and there's only one to hand! If this is to be a consent framework, I believe 'positive' and 'negative' would need to be changed to 'yes' and 'no,' and the admins/moderators will need to step in to discuss and decide among themselves. All of the above is an important distinction to make between an Exploitables Framework and a Consent Framework, but I believe that if that discussion needs to take place, it would need to be its own thread in the future, as the latter would require the former to first be implemented. So, with that all out of the way, and because I'm a developer and not a moderator or admin (thank fuck), here's my thoughts on an exploitables framework implementation. For the best of both worlds: [Type] - [Pos/Neut/Neg] - [Notes (32 character max)] Example: Bribery - Pos - Money, Snowflake, Morta Blackmail - Pos - TCAF Deserter, '55 Torture - Neg - [blank] Kidnapping/Hostage - Neut - [blank] Yes, a 32-character maximum for notes means you won't be able to write up complex narrative hooks, but it's much much easier for antags to digest. Some Types would have Notes be optional (Torture), others would be required (Blackmail). If ya'll compile a comprehensive list of entries worth having for antags to reference, I'd love to implement this some time! So far: Kidnapping Torture Blackmail Extortion Bribery

Kano seems to be some sort of space warlock. +1

Lore Impact (Small/Medium/Large): Small-- impactful to Europan characters but nothing that drastically different. Species: Human Short Description: Exands on Europa's history, hydrology, government, technology, and culture, grounded in hard sci-fi. How will this be reflected on-station?: Europan characters have more to complain about. Does this addition do anything not achieved by what already exists? Noooooope. Do you understand that the project may change over time in ways you may not foresee once it is handed over to the Lore Team? Yuuuuuuup. Long Description: https://docs.google.com/document/d/1rxMrUNrpfQ1MvC-lAWFzNwbZg1vJFAJiI8JqridG5Ps (Three tabs/pages)