Skip to content

Conversation

@Aearo-Deepwater
Copy link

@Aearo-Deepwater Aearo-Deepwater commented Aug 16, 2025

Link to current version of file

(Text below is copy-pasted and may be out of date)

Virology

Designers Coders Implemented GitHub Links
SeaWyrm SeaWyrm TBD

Overview

A take on how virology might be re-added to the game in a way that has depth and is interesting and enjoyable for everyone.

Features to be added

Diseases

A few (one to three, maybe) diseases will happen every shift, but most of them will be mild and ignorable - a runny nose, a slight cough, and so on. Moderate diseases, requiring some virology intervention, will be possible but uncommon. Severe diseases will be their own game mode.

A disease will spawn in at a location or on an object. Anyone who walks through the location or touches the object will have a chance to catch the disease. Unsanitary objects or locations - trash, spilled liquids, corpses, spoiled food, miasma, and so forth - will be more likely to harbor diseases.

A disease will be either bacterial, or virological. It will have:

  • One or more symptoms from a weighted list, ranging in severity from "you get the sniffles" to "spontaneous combustion." These will include normal, sensible symptoms, but also (more rarely) silly space game symptoms.
  • One or more methods of transmission. For instance, "surface contact," "airborne," "looking at someone."
  • A mutation rate.
  • A speed of progression.
  • Incubation time and symptom onset time. Incubation time governs how long it takes for the victim to become infectious. Symptom onset time governs how long it takes for the victim to start displaying symptoms. Incubation time should be shorter, so that victims start spreading the disease before they know for sure that they have it. Speed of progression governs both of these, as well as the rate at which additional symptoms manifest. It should be possible to change the speed of progression via medical interventions.

Bacterial diseases will also have a separate resistance level against each antibiotic.

Viral diseases will also have a genetic code, similar to how different characters have different DNA patterns that the detective can find and match to their records.

Damage and Immunity

Diseases will not and should not behave like an "invisible health bar."

Diseases will not harm the victim directly. All harm will be a secondary effect of the disease's symptoms. For instance, a fever will cause increasing amounts of heat damage. This means that a patient with a disease can be treated with normal medical interventions to control the symptoms, and if the symptoms are kept under control, will recover naturally.

All diseases will behave like reagents in the player's bloodstream, but with much slower metabolism governed by their speed of progression. Each time the progression ticks, the bacterial or viral load in the bloodstream will increase, which will also increase the severity of symptoms.

The victim's body will also produce 'antiserum,' which will diminish the amount of bacterial or viral load. These will accumulate slowly, but build up until they can overcome the disease. The numbers should center around a sweet spot where mild diseases will generally go away on their own, and severe diseases will grow quickly enough that they're likely to kill the patient before the patient generates enough antiserum to beat it back.

Antiserum will be keyed to a particular disease. If a person has one disease, and catches another, they'll produce two distinct flavors of antiserum at two different levels. If they get over a disease, the antiserum will linger in their bloodstream, making them much less likely to catch it again. Virologists can also extract antiserum from a person's bloodstream and isolate it to produce a treatment for other patients.

A new organ, 'Lymph Nodes,' will be responsible for metabolising antiserum.

Diagnosis and Treatment

The first step in diagnosis is simply observing and talking to patients to start to build a profile of the disease. Swab samples can be taken from patients and from objects and surfaces that are suspected of harboring diseases; the Disease Diagnoser Delta Extreme will take a swab sample and reveal if there is a disease present in the sample, and if so, whether it is viral or bacterial.

Bacterial diseases are straightforward: Chemistry will have three new reagents they can produce which serve as antibacterials. These will be roughly equivalent to each other - the main difference is that a bacterial infection can build up resistances to them, so for a particularly severe bacterial disease with a high mutation rate, it may be necessary to switch antibacterials. Antibacterials will attack the bacterial load in the patient's bloodstream just like antiserum.

