zha everything broken

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)

"Enviromental Systems Engineer" has the same repetition issue as the other: having "Systems Engineer" on one side of the aisle and "X Systems Engineer" on the other is misleading design. Envirocontroller, Envirocontrol Tech/Engi, Environment Control Tech, Atmodynamics Engineer, whatever you want to call it, just so long as you're not repeating yourself from elsewhere! As far as the engineering field goes IRL, there are as many rules of thumb to subscribe as far as distinguishing between Engs and Techs go as there are technical fields. Broadly speaking, conventional semantics would suggest that engineers design systems and techs operate them. However, there are too many conventions to argue that decidedly one way or another for all cases. Bear in mind that beyond the explicit goal of this change (provide engineering jobs flavorful alternative titles), you still have an implicit goal to uphold (job titles should uniquely and clearly describe the role they pertain to). The logic governing how we do that needs to follow for all possible cases: if we created three alt titles for every single role according to the same rubric as we do here, would a new player (you might laugh, but we exist) be able to look at the manifest and clearly identify what every character does? Because we don't have a RL convention to be forcibly chained to, a very obvious solution exists: make all Engineer alt titles end in "Engineer", and all Atmos Tech end with "Technician." But even that still leaves the issue of one role having implied highet education! And bear in mind too, that the explicit goal doesn't demand we rely on the existing alt title framework. We may want to have something like 'sub-titles' instead, parenthetical blocks appended to a job title that describes specialization (and, perhaps, a character can choose if they have certain skill levels in future.) Considering we don't know where maintainers weigh in on this yet though, you're probably best served not worrying about more title quibbles until they weigh in.

Whatever you change it to, so long as it doesn't have that same semantic repetition between engi/atmos please! Honestly, the big drawback to alt-titles is not being able to, at a glance, quickly identify who sits in which type of seat. Shitty example: every engineer alt-title having 'engineer' at the end, every atmos tech title having 'technician' at the end. Again, shitty example, but people who have never played any engineering at all should, ideally, be able to recognize whether or not someone can help them with the air or with the electricity.

Recommend replacement of Drive Systems Engineer -> 'Propulsion Engineer' due to semantic similarity to 'Systems Engineer', per Github comment?

Just posted a change request on the PR for a technical issue, but my thoughts on actual flavor are less firm so seemed better to drop them here. Re:Cats: To me, 'Reactor Engineer' suggests a more design/architecture role, whereas a technician is more an operator. While that argument can be applied more broadly to the entire role, I'd still lean towards 'reactor tech' over 'reactor eng'. I'm not super fussed by that one, both vibes are fine. Re:Ping: Echoing Popper & Cats in swapping out 'Shipboard Systems Engineer' with something else. As an alt-title its coupled a little too closely to 'Ship Engineer' by my thinking. I really am doing my best to resist going full ham, god i could happily wax poetic about imaginary engineering specialties all day if you let me

Suggested alt titles for Ship Engineer: - Maintenance Engineer - Reactor Technician - Electromechanic I don't think we should have something like 'Electrician'- these alt-titles aren't like Medical jobs, where each one has a distinct role. All these titles ought to sound like people who know the full range of the (engineering or atmospheric) systems for which the role is responsible. They ought to suggest additional expertise, not sole domain.

+1 We like this one.

I didn't really understand how Aides couldn't already be flavored as bodyguards, personally. I like your contributions greenjoe, this one personally just doesn't quite jive with me for reasons that have already been stated (and that happens, so please don't sweat it too much!)

Prob(clamp((rand(75, 100) - ba) / 2, 0, 100)) every five minutes or so whether you get a message like "your brain feel fuzzy :)", lol

...I really like this fwiw

Currently WIP

Uniform vendors tbh. Clothes vending machines would keep all uniform pieces available (Id love them to vend stuff like department jackets, WINTER COATS, etc) and you can strip out all extraneous dept clothing from all lockers on the ship. (Plus... we have sprites for 3 varieties of vending machine for every single dept to choose from on-hand that match our style.)

