I love the idea of using Performance as an Arcane Skill while also being able to integrate Tests and provide Support while performing. Pair this with most of the Social Edges in the core rules, and you've got a highly functional bard in your Savage Worlds game. I personally love playing support roles in RPGs, and I'll definitely be using this.

I love the idea of using Performance as an Arcane Skill while also being able to integrate Tests and provide Support while performing. Pair this with most of the Social Edges in the core rules, and you've got a highly functional bard in your Savage Worlds game. I personally love playing support roles in RPGs, and I'll definitely be using this.

When I first read over The Warrior Adept, I found myself excited by each feature as I read through it. By the end, I was outright giddy. Ron nailed it with this product.

This fits snuggly into any setting that features individuals who can manifest a psychic/magic weapon from sheer will and who can enhance their own abilities with powers. The options for enhancing the Spirit Weapon are flexible, allowing players to customize it to suit their combat styles.

Conveniently, I'm kicking off a new Savage Eberron campaign, and I'm including this as an option for anyone who wants to play a kalashtar psychic warrior/soulknife.

If you love the idea of wandslingers in Eberron and want to play that concept in Savage Worlds with a new Arcane Background and supporting Edges, Hindrances, and optional rules, get a copy of Wand Magic. The Wandslinger and Dual Wielder are just two of the nine Edges that bring that core concept to life. I mean, even the arcane skill is called Wandslining. How cool is that?

The options included create a lot of variety in how to play different flavors of focus-based arcane casting. For example, you can go the classic D&D route in which one wand has one power or the Harry Potter route in which you use one wand for all the things. Playing a divine caster? Your holy symbol is your "wand."

I don't want to say too much else for fear of giving away the product, but the rules presented here will definitely get your creative juices flowing.

One of my favorite archetypes to play is the dungeon-delving adventurer, be it in a fantasy setting, a pulp-style adventure, or both (e.g., Eberron). This is a fairly resourceful product. My favorite section within it is "Tomb Hazards" with "Idols" as a close second. I thought the Mechanical Genius Edge was a nice touch, too. My next dungeon delver will definitely take that.

My only complaints are with the page backgrounds and the PDF bookmarks. The page backgrounds are a bit busy and make the text somewhat difficult to read. There are no layers that can be toggled off either. The PDF bookmarks aren't complete, and those that are there don't link to the appropriate sections of the PDF.

I also have one quibble (not a complaint, honestly) with the About Legendary Games text in the credits page. It refers to the reader as a Paizo fan, but given the context of this being a Savage Worlds product, that might or might not be the case. It just seemed a little presumptuous given the target audience. Not a big deal, but something for the authors to think about.

One final note: please be conscientious of "racist" fonts. There's a great Twitter thread that discusses this concept.

The content of the book is fine. I have an original hardcopy. But the PDF doesn't display in Adobe Reader for Android (version 11.1.3). I believe this is related to the fact that it was generated using distiller. This isn't the first PDF in the Eberron line that has had rendering issues either. I'm sorely disappointed.

If Wizards of the Coast is reading this, which I doubt they are because they never responded to my review on Faiths of Eberron, I'd be willing to generate new PDFs using a current version of InDesign for them if they don't have the time or resources to do it themselves.

While the content of the book itself is great, the quality of the PDF is lacking. It renders as image slices tiled into place, and I suspect its because of the method used to generate the PDF. This can be caused by using the distiller instead of exporting the document as a PDF. I would appreciate it if WotC could correct this by exporting it from a more current version of the InDesign (this was made with InDesign CS2).