In the case of bacterial diseases, virologists might still be responsible for helping to track down the source of the disease and eliminate it, possibly with some janitorial assistance for those hard-to-clean surfaces.

Viral diseases are more complicated. The virologists will need to piece together the virus's genetic sequence as best they can. The most effective way to do this will involve some legwork and detective skills: Tracking down contaminated individuals, objects, and surfaces, and taking lots and lots of swab samples. Each sample will have fragments of the virus's entire genome. To reveal these fragments, the sample must be run through a new machine: The gene sequencer. This will take a little while - maybe 30 seconds to a minute - to sequence the DNA from the sample, though multiple samples can be queued up and run in parallel. (The delay introduces downtime in the virology lab, incentivising virologists to go out into the station and gather more samples and information about the disease's spread.) The gene sequencer, when finished, will print its results out onto a slip of paper. The sequenced DNA, however, will take the form of a set of chopped-up, unordered segments of varying length and completeness. Older samples will have shorter segments, fewer segments, and a higher likelihood of having unreadable or incorrect nucleotides.

The paper slip from the sequencer is inserted into the DDDE, which will help the virologist organize the information they have and offer some information about what the fragments actually do within the virus (see below.)

If the sample comes from a patient's blood, it will also have pieces of the patient's own DNA (the same code used by detectives) mixed in with the viral DNA. Virologists will have to sort out which fragments come from which source. Blood, incidentally, must be centrifuged and separated into components, one of which will contain the DNA sample.

Virologists don't need to figure out the whole genome of the virus before they can start to produce treatment, but the closer their sequence is to the correct sequence, the more effective it will be. If the treatment sequence is too far off, it will either be ineffective, or downright harmful. They can also produce vaccines based on shorter fragments of DNA. The effectiveness of the vaccine is based both on how well it matches the viral DNA, and how long a sequence it uses; a vaccine based on, say, "A" would match pretty much any virus, but would be basically useless. Vaccines of course won't help patients who are already infected, but will prompt uninfected patients to start producing antiserum.

Once the virologist has a promising sequence, they can take it to the vaccine generator, which will produce a small quantity of test vaccine. When a test treatment is determined to be effective, it can be sent to Chemistry for mass-production.

In addition to the DDDE, petri dishes will be available. A petri dish can be swabbed, and any bacteria present on the swab will be loaded into the petri dish. Once enough time has passed, the petri dish will reveal the presence, amount, and number of different types of bacteria that have grown in it. Reagents can also be added to a petri dish to observe their effects on the bacteria - this is one way to check if bacteria have developed resistence to a given antibiotic. Petri dishes should be supplied to Virology, and possibly also Chemistry.

Petri dishes can break, spilling their bacterial load onto the ground. They will also contain agar, a food reagent that will transmit any bacteria growing in the dish to anyone who eats it. If there are no bacteria, it is harmless. Agar could also potentially be a component in food or drink recipes for chefs and bartenders.

Viruses will not interact with petri dishes.

Recordkeeping

The vaccinator machine will automatically log all created vaccines to the medical records computer's database - something a would-be bioengineer will have to keep in mind if they're trying to be underhanded. Virologists can then use the computer to associate vaccines with patients they've been used on, similar to how the criminal records computer can be used to set crewmembers to wanted and so forth.

Virologists should also be well-equipped with labelers, on top of which, swabs and petri dishes can have paper applied to them as labels similarly to how crates and lockers can.

Mutation

Mutation rate is one of the things that can make a disease more dangerous.

Bacterial diseases can only mutate to build up resistance to specific antibacterial agents.

Viruses, however, can cause more problems.

First of all, as viruses mutate, they will drift from the original virus's genetic code, making treatment less effective. Second, as the code mutates, the disease's symptoms and stats will also change. At worst, this can introduce new, more harmful symptoms. For more serious diseases, virologists will have to act fast and continue gathering samples to stay ahead of mutations. Treatment based on the original genome will still tend to be most effective overall, since it will best match the widest range of possible mutations, but as a disease spreads, that initial genome will become less and less relevant.

This also affects antiserum! A rapidly-mutating virus's genome might drift from what the victim's immune system is trying to fight to the point where the antiserum they've accumulated becomes useless.

Virology as a Role

Since an average round will require little to no action from virologists, a virologist will by default act as a regular doctor. Since medbay is where it will most likely first become evident that a disease is on the loose, this does mean that they'll be in position to know when they have to start mounting a response.

If there are no virologists on staff, a CMO might recruit from among the existing medical staff, or they might take on those duties themself.

Prevention

Depending on the disease's mode of transmission, surgical masks, (which already exist,) latex gloves, (which already exist,) and even tissues or handkerchiefs (which could be added) can be used to help prevent them from spreading. Space Cleaner will reduce viral load on a given surface or object, though it won't necessarily eliminate it entirely. Bleach will be twice as effective, but not immediately available. For more severe diseases, biosuits and gas masks might be necessary.

Anyone who leaves their used tissues on the ground is a bad person and should feel bad. Anyone who picks them up bare-handed is liable to contract whatever disease the person had.

Quarantine

Quarantine is fun, except for when it really, really isn't: Dividing the station up into "safe" and "infected" areas could lead to all sorts of interesting situations, and should be encouraged by giving the virology department a healthy supply of inflatable doors and barriers, as well as warning signs and holos to put up. Locking a given player into a tiny room for half the round should be discouraged, and isolated wards for sick people should probably not be provided.

Unfortunately, it would be difficult for any system where infections can be passed from player to player to not have some incentive for players to lock each other up.

For this design, it helps that diseases both have an incubation period where they can spread undetected, and multiple possible modes of transmission. Locking an infected person up still might seem like a good idea, but there are alternatives if the mode of transmission is identified, and it's less effective anyway since by the time symptoms show up, at least some of the damage is already done. The added uncertainty especially means that locking a particular person up is less undeniably a good idea, giving them more grounds to argue back or even justifiably resist.

Bioengineering

For anyone who wants to dip their rubber-gloved arms into the dirty, grimy world of engineering their own viruses, thinking of a virus's genetic code as a mere string of letters is no longer sufficient. The code has to have meaning.

Here's how that works:

A virus's genome is a series of alternating tags and modifiers. A tag will declare the 'field' being modified - mutation rate, or symptoms, or so forth. The modifier will then decode to a numeric or keyed value, which is added to the virus's base values for its fields. This code is interpreted linearly from the beginning of the string to the end.

Of course, players won't see the tags and modifiers directly. They'll see an apparently-meaningless jumble of nucleotides: CAGAGTTAGACTAGA and so forth. It'll be up to them to figure out what means what.

That task isn't as impossible as it sounds, though, because they'll have some tools to help them. But before those tools are of any use, they'll need to collect samples; nobody can sit around in a closed-off virology office and do all the work without interacting with anyone else. Once samples are acquired, the samples have to be sequenced in a gene sequencer, and then fed into the DDDE. (So far, this is identical to the process of developing a vaccine.)

The sequenced DNA, as previously mentioned, will have been chopped into shorter fragments, and won't represent a complete virus genome. The DDDE can parse each fragment and explain what it does, though incomplete fragments might not be parseable, or might be interpreted differently from the gene's representation in a virus's complete genome.

For the sake of creating a vaccine, the virologist's only goal here will be to piece together fragments into a complete and accurate genome, or as close to one as they can get. Engineering gets more complicated - but it's essentially the same process, except instead of trying to match a particular genome, the virologist is trying to create a new one based on the fragments they've been able to find and whatever guesswork can fill in the gaps. It's unlikely that whatever exact mix of symptoms and severities they're hoping for will show up directly in the samples they take, so they'll have to figure out what they can do with the fragments they do have.

To prevent players from gaming the system too heavily, the mappings between genes, and tags and modifiers should be randomized for each round. An experienced virologist should, nevertheless, be able to recognize some patterns - enough to offer a component of skill mastery, but not enough to allow bioengineering to devolve into copy-paste-this-genetic-code-to-make-superplague.

Once the bioengineered virus's genome is complete, the vaccinator can be used to produce viral load - but it will only dispense this in the form of a vaccine, in which the viruses are dead and incapable of multiplying. To get around this, the virologist must disassemble the machine, revealing a vial with a small amount of viral load as one of its components. Once they have the live viral load, they'll want to increase its yield by incubating it in a host body, or else it'll be too weak to survive for long enough to do damage. Syndicate members can, for a token amount of TC, obtain an immuno-suppressant pill. Their easiest option will be to take the pill themself and use their own body as a bioreactor. They could also kidnap some hapless victim and force-feed them the pill, but their efforts will be wasted if the victim dies, or if the victim escapes and runs to medbay. Smaller animals, such as mice, monkeys and kobolds, can be used to incubate the virus without the help of immuno-surpressants, but the smaller they are, the less viral load they will produce, meaning the plague-engineer will need to accumulate several of them and keep them under control and alive until the virus has gained a foothold.

Once the virus has incubated for long enough, the bioengineer can release their plague rats/victims/own sick self upon the station (if they're contagious) or else take the additional step of drawing blood and centrifuging it down to produce raw viral load in larger quantities.

Zombies and Romerol

The components of zombism could and should be picked apart and added separately as (severe) symptoms and transmission modes within this system, possibly weighted to have a greater chance of occuring together. Romerol then simply becomes a particular strain of disease suspended within blood. Zombie gameplay remains similar, in that the blood of zombies can be used by virology to help pin down the virus's genome and thereby develop a treatment. Initial Infected rounds, likewise, work basically the same way, with II players starting out with a certain amount of viral load in their bloodstream, a deficiency in antiserum production, and a particularly long time until onset of symptoms.

Game Design Rationale

An important part of this is that virologists don't get to just sit in their department and swirl test tubes or whatever. They have to get out there and track down the disease's source, which will generally require interacting with crew members as well as poking about in various parts of the station.

On the flip side, having a disease doesn't automatically mean running to virology - most diseases won't have enough impact to be worth doing anything about other than to carry tissues and maybe take off a layer of insulating clothing. Even somewhat more serious diseases might be manageable with regular medication, or topicals, or just gritting one's teeth/beak/whatever and tanking it. This means that having a disease is interactive for the victim; they're not just an object for virology to deal with. They have to make their own decisions about how and if to address their own symptoms, balancing the possibility that they've contracted something horrible that will lay waste to the entire crew with the probability that it'll go away on its own and be no big deal.

The different modes of transmission also lead to decision-making for infected crewmembers, since they have to figure out what they can and should do to prevent spreading their disease to others.

Since diseases cause problems through their secondary effects, in the form of symptoms, and since people will tend to get over any disease they can survive, there's flexibility and room for creativity in how players decide to handle a disease. Some diseases won't even be harmful or fatal - just inconvenient, or ugly. In which case, the whole crew might just end up going about their regular duties while trying to ignore their dripping pustules leaving puddles of yuk everywhere they go. This helps foster emergence as well as making diseases more interactive for non-viro crew. A good variety of symptoms, with potential interaction between them, can lead to emergence in its own right - any disease might present some novel and surprising conjunction of symptoms with unexpected consequences for the crew.

Roundflow & Player interaction

Though every round should have a mild disease or two, these should usually be ignorable or at worst inconvenient, whereas a severe disease counts as a round-defining major 'antagonist' and should be its own game mode.

In a regular round, there should be a constant, low chance for a mild disease to spawn as an event. These will infect a particular object or location (tile), gravitating towards the filthier parts of the station, and afflict themselves upon anyone who touches or stands on their source, spreading from there as per their mode of transmission. The disease should infect one to a few people and cause mild inconvenience at best. The exact nature of the disease should be random, with at least some possibility that it will be severe enough for virology to take an interest - maybe one moderate disease appears every three to five rounds on average. Good janitorial coverage can reduce this. Extremely filthy stations, on the other hand, might generate extra diseases in sufficiently disgusting areas.

In a Plague Round, there will be a severe disease that spawns within the first 10 minutes or so. Other minor diseases might also show up via events. Like mild diseases, the severe disease will have a particular object or tile that is its source, though it might slowly spread out from that source to help ensure that the crew doesn't totally miss it all shift. The only real difference between a severe disease and a mild one will be the numbers: Severe diseases can have higher mutation rates, a longer infection period before symptoms appear, faster progression once symptoms do appear, more serious symptoms, or most likely a combination of those.

Diseases start out small and weak, then escalate through spread and mutation. A quick and appropriate response on the part of the crew - not just virology, but the whole crew - can stop the disease in its tracks. On the other hand, the disease has the potential to lay waste to the entire crew and render the station downright uninhabitable if the crew can't stay ahead of them.

Department Interactions

  • Medbay will be the front line against any serious disease. Not just the virologists, but the doctors responsible for treating the symptoms; the chemists who will need to help produce and distribute treatments and vaccines; and the paramedics, who have to face the risks of going out into the infected parts of the station to recover downed crewmembers.

  • Janitorial staff will also play a surprisingly strong role, since their efforts to keep the station clean will also help curb the spread of the disease. Also, if a disease causes projectile vomiting or something, their efforts will be doubly vital.

  • Security might have to be responsible for keeping a panicking crew in order, or stopping people from breaking quarantine.

  • Command, likewise, might need to take charge of organizing the crew to act together against the threat of disease.

  • Engineering could help with creating quarantine zones. Atmos could help especially against airborne diseases with scrubbers and holofans. They might also be able to do things like cool down the station if the majority of the crew have terrible fevers.

  • Possibly, some symptoms could be worth research points to Science? Which might lead to some interesting conflicts of interest. They should also get some relevant technologies to research - faster disease diagnosers, bluespace sample swabs, better bio-suits and the like.

  • Cargo will have to keep the supply of sample swabs and latex gloves flowing in. They're also implicated as the department most likely to be responsible for spreading the disease all over the place. Salvage will be less directly involved, but might get to be the last few crew members left on their feet if they were away for the worst of the disease.

  • Service has the least to do, but might have to navigate delivering food and drinks to quarantined parts of the station.

Species Interactions

  • Reptiles, arachnids and vulpkanin, as well as any other predatory species, should have a stronger immune response to diseases that come from eating raw flesh or (for reptiles in particular) drinking floor blood. Flood blood consumption is, after all, an important part of reptilian culture. Fresh kills should also not count as unsanitary - only after they've sat for a bit do bacteria have a chance to develop.

  • Diona should have a stronger immune response to diseases that come from the floor, and especially from infected puddles. This is to help counterbalance the fact that they can't protect themselves with shoes.

  • Vox should have a stronger immune response across the board, but especially to diseases that come from trash.

Administrative & Server Rule Impact

There is some potential for griefing in the form of players deliberately trying to infect others. This is ameliorated in part by the fact that players potentially making bad decision about whether to get something looked at is deliberately part of the disease's challenge - a griefer and an irresponsible character don't look all that dissimilar in practice. Combined with the fact that disease sources are rare, unpredictable and invisible, and deliberate bioengineeering is difficult and slow, I think the potential for serious griefing is low.

Technical Considerations

The Disease Diagnoser Delta Extreme and the machine(s) that develops treatments and vaccines will need new UI. For treatments and vaccines, this could be as simple as a single text input to type the genetic code into, although it should probably also keep some record of previously-used codes and allow for quickly copying them into the text input for easy modification. The DDDE needs to indicate both viral and bacterial load: It would be fun to show bacterial load in the form of circular blots drawn on a virtual petri dish, with the presence and size of the blots indicating the amount of bacteria. Viral detection should also have something along those lines, although it's less obvious what.

There will need to be an additional component for holding viral/bacterial load on objects as well as players. For objects, this is basically just a string for the genome, plus an integer amount. For players, the extra process of experiencing disease progression and generating antiserum needs to happen, but a lot of that can mirror or directly use the existing metabolism system.

Addendum/Mediography

"Doomsday Book" by Connie Willis is a marvelous work of science fiction about a time traveller who is stranded in the dark ages, cut off from resources, and has to deal with a severe disease. I encourage anyone and everyone to read it for inspiration on how virology might work, and for a general example of what good storytelling about diseases can look like.

@github-actions github-actions bot added Design Related to design documentation for Space Station 14. English labels Aug 16, 2025
@Aearo-Deepwater
Copy link
Author

I'm currently putting together a rudimentary implementation of some of this as a proof-of-concept. I'll put a link here to the draft PR for that once it exists.

@Cadunkus
Copy link

Cadunkus commented Sep 8, 2025

I don't think diseases should spawn randomly. Disease gameplay always has sucked in SS13 to the point some old branches like TG have actually axed the system entirely.

What I think it should absolutely do is encourage healthy role-playing habits.
Rather than a disease spontaneously appearing in a completely random spot on the station or spawning in a random person, it should only appear in unsanitary conditions. Trash, spilled liquids, corpses, spoiled food, and especially miasma should become a spawnpoint for disease if left alone for long enough. Janitors become the first line of defense against infection, salvagers are inclined to not leave rotting space carp all around cargo, getting sick from prowling dirty old maintenance tunnels is a possibility, and lizards might refrain from eating dead rats off the floor like some feral animal.

Also you could promote diet. Vitamins found in fresh food boost the body's immune system to alleviate infection symptoms. Chefs might respond to a disease outbreak by serving tomato soup instead of the usual burgers menu and people are more likely to visit the canteen instead of surviving off of nutribricks and whatever junk food the vendors have.

Basically reward players for acting like a real person would.

@2DSiggy
Copy link

2DSiggy commented Sep 8, 2025

Trash, spilled liquids, corpses, spoiled food, and especially miasma should become a spawnpoint for disease if left alone for long enough.

Rat kings should apply an infection of some kind too when they bite someone. Would make them more dangerous as antag.

@EthanQix
Copy link

EthanQix commented Sep 8, 2025

Bleach should be used instead of Space Cleaner for disinfecting areas, as it currently has little use except as a poison.

@Cadunkus
Copy link

Cadunkus commented Sep 8, 2025

Bleach should be used instead of Space Cleaner

I think both should work. Maybe bleach works better.

@Aearo-Deepwater
Copy link
Author

I've been busy with stuff, but I haven't forgotten about this.

@Aearo-Deepwater
Copy link
Author

Making some additions based on the comments.

Lizards absolutely should eat dead rats off the floor like some feral animal, though. Saying this as a lizard main. Look, it's just our culture, okay? :godo:

@Aearo-Deepwater
Copy link
Author

I think this is basically complete. I just need to revise it so it flows a little better, and add some examples.

@ThanosDeGraf
Copy link

One thing I feel is missing/can be adressed with virology is expanding the medical records computer.

They should work like criminal records, where there'd be a PDA cartridge to track crew with a history of infection much more effectively, or look up possible immunities/vaccinations/allergies. There should also be functionality in the medical records computer to add new known infections by those with virology/medical access with information gained from the DDDE, possibly noting vaccines/treatment created for each.

@Aearo-Deepwater
Copy link
Author

@ThanosDeGraf I think some of that is out of scope for this design proposal, but allowing the medical records computer to track known infections and vaccines is a good idea.

I'll add in a bit about that.

As suggested by GitHub user @ThanosDeGraf
@Aearo-Deepwater Aearo-Deepwater marked this pull request as ready for review January 24, 2026 02:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Design Related to design documentation for Space Station 14. English

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants