Skarda's Mirror

Skarda's Mirror is an adventure module for the Dungeons & Dragons fantasy role-playing game. It was published by TSR in 1987, and designed by Aaron Allston. Its cover art is by Tim Hildebrandt with interior art by Al Williamson and Jeff Easley, and cartography by Dave S. LaForce, Dennis Kauth, and David C. Sutherland III.. The module's associated code is X12 and its TSR product code is TSR 9188. This module was developed and intended for use with the Dungeons & Dragons Expert Set and Companion Set rules.

Skarda's Mirror
CodeX12
TSR Product Code9188
Rules requiredD&D Expert Set
Character levels5-8
AuthorsAaron Allston
First published1987
Linked modules
X1, X2, X3, X4, X5, X6, X7, X8, X9, X10, X11, X12, X13, XL1, XSOLO, XS2

Plot summary

In this scenario, the player characters pass through a magical mirror to save victims who are trapped in a "pocket universe" within the mirror; the hard part is getting back out again.[1] The module includes pregenerated player characters and players' aids.[1]

The wizard Skarda and his band of raiders once terrorized the rural settlements of the Grand Duchy of Karameikos, kidnapping everyone and taking their treasure. By chance, he was discovered by famous adventurer Lord Retameron in Specularum. In the aftermath of the raid, Skarda (alias Mallek) was left trapped in his burning house. A search of the wreckage found papers describing his role in the raids and outlining a coup against the Duke, and a magical mirror of great power. Retameron kept the mirror and brought it to his tower. One night, both he and his wife Halia gazed into the mirror and disappeared, and in their place appeared large baboon-like creatures with huge teeth that attacked everyone in sight. So far, no one has come out of the tower alive. Retameron's father finds the player characters and pleads with them to enter the tower and rescue his son.

Publication history

X12 Skarda's Mirror was written by Aaron Allston, with a cover by Tim Hildebrandt and interior illustrations by Al Williamson, and was published by TSR in 1987 as a 48-page booklet with an outer folder.[1]

Reception
gollark: > 5. .net platform is cracker / hacker friendly Any program running on the client can INEVITABLY be reverse-engineered. Do not rely on it not experiencing that, because you will fail.
gollark: > 4. XAML - the incredibly messy UI technologyPerhaps, but this is not a *language* thing.
gollark: > 3. Garbage collector and memory leak detection tools?Again, not sure if anyone actually runs into this sort of issue in practice.
gollark: > 1. Performance penalties.> [some rambling about C++].NET is generally pretty much *fast enough*. If your application somehow hits performance bottlenecks, rewrite the slow bits in native code, don't just immediately take a development speed hit.> 2. Need to interoperate with C++ / Native (Windows) API’sI don't know how often you actually need to bind to a native API not wrapped by .NET or a third-party library, but you can do it, it's just annoying - but probably less than using C++ for everything!
gollark: This is outrageous pro-C++ anti-C# propaganda.

References
  1. Schick, Lawrence (1991). Heroic Worlds: A History and Guide to Role-Playing Games. Prometheus Books. p. 149. ISBN 0-87975-653-5.


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.