Car Collision is a Generic Call Incident featured in 911 Operator. This call has two different storylines involving a collision between two cars. In one case the collision happened the previous day and can be safely ignored. In the other, the incident is in progress and there may be injured involved, cars to clear out of the street, or even someone to arrest.
As a Generic Call, Car Collision may be triggered at any time during Free Play mode.
During Career play, this call may occur multiple times.
NOTE: There are two different script files for this call, and both are included with the game. The differences between them are very minor, and solely restricted to the dialogue text. Only one of these calls will be triggered during Career Play, but more research is required to figure out whether both can be triggered "naturally" during Free Play.
Opening Lines[]
| Speaker | Line |
|---|---|
| Operator | "911, what's your emergency?" |
| Caller | "Hello, there was a car collision." |
Randomized Plot Structure[]
This call has two possible plots, determined by a randomized factor which is only decided when it becomes relevant. The first plot is pretty straightforward (the call will ultimately be ignored), but the second is quite complicated: it contains multiple randomized factors which can cause the incident site to change rather radically. The number of Reputation points awarded for this call is directly tied to the severity of the incident.
The main plot divergence is structured as follows:
Intro: All plots begin with the standard request for an address, followed by asking the caller when the accident happened. This will already encounter a random factor.
Plot 1: The caller has a 16% chance to report that the collision occurred the previous evening. In this case, the call is not an emergency and will conclude with no Reputation points awarded. It can then be safely ignored.
Plot 2: The caller is interrogated about the situation on site, including the number of injured persons, the severity of injuries, who was responsible for the collision, and whether either of the crashed cars is blocking traffic. Each of these is a randomized factor, with three possible responses that modify the on-site elements as well as the flow of the conversation itself.
Reputation[]
| Dialog Choice | Resolve Call Reputation | Ignore Call Reputation |
|---|---|---|
| (ANSWER CALL) | +1 | |
| Incident occurred yesterday (16% chance) | -1 | Set to 0 |
| One person is injured (33% chance) | +1 | |
| Two people are injured (33% chance) | +2 | |
| Injured person heavily bleeding (33% chance) | +1 | |
| Both cars are smashed (33% chance) | +1 | |
| Maximum possible: | 5 | No Penalty |
Ignoring the Call[]
The call can only be safely ignored (no penalty) if Plot 1 has triggered. Otherwise, there is no way to ignore this call without suffering a penalty.
Intro[]
The first part of this incident call is identical regardless of whatever plot unfolds. It is described here as an entry-point into the five different plots. The plots fully begin to diverge only once the caller is asked when the incident occurred.
Summary[]
A man calls 911 to report an accident between two vehicles. After ascertaining the location of the accident, the operator asks when the accident occurred.
Optimal Conversation: Intro[]
| Speaker | Dialogue | Extra Effects |
|---|---|---|
| Operator | 911, what's your emergency? | Reputation +8 |
| Caller | Hello, there was a car collision. | |
WHERE?
| ||
| Operator | Where did the collision happen? | |
| Caller | Around <address> |  Location discovered.
|
WHEN?
| ||
| Operator | When did it happen? | |
| Caller | Yesterday evening. | 16% chance. Reputation -1 Skip to Plot 1 conversation. |
| Just a moment ago. | 42% chance. Skip to Plot 2 conversation. | |
| 5 minutes ago. | 42% chance. Skip to Plot 2 conversation. | |
Plot 1: No Emergency[]
This plot can only unfold if the Intro ended with the caller saying that the collision occured the previous evening.
There is a 16% chance of this being the chosen line.
Summary[]
Having realized that the collision occurred many hours ago, the operator tells the caller that he should not call 911 about non-emergencies. The caller tries to argue, but the operator insists that he should go to a police station instead.
The caller hangs up, and the call is summarily ignored.
Optimal Conversation: Plot 1[]
| Speaker | Dialogue | Extra Effects |
|---|---|---|
| Continuing from Intro conversation... | ||
| Operator | Sir, you don't call 911 for an accident that happened yesterday. | |
| Caller | But the car is crashed and bumper is off.... | |
| Operator | Sir, please contact your body shop or go to the nearest police station if you have any complaints. | |
| Caller | Ok... bye. | Call ended. |
At this point, click "IGNORE" to dismiss the call at no cost to your Reputation.
Plot 2: Incident in Progress[]
This plot should only be followed if the caller reports that the collision happened a short time ago - either 5 minutes or just a moment ago.
There is a 42% chance of either option being selected at random (total 84%), and there is no actual difference between them.
Summary[]
Realizing that the incident is currently in progress, the operator asks the caller a series of questions to try and understand the situation.
First, the operator inquires about the number of injured on the scene. The caller reports, randomly, either zero, one, or two injured passengers.
If there are any injured people on site, the operator inquires about the severity of their injuries. The caller may report that neither is severely injured, but it's also possible for him to report that one passenger has broken his leg, or that he is feeling severe pain in his stomach. If so, the operator will instruct the caller to make sure they don't move.
Next, the operator asks who was responsible for the accident. The two drivers might still be arguing about this matter, indicating that there is no one clearly responsible. However, the caller may instead confess that they are responsible, or report that the other driver is drunk - making them the responsible party. If either driver is to blame, the operator decides to send a police officer to fine the responsible party for their actions.
Finally, the operator inquires whether the crashed cars are blocking traffic. Once again, the caller might respond that neither car is blocking traffic, that one car is, or that both cars are blocking traffic. If any blockage is reported, the operator decides to send firefighters to the scene to remove the offending cars and allow traffic to resume.
The operator instructs the caller to remain where they are while units make their way to the site to handle the various issues that were reported in the conversation.
On Site[]
|
CAR COLLISION | |||||
|---|---|---|---|---|---|---|
| Element | Name | Actions | Notes | |||
|
Caller | 
|
Interrogate | Always white male. | ||
| Initially disabled elements (may become active depending on conversation or other events) | ||||||
|
|
Driver |
|
Arrest Chance | 50% | ||
|
Fight Risk | 10% | ||||
|
Passenger (1) | 
|
Hit Points | 80 | ||
|
|
Passenger (2) |
|
Hit Points | 80 | ||
|
Smashed car (1) | 
|
Tech Work | 100 sec. | ||
|
|
Smashed car (2) |
|
Tech Work | 100 sec. | ||
- By default, the only element at the scene will be the caller himself, who must be questioned by the police. However, random factors can radically alter the number of elements appearing on the scene, as well as the particular properties of each element.
- The caller has a 16% chance of ending up being responsible for the accident. In this case, he will need to be fined for $2,000 instead of questioned. The script also calls for a 20% chance of arrest, but the game will never allow him to be arrested because of the fine.
- The other driver has a 33% chance of being responsible for the incident. If so, he appears on the scene, and must be fined for $5,000 due to drunk driving. He is also set to have a 50% arrest chance and a 10% chance of starting a fight, but again, none of this will happen because of the fine.
- Passenger (1) has a 66% chance of appearing on the scene, requiring medical treatment but not necessarily transport to hospital. If this passenger is the only injured person on site, they have a 33% chance of bleeding mildly (-0.1/s) and 33% chance of bleeding more heavily (-0.2/s).
- Passenger (2) has only a 33% chance of appearing on the scene, and will only require treatment - no transport to hospital.
- There is a 33% chance for one smashed car to appear on the scene, and 33% chance for both smashed cars to appear. Each is an obstacle requiring 100 seconds of Tech Work. The injured passengers (if any) are not blocked by the cars, so medics don't have to wait until starting treatment.
Optimal Conversation: Plot 2[]
| Speaker | Dialogue | Extra Effects |
|---|---|---|
Continuing from Intro conversation...ANY VICTIMS?
| ||
| Operator | Are there any injured? | |
| Caller | No, no one. | 33% chance. |
| Yes, one person is injured. | 33% chance. Reputation +1. Enable Passenger (1).
| |
| Yes, two people have some injuries. | 33% chance. Reputation +2. Enable Passenger (1).Enable Passenger (2).
| |
WHAT INJURIES?(Only available if the caller reported one or more injured passengers) | ||
| Operator | Can you tell what kind of injuries they have? | |
| Caller | Just some scratches. | 33% chance. |
| I think one of the passengers broke his leg. | 33% chance. Passenger (1)  Bleeding at -0.1/s.
| |
| One of the passengers says his stomach hurts really bad. | 33% chance. Reputation +1. Passenger (1) Bleeding at -0.2/s.
| |
DON'T LET THEM MOVE(Only available if the passenger is reported to be more than lightly hurt) | ||
| Operator | Ok, just make sure they won't move until an ambulance arrives. | |
| Caller | Sure... | |
WHO CAUSED IT?
| ||
| Operator | Who has caused the accident? | |
| Caller | We are still arguing about that, can you send a policeman to figure it out? | 33% chance. |
| I did... | 33% chance. Caller  Fine set at $2,000. Caller  Arrest Chance 20% (unused!)
| |
| The other driver, he's obviously drunk. | 33% chance. Enable Driver. Driver Fine set at $5,000.
| |
HOW'S THE TRAFFIC?
| ||
| Operator | Are any of the vehicles blocking traffic? | |
| Caller | No, they are not. | 33% chance. |
| Yes, one of them cannot be moved. | 33% chance. Enable Smashed car (1).
| |
| Yeah, both of them are completely crashed. | 33% chance. Reputation +1. Enable Smashed car (1).Enable Smashed car (2).
| |
| (This final dialogue occurs automatically once all other choices have been exhausted.) | ||
| Operator | All right sir, please wait for the emergency services to arrive. | |
| Caller | Ok, thank you! | Call ended. |
Choices to Avoid[]
There are no wrong choices in this conversation. You will have to exhaust every conversation option before the final two dialogue lines trigger automatically.
After Action Report[]
| Condition ID | If... | After-Action Report Text |
|---|---|---|
| Yesterday | Caller reports that the accident took place the previous evening. (16% chance) | "The accident took place yesterday and there was no need of intervention." |
| Injur | Caller reports one passenger injured. (33% chance) | "One person was injured in the result of the car crash." |
| Injur2 | Caller reports two passengers injured. (33% chance) | "Two people was injured in the result of the car crash." |
| Blocking | Caller reports one car blocking the road. (33% chance) | "One of crashed vehicles was blocking traffic." |
| Blocking2 | Caller reports two cars blocking the road. (33% chance) | "Crashed vehicles were blocking traffic." |
| Drunken | Caller reports the other driver was drunk. (33% chance) | "A driver who caused a collision was under influence of alcohol." |