- "This crash was. . . Can you please send someone to help these poor people?"
Railcross is a Call Incident in 112 Operator. With a Call Level of 0, it is allowed to trigger on any Duty that allows random Call Incidents, including the very first Duty. This call only spawns a single incident site, but the nature of the site could vary greatly depending on the outcome of the conversation - requiring either police response, firefighter response, or both. The call dialogue is completely predictable (no randomized responses from the caller).
The incident involves a man calling to report that his car is stuck between the two barriers of a rail crossing - and a train is rapidly approaching. The operator must decide whether to get the man or his car off the rails, and this influences the necessary response from emergency units. Police may have to either question the caller or recover his dead body; whereas firefighters must either remove the car wreck or fix the barriers. In the best case scenario, only police are needed.
For the best solution to this call, see this guide.
Opening Lines[]
| Speaker | Line | |
|---|---|---|
|
Operator | 112, what's your emergency? |
|
Caller | I'm stuck on the railroad crossing. What do I do? |
Trigger Conditions[]
The Railcross incident has a Call Level of 0. This means that the call may randomly happen on any Duty - including the very first one - if the game decides to trigger a random Call Incident on that Duty.
Once this call is triggered, it will not be triggered again for the remainder of the game - except in Freeplay mode if "Repeated Calls" have been enabled.
Structure[]
The Railcross incident is a Call Incident, which begins with a phone conversation with a citizen. The call is completely predictable: it contains no randomized responses from the caller, and the outcome depends entirely on choices made by the operator; the same choices will always lead to the same results.
This incident contains only a single scene, which becomes visible on the map if the caller is asked for their address. If the caller survives the incident, he will always give his address at the end of the conversation. If he doesn't survive and the address hasn't been acquired during the conversation, the call can be traced instead, which takes approximately 450 real-time seconds (on SLOW game speed).
The nature of the scene is highly dependent on the operator's dialog choices. These will determine whether the man is alive or dead; whether the car is wrecked and must be towed away; and whether the rail crossing barriers have been damaged and require repair. In the best case scenario, the man is alive and no repairs or towing are needed.
Other than that, there is no negative effect for any choices made during the conversation - they only determine the amount of work required to resolve the scene.
Call Summary[]
The Railcross incident begins with a man calling 112 to report that his car's engine died while crossing a railway, and is now the barriers have come down and his car is stuck between them. A train can be heard approaching.
The operator, realizing the danger to the passengers on the train, asks the caller to get back into his car and try turning it on again. When the caller does so, the engine won't start, but the operator advises the caller to turn off his headlights and radio and try again. The engine finally starts, and the operator tells the caller to drive his car just off the rails.
The train passes without a collision, and no damage is done. Police arrive to extricate the caller and his car from the crossing.
Negative Choices[]
Technically speaking, there are no "wrong" choices, since the Reputation Reward for this call doesn't change depending on its outcome. Nevertheless, there are several outcomes that are objectively worse:
- The operator can just tell the caller to abandon his car and run. This causes a collision in which the car is destroyed. Fortunately, none of the train's passengers are hurt.
- The operator can urge the man to start his car's engine again and again, without providing a smart suggestion on how to get it to work. This results in the train colliding with the car, killing the man and leaving a wreck on the rails.
- Once the caller gets his engine started, the operator can advise him to gun it through the barriers. While the man and his car are saved, and no collision occurs, firefighters now need to repair the barrier as soon as possible to prevent any more accidents.
Each of these outcomes increases the amount of work required at the scene, compared to the "optimal" solution where only a basic police response is needed.
Railcross Scene[]
The Railcross incident contains only a single scene, which is hidden at first. This scene only appears on the map once either of the following conditions is met:
- The caller was asked for his location.
- The caller survives, and the end of the conversation is reached.
- About 450 seconds of real-time have elapsed (on SLOW game speed) from the moment the conversation began.
This scene always spawns on a rail crossing. The location of all rail crossings is derived from real-world map data.
The scene contains either a police element or a dead body, and sometimes one firefighter element. This all depends on the outcome of the phone conversation.
Description[]
This scene takes place at a rail crossing. The scene's layout strongly depends on choices made during the phone conversation. There are four different elements that could be present:
- The caller, alive and well, requiring questioning by police.
- The caller's dead body, requiring processing by police or medics (a trivial job).
- The caller's destroyed car, a Tech element requiring 550 Work Seconds to clear away.
- The destroyed rail barriers, a Tech element requiring 200 Work Seconds to repair.
The caller will only be dead if he was told to try starting his engine, but not given constructive advice on how to do so.
The destroyed car will always be here unless the caller was given good advice on how to start the engine.
The broken rail barriers will only be here if the caller was instructed to drive through them to escape.
Resolution[]
This scene must be reached within 1,000 seconds of real time (on SLOW game speed) or it will automatically fail the entire incident.
The Reputation Reward for resolving this scene is +6.
The penalty for ignoring this scene is -6, subject to multipliers from the current difficulty setting.
Despite the very different outcomes possible for this incident, none of the dialog choices will change the reward nor the penalty in any way.
Police[]
|
Firefighters[]
|
|
Medical[]
|
After-Action Report[]
| Condition | Text |
|---|---|
| Opening Lines spoken | The operator was called by a man trapped with his car on the railroad tracks |
| BREAK THE BARRIER | After several trials the caller managed to turn the engine on and force the barrier, thus saving himself and the people on the train |
| TRY AGAIN | The caller died, because he didn't manage to turn the engine on and he couldn't stop the train from crashing into his car |
| JUST RUN | The caller managed to save his life, but the train hit the car |