2,213
edits
Engineer Simming Guide: Difference between revisions
merged content from Engineering now under Away Mission
mNo edit summary |
Ethanbrice (talk | contribs) (merged content from Engineering now under Away Mission) |
||
| Line 37: | Line 37: | ||
We wouldn't call this "ongoing" if it only happened once... | We wouldn't call this "ongoing" if it only happened once... | ||
==Away Missions== | |||
Typically engineers are not required for Away Team missions unless there is some kind of technology involved - powering up an alien ship, trying to repair another Starfleet vessel, et cetera. Occasionally you may get to go just because the experience will do you good. One thing to always remember: even though you're an engineer, you are not a god. Trip Tucker nearly died during one away mission. Scotty never died on an away mission because he rarely ever went on away missions, but he could have been seriously hurt or killed at any point. La Forge had his share of problems. O'Brien did, too. And Torres had plenty to worry about on her missions. To put it simply, you have to rely on others just as much as they do you. | |||
For example. You've arrived at an alien planet and you're trying to get their equipment working, but you can't read the script. Your tricorder won't work, so you should ask your science or comm officer that is accompanying you to translate it for you. Or some other situation. | |||
Being an engineer is easy. Being an effective engineer is what's difficult. | |||
==The Chief Engineering Officer== | ==The Chief Engineering Officer== | ||