By Monte Cook
64-page event book
Table of Contents
Free web enhancement: "Thomad the Preserver"
Other links for this book: http://www.montecook.com/archive_mpress.html#R4AG
A god dies. The faithful mourn. Others rejoice. A few see opportunity. All is forever changed.
Kill a God in Your Game!
Malhavoc Press proudly presents the event book, a new concept in roleplaying products by 3rd Edition codesigner Monte Cook. Requiem for a God postulates that a major event has taken place in your campaign -- the death of a divine power.
This d20 event book has everything you need to introduce the death of a divine power into your game. Game master notes detail the death’s repercussions on your campaign and new prestige classes tap into the departed god’s power. Characters can wield artifacts made of god-relics, as well as spells fueled by lingering divine essence. Meanwhile, dark creatures born of the god’s passing challenge adventurers of all levels. Tie-in scenarios feature power-mad villains seeking to hoard their new might, while cosmic forces move to realign the balance.
What's an Event Book?
If you are looking for a how-to guide for implementing a major event into your campaign, the event book line is for you. Requiem for a God is merely the first of many such products. Each takes a major event that could have interesting repercussions on your campaign and examines it thoroughly from every angle. It provides DM advice on staging the event, involving the PCs, and making the necessary changes to the campaign that result naturally from the event. Each event book also includes new NPCs, organizations (usually with associated prestige classes), and even rules, spells, magic items, and monsters that might be involved with the event. In short, it's everything you need to make that event a part of your own campaign. The focus here is that it is your campaign -- the event book is merely a guide. It doesn't force you into structured plots or leave you with no idea of what happens next.
For printing and navigation tips, be sure to read the readme file.