Scenario Early Evaluation Exercise #2170
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This scenario is designed to train from one to sixteen player ships simultaneously. Each player ship will be assigned a friendly home base. The scenario tasks are relatively simple and each console gets a message explaining the task and their contribution to the task. At the end of each task, an evaluation may be viewed by the players or the GM. The scenario provides objective evaluation information, mostly based on how long each task or subtask took. Some subjective evaluation questions are suggested in the GM evaluation for each ship.
This scenario is based on the "Earn Your Wings" scenario written by Kilted Klingon. The original target player group consisted of three to six player ships with either young scouts or coworkers as the bridge officers. For the event, an After Action Report is intended for each player ship. An observer should be providing the subjective content along with the objective content provided by the scenario via the GM screen.
The Tasks Within the Scenario
Dock with Station
Sounds easy (and it is). However, Relay must contact the station to determine the station docking protocol. The protocol requires actions by Engineering and Weapons before the player ship will be allowed to dock.
Scan Freighters
Scan three freighters. Report the ship type of each freighter to the friendly station. Using the deep scan information, report the strongest defensive shield frequency to the friendly station for each freighter.
Destroy Enemy Freighter
Of the three freighters scanned, one will be an enemy. Destroy that freighter. Player's beam weapons will not be effective, so they will be forced to use broadside HVLIs to destroy the freighter.
Help Distressed Freighter
An independent freighter will report engine trouble. The players will need to help. This will involve finding the freighter, talking to the freighter, protecting the freighter from marauding Exuari, scanning the freighter to determine engine damage, reporting engine damage details to the friendly station, picking up parts from the friendly station, providing parts to the distressed freighter. These sub-tasks won't necessarily be performed in this order. Some decisions will need to be made regarding task prioritization.
Research Orbiting Bodies
The planets and moons in the central part of the playing area are orbiting in an unusual fashion. The players will be asked to gather data on these orbiting bodies. This is probably the most dangerous task since bumping into these planets and moons severely damages the player ship (unlike the typical default behavior in other EE scenarios).