This is currently test-merged. There's an insane number of structures, objects, machines, and items in this game, and it'll take me forever to trawl all the code of every single one personally. Therefore, I would be very grateful to the community for any help filling in more in-game documentation, by posting items or objects that could use additional Mechanics or Antagonist hints! (I am not currently adding many assembly/disassembly hints except to the most commonly built/broken objects- there's another rework behind this one to make that programmatic.) For mechanics hints, I am looking for objects which have special interactions (alt-, ctrl-, click-drag, etc.) which are not already listed, or which have functions or interactions with other objects that are useful/non-obvious. For antagonism hints, I am looking for objects which have unique mechanical antagonist interactions, or which can be effectively exploited by antagonists (for example, airlock crush and electrification wires). Please use the below format for any suggested tips: Object Name Mechanics - [Suggested mechanics hint 1.] - [Suggested mechanics hint 2.] Antagonism - [Suggested antagonist hint 1.] - [Suggested antagonist hint 2.] Feedback [Blah blah blah.]

Two more quick screengrab of current working version- critique for readability/clarity, problem of information overload. Initial examine Extended

So I've been playing on Aurora like three months, and this is a place with some seriously opaque mechanics, and it often demands I wiki dive or even code dive to figure out how to do something or if I even CAN do something. While people are very supportive of each other when it comes to helping with mechanics (since it seems like Everyone Suffers), ideally you should be able to examine an object and receive all the information you need about how to interact with it in any common capacity. While many objects do have some 'show additional information' text, it is not implemented consistently. There are several different types of information that would be very useful to have when examining objects, which I have broken down by function below: [Name] [Damage/Condition]* [Description] [Extended Description]** [Mechanics]** (how do i X) [Assembly/Disassembly]** (what tools to use) [Upgrades]** (science has a point?) [Antagonist Interactions]** (if the user is an antagonist/observer) [General Status/Feedback] * - If the object is damaged. ** - If the user clicks the '[Show in Chat]' button. This is currently a WIP. There is a PR for this where implementation feedback can be provided, but this forum thread is intended for UI feedback and how it looks/feels presents. I have laid some groundwork for this update already, and [Show in Chat] already gives you better information on many objects, but the following are some screenshots from both live in-game and my WIP branch for your consideration. Please disregard minor style differences between screenshots, they were taken at different times and stages.

Ckey/BYOND Username: batra Discord Name: batcountry Position Being Applied For: coder Past Experiences/Knowledge: Many years development for a major Neverwinter Nights persistent world as a 'core' staff member. This included coding, mapping, spriting, modeling, texturing, lore-writing, and advising on long-term planning and design. Also, being another spaghetti-filled volunteer-built server on a 20+ year old game, lots of untangling old baked-in weirdness in the code and engine. Examples of Past Work: All the Neverwinter Nights repos I've contributed to are private unfortunately, but here's some Aurora stuff: https://github.com/Aurorastation/Aurora.3/pull/20892 https://github.com/Aurorastation/Aurora.3/pull/20880 https://github.com/Aurorastation/Aurora.3/pull/20831 https://github.com/Aurorastation/Aurora.3/pull/20813 Additional Comments: As can be inferred above, I am very much a 'jack-of-all-trades' type developer- while I worked with plenty of excellent people who were far more skilled in any given domain, I tended to advise on the integrations between different roles/products of those roles. Being new to SS13 (barely over 3 months as of this application), I've had quite a bit of difficulty dealing with the engine and interface, and am as interested (if not moreso) in organizing, streamlining, and QoL improvements as I am in new features.

Functionally, this is just an ask for the gamemode vote duration to be changed from 60s to 300s, isn't it?

PRed in https://github.com/Aurorastation/Aurora.3/pull/20860

Opens mouth- -closes mouth. GL!

Updated second post with just the titles that start with A. As I'm going through these, tbh giving the online library page controls to edit everything right from the browser would be extremely ideal, but that's also out of my scope and would demand admin call too. Would make managing books on the fly when necessary (i.e. someone uploads some crazy shit or whatever) extremely easy to just handle and clean up from a web interface.

Post reserved for the lists of every item to be re-categorized/archived/removed, once I finish reading all of them. TL;DR completely subjective judgement calls on my part below. You've been warned. Why a book might have been categorized for archive: - References old mechanics. - Every creative act involves a person putting a part of themselves into something, but when I played a librarian elsewhere, I would have asked for more because I'm a heartless gatekeeping cad like that. I'm still new enough here that I don't know enough people for any of it to be personal sorry love y'all but if a judgement call on quality has to be made I'll bite the bullet and make it. Why a book might have been categorized for deletion: - Duplicate of an existing book - Minimal contribution to the server or setting - Works from other media- I don't have an issue with someone uploading Kipling or Coleridge so long as they're credited, but a snippet copy-pasted from a book from a random other video game that has 0 to do with Aurora or the setting or anything? Curation strikes again. - References excessive meta/OOC information or removed lore - Personal judgement call like above. Sorry! There's a reason I'm dropping it all here for the public eye first! All books listed in csv-friendly format: Title|ID Books to assign to Archive repo: 10 Random Sol Facts, Earth Edition|701 A Beautiful Way of Understanding Our Universe One|799 A guide to Blobs|1188 A Short Series Of Events, 1|1029 A Short Series Of Events, 2|1030 A Short Series Of Events, 4|1032 An Idiot's Guide To Binary|656 blank book|1622 Books to delete: An Interview with a Th'akh Shaman|1575 Book: Big Blue Sky|1623 A Series of Quotes|923 Anything Goes|1089 April Come She Will|1134 Books to update Category to 'Fiction': Ayta and the Pale Stag, Part 1|1577 Books to update Category to 'Non-Fiction': An sumarized History of the Empire of Dominia|1636 Appeal of 18 June|1168 Books to update Category to 'Poetry': A Drop Of Red|248 A Hopeful Tale of the Depressed|1277 A Poem of Question|655 A Seaside Stroll|1511 A Short Poem On Mice|1038 A Trace in the Ether|1657 A wasteland|1466 Acquainted with the Night|242 Ad Gloriam - Memories of a warrior|1040 After You Have Gone|1143 Alabaster Eyes|1505 Alcohol, Cargo, Despair|565 Alone|1158 Altered Beast Inside|1097 An Account From the Siege of Trizar|1358 An Homage to the Miniscule, in the Style of Rudyard Kipling|445 Apartheid|1426 Apocalypse State of Mind|1295 Ark upon the sea|1482 As they sit here|1369 At the Bar|477 AT:After Theft|1474 Books to update Category to 'Art-Culture': 6 Moments musicaux, D 780, Opus 94 No3|1638 A Guide to Marching Band Instruments: Brass and Woodwinds|514 A Guide to Marching Band Instruments: Percussion|515 Adult Coloring - Adhomai Fauna Edition|912 Adult Coloring - Old Earth Wonders Edition|946 Adult Coloring - Space Edition|908 Adult Coloring - Tau Ceti Edition|911 An Exciting Journey Through Europan Cusine|1580 Assunzionii Paintings|1554 Books to update Category to 'Article-Report': An Interview with CelestAI, Part One|559 An Interview with CelestAI, Part Two|560 An Interview with Walter Keck, chaplain|386 Books to assign to Command Repo: A Guide For New NT Liaisons|1388 Books to assign to Engineering Repo: A Scrapmaster's Guide to Disassembly, Vol. 1:1410 Assembling A Pistol|557 Atmospheric Technician's Reference Book|573 Books to assign to Medical Repo: A Brief Medical Primer|1641 A Study on the Pharmaceutical Benefits of Botany|1339 Anxiety and You|927 Aurora and Mental Health|251 Books to assign to Science Repo: A Guide to the Science of Crafting Guns - Part 1|1336 A Guide to the Science of Crafting Guns - Part 2|1337 Advanced Combinatorial Explosives Manual|800 Apple Tree Mutation Study|781 Books to assign to Security Repo: A Guide to the Science of Crafting Guns - Part 1|1336 A Guide to the Science of Crafting Guns - Part 2|1337 An Idiot's Guide to Crime Scenes|448 Assembling A Pistol|557 Books to assign to Service Repo: A Study on the Pharmaceutical Benefits of Botany|1339 Apple Tree Mutation Study|781 Books to migrate to the Corrupted Repo* (if this isn't created, then just deleted): Authentic Scriptures of the Forgotten|1012