Sounds good to me. When I start to work on a new fanfic, I think of what ship I want (so I know what crew to assign, eg a Sabre-Class with 40 crew is doubtful to have a counsellor on board for patrol missions) then look at who those aboard are that I can tell fun/interesting stories with. Once I have them, then I go back and look at tech specs, bot mostly just the basics: warp capabilities, armament, dimensions, etc.It's helpful not to lose sight of the forest because of the trees, IMO. I think it's real easy to get so caught up in the technical aspects of the ship, Starfleet, etc., that the story and characters are drowning in them. Details are important, but too much detail can be as bad (if not worse) as not enough detail because it can bog down a story. Not everything requires a full page or even a full paragraph explanation.
Characters, characters, characters… never forget they’re the underpinning of any good story. The reader has to be drawn in to your characters, to their stories, their hopes, fears, failures and triumphs. All the cool space battles and super-starships in the cosmos won’t make a bit of difference if your characters are paper-thin and the reader can’t identify with them.
Another thing I recognized upon watching Abramstrek 1... write the story for the real world first, and then translate it into space. If it makes sense in a real world scenario, it will make sense in sci fi as well.
nuKirk's journey from cadet to captain is completely ridiculous if you apply it to the real world. A madman with his own ship (let's say a submarine), and an arsenal of nuclear weapons has destroyed a Navy ship, and killed cadet Kirk's father in the process. Years later, he shows up again, and attacks a major city. Naval cadet Kirk is suspended for cheating on a test, but illegally boards the aircraft carrier Enterprise which is sent to the rescue mission. He runs into the command center and confronts the commanding officer (Pike) with his hunch about how it's the madman. When the Enterprise arrives, the rest of the fleet is already destroyed. Pike promotes cadet Kirk to First Officer (!). To save the ship, Pike takes a helicopter to the madman's ship, but drops Kirk and a couple of others in diving suits into the water to stop the nuclear bomb. Pike gets captured, Kirk fails the mission, and the bomb goes off. The city is completely destroyed. The Enterprise could escape the blast zone just in time.
Now, the actual First Officer (Spock) lost his mother in the explosion. He actually left his post (!), took a helicopter to rescue her, but she didn't make it. There is a heated confrontation with Kirk, who wants to go after the madman's submarine immediately. Spock exiles Kirk on a rescue boat on a deserted island (!), instead of putting him into the brig. The Enterprise heads off to meet up with the rest of the naval fleet.
Kirk manages to reach the outpost on the island. He steals a helicopter together with another exiled dude (Scotty) on the outpost, and catches up with the Enterprise. When they are caught, they are taken to the command center. There, Kirk causes a serious meltdown in Spock. Now, the entire crew of the aircraft carrier is completely baffled, no command hierarchy exists (!), so Kirk takes command of the whole thing. And the other dude from the island outpost is promoted to chief engineer of the aircraft carrier (!).
Eventually, Kirk and Spock do a sneak attack on the madman's ship before he can destroy yet another city, rescue Pike and detonate one of the nuclear bombs to destroy the ship.
After that, Kirk is promoted to commanding officer of the aircraft carrier.
This is an absolutely ridiculous story.
Another thing I recognized upon watching Abramstrek 1... write the story for the real world first, and then translate it into space. If it makes sense in a real world scenario, it will make sense in sci fi as well.
AND SO, IN EVERY SCENE OF OUR STAR TREK STORY...
... translate it into a real life situation. Or, sometimes as useful, try it in your mind as a scene in GUNSMOKE, NAKED CITY, or some similar show. Would you believe the people and the scene if it happened there?
IF YOU'RE ONE OF THOSE WHO ANSWERS: "THE CHARACTER ACTS THAT WAY BECAUSE IT'S SCIENCE FICTION", DON'T CALL US, WE'LL CALL YOU.
Another thing I recognized upon watching Abramstrek 1... write the story for the real world first, and then translate it into space. If it makes sense in a real world scenario, it will make sense in sci fi as well.
Exactly. In fact, Gene Roddenberry said as much in the original TOS Writers' Guide:
AND SO, IN EVERY SCENE OF OUR STAR TREK STORY...
... translate it into a real life situation. Or, sometimes as useful, try it in your mind as a scene in GUNSMOKE, NAKED CITY, or some similar show. Would you believe the people and the scene if it happened there?
IF YOU'RE ONE OF THOSE WHO ANSWERS: "THE CHARACTER ACTS THAT WAY BECAUSE IT'S SCIENCE FICTION", DON'T CALL US, WE'LL CALL YOU.
It's amazing how many professional and fan writers ignore this very basic advice that's as old as Star Trek itself. It's one reason I think the TOS Writer's Guide should be required reading for anyone writing any kind of Star Trek story.
We use essential cookies to make this site work, and optional cookies to enhance your experience.