Or, if you have Raiders, Renegades & Rogues, fit the holoemitter doodad with a forensic cleanser triggered to activate when the hologram shuts down (ie: has accomplished its task). That should give the cleanser ample time to scramble any DNA/energy signature evidence prior to an investigation. Of course, they could still trace the components, but no-one with half a brain thinks they can commit an perfectly unsolvable crime - the key is to have it unsolvable enough to get away with it...
------------------
"Captain Hunter, you are clearly outgunned. I suggest you surrender your vessel": Romulan Commander Terev, Imperial Warbird Senex
"Cmdr.Terev, you clearly have no idea we're carrying quantum torpedoes. I suggest you duck!": Capt.Matt Hunter, USS Tempest
Just played the episode over the week-end, so for those who are interested, a (long) update on how it went. I propably should submit it as an adventure in the tactical core, but am too lazy for it .
Players are a Trill science officer (with a few medical skills from his symbiont(sp?)), a Klingon security officer, a Cardassian exchange officer with an "eagle order" (intelligence) background ... and a few guest appearances from a Bajoran Vedek (who is really good a noticing small details or mood changes and such).
Setting is as above, on Empok Nor, in the middle of tense negotiations between the Federation/Cardassia and Romulans (who want their share of Cardassian space) and Klingons (who might settle on some compensations for the war damages). A Romulan spy is sent to the station, to disrupt the Federation-Cardassian entente by means of murders that will be imputed to each side. Of course, the murder weapon will be as discussed above in the thread.
The PCs are having a well merited time off in the holosuite from the bar that has just opened on the promenade. Suddenly the holoprogam fails and they end up very frustrated in the middle of the room. Enters Morn (one of the bartenders), who makes a lot of "not my fault" movements before explaining (off screen, of course) that the holosuite is quite new and that they are having troubles fixing it, that the PCs will get a rebate the next time they want a holosuite. Then the PCs are called to the command center / bridge, and forget about it. A few tense interactions with Federation and Cardassian officials later, a murder is discovered (the specialist who was installing the cetacean chief engineer's quarters). The Klingon and Trill (Security and Science) run to the habitat rings to investigate (and get sick).
End of the prelude.
Back to the murder scene. The victim has been teared apart by one slash of what looks like extremely long and powerful claws. Traces of powerful slashes can be seen on the walls or ground of the quarters as the victim probably tried to dodge. The type of the wound may indicate a kind of reptilian predator. Absolutely no DNA or cloth particles of the murderer can be found. Time of the death is 1 hour ago (coincides with the holosuite malfunction, but the PCs do not notice it).
The PCs almost immediately think of an isolation suit with special weapons, and the Cardassian tries to ring up some contacts to check on intelligence activity on the station. Then they pursue their inquiries, looking into the logs of everyone involved (they suspect a Gorn looking merchant (reptilian, strength, and claws)).
Later in the day, they go back to the bar, trying to get some info from both bartenders. At some point in the conversation, an infuriated and soaking wet dolphin (the chief engineer) comes down from the holosuite (having no quarters for now, it was getting a bit of his natural environment in the holosuite when everything disappeared (except the water that had been replicated around him)). Immediate comic relief, then the PCs go on about their inquiries.
Shortly thereafter, a second victim (starfleet again) is discovered. A very foggy image on a security camera that was a bit further away shows a huge clawed arm gripping the victim. It has metal like shining scales. Most Cardassians involved link this with a monstruous bogeyman from their childhood, the Mumak. Research shows that this is an ancient belief that dates back to the time when the Cardassian folk was more religious, and indicates a kind of demon of vengeance that appears to punish oppressors when Cardassian peoples have been harmed. Rumor spread that a vengeful Cardassian is runing amok on the station, murdering non Cardassians at random.
Things go on a bit. Each time a new victim was going to be discovered, I made sure that they heard about a holosuite malfunction (riot in the bar, starfleet or cardassian officers complaining, the PCs going back to the holosuite to see the end of their program, and so on), and enabled to trace the time of the death of the victim. Unfortunately (for them), none had the idea to investigate the malfunctions nor to link both facts.
Then a Cardassian is murdered. Things seem to clearly identify a Klingon as the murderer, even if no traces of metal can be found, possibly indicationg a specially manufactured Bat'leth. Good news is that the PCs have a very believable suspect: An extremely violent Klingon mercenary (who even tries to beat the hell out of the Klingon security officer). They promptly incarcerate him. Riots begin on the station between Cardassians and the few Klingons present on the station.
However, murders continue to happen (mumak wounds), then the Klingon suspect escapes (killing a Cardassian security officer in the process, same bat'leth wound with no metal traces). Starfleet sends intelligence officers to replace the PCs (the Klingon officer is even suspected of helping his fellow Klingon escape). It is not until the PCs are attacked (the mumak nearly kills the Klingon PC who only narrowly escapes thanks to a turbolift, and the Cardassian PC has to run for his life chased by the klingon murderer), that they begin to guess something. Tricorder read absolutely nothing on the attack spot, only minutes after the attack. A beast that should have difficulties crawling around in the stations corridors appeared almost soundlessly behind the PCs, and then escaped in a matter of seconds. Moreover, the slashes of both attackers were a bit mechanical (very good perception roll). And suddenly (after a few guesses that were promptly proved wrong), there was light . They linked it with the holographic malfunctions. They began to suspec the bartenders, then found out the holomurderer programs had been sent from inhabited quarters on the habitat rings. However, the Romulan spy had time to beam on a cloaked ship nearby and escape ... .
All in all, the episode was much fun to play. It also was a nightmare for the Gamemaster, because I had to find ways and ways and even more ways to report holosuite malfunctions without it being way to obvious. Same problem with time of death that had to be pinpointed so that the players had a chance to discover the truth. Actually, it helped much to have interesting and colourful bartenders because the players went more naturally to the bar.
Lastly, a hint to the GMs or spies that would like to use a holographic murder weapon: beware of security camera, they can be a real problem at times . Always take time to think of a way to disable them (a replicated decaying Vole in the circuitry does miracles ).
------------------
Sometimes it's better to light a flamethrower than curse the darkness.
-- (Terry Pratchett, Men at Arms)
[This message has been edited by Calcoran (edited 06-25-2001).]
Calcoran, I really like the clue of having holosuite malfuctions being inserted as comedic relief just before the murders are reported. The hard part about having a murder mystery scenario in an RPG is fitting in the clues naturally. The way you did it really fits the source material- I can easily see that as a DS9 episode, and it works well in an RPG, being obvious in retrospect, possible to solve, but not being too obvious.
Sounds like a great time, thanks for posting the episode summary. I just might use that somewhere along the line.
Registered User
).
.
).
Posting Permissions
Reply With Quote