Before MidnightGame Studio
Illnesses can develop through normal Trenchport gameplay, close contact with contagious players, dangerous heat, animal handling, or the private Intimacy sexual-health flow. This guide explains what can happen, how exposure works, and what players can do after symptoms begin.
With Wellness enabled, the Trenchport cloud can record background illness exposure from qualifying gameplay. Automatic conditions begin hidden and incubating. Once symptoms appear, the HUD gives private symptom information without immediately naming the condition. Hospital diagnosis reveals what the character has and which treatment applies.
Automatic gameplay exposure is disabled when Wellness is off. Staff-created medical conditions and private STI processing follow their own medical flows.
A player can have only one active/incubating automatic condition and can receive only one new automatic condition in a rolling seven-day period.
After recovering from an automatic condition, that same condition has a 30-day automatic exposure immunity window.
Not every catalog illness is attached to a random background trigger. The routes below are the current automatic or private transmission paths used by the system.
Two Wellness-enabled current-HUD players must remain within 3 meters continuously for 60 seconds. Only an ACTIVE contagious condition can spread; incubating conditions do not spread yet.
Rummage results can carry sanitation or food-related risk.
Fishing contact and gutting can expose players to Bacterial Infection.
Cock activities are animal-contact exposure only and do not add heat-exertion points.
Weather alone never makes a player sick. The Trenchport cloud combines real Mobile/KMOB heat conditions with exertion from rummaging, fishing, fish gutting, and combat/hunting.
Chlamydia, Gonorrhea, and Syphilis are transmitted only through the completed private Intimacy sexual-health flow when a partner is affected. Condoms reduce risk; Birth Control Pills do not.
Durations below use the current seeded defaults. Automatic activity exposure may use a different severity, so a specific character's recovery time can differ.
Symptoms: Runny nose, sore throat, coughing, and mild fatigue.
Symptoms: Fever, body aches, chills, coughing, and heavy fatigue.
Symptoms: Nausea, stomach cramps, weakness, and dehydration.
Symptoms: Nausea, stomach pain, reduced appetite, and fatigue.
Symptoms: Pain, fever, swelling, and worsening fatigue.
Symptoms: Itching, irritation, swelling, and difficulty concentrating.
Symptoms: Strong thirst, headache, weakness, and reduced stamina.
Symptoms: Dizziness, heavy fatigue, thirst, and weakness.
Symptoms: Coughing, chest discomfort, shortness of breath, and fatigue.
Symptoms: Fever, coughing, body aches, shortness of breath, and heavy fatigue.
These three conditions are handled through the completed Intimacy flow only. They are created active and diagnosed immediately rather than using the generic automatic-incubation flow.
Possible discomfort, unusual discharge, or no obvious symptoms.
Possible discomfort, irritation, unusual discharge, or no symptoms.
Possible sores, fatigue, rash, or no obvious early symptoms.
Automatic conditions stay hidden by name while incubating and undiagnosed. Once incubation ends, symptoms become active but the diagnosis remains private until the medical system identifies the condition.
When Ambient Symptoms are enabled in Config, active respiratory/allergy conditions can drive automatic coughing, sneezing, or sniffing behavior through the HUD. Turning Ambient Symptoms off silences those automatic RP sounds without curing the illness or removing its mechanical effects.